The shell injects the OS version; on macOS 26 the wordmark, reveal button and topbar cluster move up to the lights' midline (centre 21pt, measured on the 0.3.0 DMG).
?overlay=26 previews it in the browser.
The app moves to a free port only when 8765 is taken (after waiting 5 s for a previous copy to stop) and the Machines page then says so; OPENWORKER_PORT overrides for developers (OPE-212).
Linux x86_64 and aarch64 tar.gz from build_linux.sh, attached with versioned and stable names.
The macOS build installs the openshell extra (build_dmg.sh refuses to build without grpcio).
api.ts routes each call to the session's machine or the cloud proxy.
One module turns server payloads into card props and card answers into wire messages.
Sidecar inherits the login shell's env; toolchain resolves absolute paths with pinned
installs; request_tool replaces the 'tool missing -> STOP' instruction that hid a check.
Close-to-tray hides the main window instead of quitting (on_window_event's
CloseRequested handler), but the RunEvent handler only dealt with Exit. macOS
fires RunEvent::Reopen when the Dock icon is clicked, and Tauri does nothing
with it by default — so the app activates (menu bar switches) but no window
appears, and the user has no way to get it back short of relaunching.
Handle RunEvent::Reopen by reshowing the main window via the existing show_main
helper (unminimize + show + set_focus) — the same path the tray "Open" item
already uses. Reopen is macOS-only, so the arm is #[cfg(target_os = "macos")].
Verified against the pinned tauri 2.11.5 source: RunEvent::Reopen is a
macOS-gated non_exhaustive struct variant emitted for applicationShouldHandleReopen
(the Dock-icon click).
The bundle's Info.plist declared usage strings for the mic, Desktop, Documents,
Downloads and Photos, but not Calendars or Reminders. On macOS, TCC blocks
EventKit access OUTRIGHT (no prompt) when the usage-description key is absent,
so a calendar/reminders MCP tool silently fails with no way for the user to grant
access.
Add the Calendar and Reminders usage strings. macOS 14 split the key into a
...FullAccessUsageDescription variant (read by apps built against the 14+ SDK)
and the legacy key (older systems), so both are declared for each. Like the
existing Photos entry — and unlike the mic, a hardened-runtime *device* resource
that also needs an entitlement — these personal-information resources are gated by
the usage string alone on this non-sandboxed, hardened-runtime app.
Info.plist passes plutil -lint; each new key reads back via plutil -extract.
The GUI README still described the pre-split monorepo layout: every command
cd'd into a platform/ directory that does not exist in this repository, so a
fresh contributor following it verbatim fails at the first step. The venv,
packaging scripts, and surfaces/gui all live at the repo root now — align the
commands and the server_bin() dev-fallback comment with the layout the root
README already documents.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
tauri-build validates every bundle.resources path on each cargo build, dev
included, but binaries/sidecar is only staged by the release scripts and
/binaries is gitignored — so `npm run tauri dev` on a fresh checkout failed
with `resource path 'binaries/sidecar' doesn't exist`.
Create the empty placeholder in the build script. Dev needs no packaged
sidecar (server_bin() falls back to the venv server) and tauri-utils skips
empty resource directories, so the bundle is unchanged. Putting it in
build.rs rather than setup_dev_env.sh also covers Windows, where the bash
bootstrap script never runs.
Fixes#131
Shell injects the OS; Windows/Linux keep the native title bar with no traffic-light insets.
Thin scrollbars on Windows/Linux so panels stop losing width to classic scrollbars.
Imported from andrewyng/aisuite@1b4bbf303e
(contents of its platform/ directory, hoisted to the repo root).
Development history prior to this commit lives in that repository.
Co-authored-by: Devika <devikaverma11@gmail.com>