Make your computer a home for your AI partner. Avibe is the local-first Agent OS: Vibey, its built-in AI partner, works out of the box, and Claude Code, Codex & OpenCode run unchanged beside it — reach them from your browser, phone, or any chat app.
Pinned Cua Driver Patches
Avibe consumes the MIT-licensed cua-driver-rs-v0.31.0 source at commit
5272e492d61b96caf08e3bf434d91126c1f3dccc. The release binary is not used
for this variant. The package workflow downloads the pinned source archive,
verifies its SHA-256, applies the patch recorded in sources.json, builds the
requested macOS target, and records the resulting provenance.
avibe-raw-single-click-reopen-v2
Patch: patches/0001-macos-raw-single-click.patch
This patch adds the opt-in click.click_mode selector:
- omitted or
"auto"preserves the existing AX-firstcount=1behavior; "raw"is accepted only for an exactpidandwindow_id, window pixel coordinates, background left-click delivery,actionpressorclick,count=1, no modifiers, and no element or portable target;"raw"bypasses the macOS pixel-path AX hit-test/AXPressoptimization and uses the existing routed CGEvent path;- unknown values and invalid combinations return structured
invalid_arguments.
The patch also changes macOS launch_app for an already-running application: it
sends kAEReopenApplication (aevt/rapp) while preserving activates=false;
cold launches and explicit new-instance launches continue to send
kAEOpenApplication (aevt/oapp). Bundle-ID and name lookup share this event
selection. The URL handoff path remains unchanged.
The patch also adds the test-owned AppKit hollow-AX target and its ignored
background acceptance harness. The target reports AX presses separately from
native mouseDown/mouseUp delivery, so the acceptance can prove one raw
mouse pair and unchanged default behavior without relying on the tool result
alone.
For embedded serve mode, the patch also makes parent-liveness shutdown
terminal: stdin EOF removes only the socket bound by that process, removes its
PID file, aborts accepted connection tasks, and drops the Tokio runtime without
waiting for non-cancellable platform work. After that cleanup,
std::process::exit(0) terminates the helper even when the macOS cursor
overlay owns the main AppKit run loop. Its shutdown diagnostic is best-effort
because parent death also closes the shell-owned stderr pipe. The terminal path
leaves process globals intact because abandoned tasks may still reference them
until process exit. Explicit daemon shutdown keeps the existing graceful drain
and global teardown. The default process test keeps the cursor overlay disabled
so ordinary cargo test runs remain hermetic; the overlay-enabled macOS variant
is ignored and reserved for an explicit logged-in GUI acceptance run.
The upstream investigation found no consumable maintainer-accepted contract with these semantics. The relevant discussions are:
The exact patch SHA-256, source archive SHA-256, tool snapshot SHA-256,
contract, and upgrade plan are duplicated in sources.json. The reopen hunk is
tracked by upstream PR #6198 and is removed after a release containing that
contract; the raw-click and parent-liveness hunks have independent upgrade
conditions. The release
provenance uses schema 2 and includes those hashes plus the prepared binary
hash and post-signing packaged hash.
When an upstream release includes the running-app rapp launch contract,
remove only that hunk. Keep the raw-click and parent-liveness hunks until their
corresponding upstream contracts are released. Otherwise, rebase the single
patch onto the next pinned source commit, rerun the fixture and lifecycle
acceptance, refresh the source and snapshot hashes, and review the Avibe
forwarding admission again.
Foreground delivery is the unpatched driver's own delivery_mode: "foreground" rung, and window activation is its bring_to_front tool. Both
are forwarded unchanged since #3050; neither is an implicit fallback for this
patch, whose raw selector stays background-only.