A personal assistant that lives on your desktop, remembers what matters, and can use your Mac for you.
Pink working rings without desktop obstruction
Branch: feat/computer-working-rings; baseline: 535e7f7d4bccb83ea4ab7759ef4b97e2622e1208; isolated worktree: .cache/computer-working-rings in the external gentle-assistant clone.
Delivery: single-pr (explicit user choice), local only; forecast ~650 authored diff lines including tests. Runners: offline Cargo with existing sherpa libraries, installed Vitest/TypeScript, isolated native app probe; no dependency installation.
Specs
S1 — "y sino mas facil, durante esa accion hacer que gentle dot no se vea y reemplazarlo por otra cosa, en algun lado de la pantalla mostrando que esta trabajando". Temporarily hide the Dot and panel for a screenshot-producing/action call or entire batch, from preparation before capture/input until the final capture. Restore previous visibility afterwards without persisting preferences or activating the app. Do not hide for
list_appsor a denied session grant.S2 — (superseded visual, see S8) "no no, no indicador compacto de texto, sino unos circulos dando vuelta o algo asi en la parte superior de la pantalla, con el mismo estilo que el glow rosa que ya tenemos". Reuse the click-through, nonfocusable, screenshot-excluded glow for pink animated rings/arcs near the top of the controlled display, no text/banner. Rings remain visible through action-mark fading. Follow existing reduced-motion convention with a static illuminated state. Placement on the current controlled display is the proposed implementation default, not permission to cover usable controls.
S3 — "me gusta la de contenido oculto". Preserve exclusion of own panel contents from model screenshots; do not expose chat/settings. No change to JPEG quality65, max long-edge1280 or coordinate mapping.
S4 — Accepted proposal: "El guard permanecería intacto." Do not weaken blocklist, consent, permission checks, risky confirmations, epoch/Stop/panic or target guards. Existing tray Stop and panic remain available; their native operation is a verification obligation, not an assumed pass.
S5 — Accepted proposal: "No aceptaría continuar silenciosamente si falla la ocultación. Si no podemos confirmar un estado seguro, no se envía entrada." Confirm indicator readiness and native temporary hiding before executing capture/input. Bound waits, reject stale/late operations, recheck session epoch after preparation, and restore on all normal refusal/error/Stop paths. Do not claim Drop guarantees restoration after process abort or a blocked native UI. Restoration must not steal keyboard focus.
S6 — "dale vamos con esa" authorizes implementation and verification in external
/Users/alanbuscaglia/work/gentle-assistant. Preserve isolation: no accounts/connectors/keychain use, app model calls, remote execution, automatic dependency downloads, auto-answering native permission dialogs or Yolo. Use RED → GREEN for applicable deterministic rules and the existing shared behavior; independently verify security/concurrency changes and repeat isolated native geometry/refusal checks against a harmless local surface. Report unavailable native/full-screen/multi-monitor checks honestly.S7 — "probemos antes de pr". Do not open/publish a PR or push before applicable automated, independent and isolated native checks are observed. Missing or failed proof is reported for a human decision, never treated as a pass. Single-pr is delivery organization, not immediate publishing authorization.
S8 — (superseded visual, see S9) "cambia los circulitos a algo que concuerde mas con la app y el diseño actual". Replace the three spinning arcs with the app's own visual language: a small copy of the Dot (black disc, accent in-control rim, Rose in mood "control") near the top, no text. Reduced motion follows the Dot's existing rule (no traveling light, rose stays lit). Readiness ack, click-through and fences unchanged.
S9 — "hmm algo mejor, no reusar el logo". Do not reuse the rose/Dot logo. Indicator: thin neon line along the top edge of the controlled display in the rose's neon (#ff2d7a / #ffd6e8) with a traveling light (the app's "traveling light" language), no text or logo. Reduced motion: edge stays lit, traveling light hidden. Ack, click-through and fences unchanged.
Tasks
- T1 | S1–S9 | delegated parallel native/UI units with disjoint edit surfaces; parent owns integration/docs/git | done | commit: see L21 | Risk: items2/4 (visible safety and native/IPC ordering), item3 if shared behavior changes | RED/GREEN: pending | Native and independent proof: pending.
Log
L1 — Original implementation authorization verbatim: "dale vamos con esa". Prior investigation-only directions and earlier hidden-content/blocked-area proposal were refined by S1/S2; the selected implementation hides obstructive own UI temporarily rather than painting blocked rectangles.
L2 — Native prior reproduction at source HEAD660be8: a1280×720 JPEG at scale2/3 omitted an ordinary Dot window at global1836,504,72,72; click1248,360 resolved to own window and returned
Gentle Dot does not control Gentle Dot. The action was refused.No real Calendar actions. Preserve this guard.L3 —
mainis not an ancestor of the original feat/gentle-dot HEAD, so the initial ancestry preflight exited1 before creating a worktree. Inspection foundmain..HEADdiffers only in two historical task-note lines, no source differences. Created a fresh worktree based on local main; original checkout and notes remain untouched. No merges, resets or remote operations. Existing node_modules linked into worktree; no packages installed.L4 — Writer reason: two independent substantial native lifecycle and UI animation units launched together in the same fresh external-repo worktree, with disjoint surfaces. Parent handles docs and seam verification. A400-line heuristic is not a code/test cap; forecast exceeds it, so delivery strategy must be resolved before a feature commit. No push/PR in scope.
L5 — Integration contract: internal
computer://workingevent emitted only to glow, payload{active:boolean, operationId:number}. UI acknowledges rendered active state via internalcomputer_working_ready {operationId}; native handler must accept only glow window and current pending operation. End/stale events cannot resurrect old indicators or perform late hides. Native preparation, including confirmed hiding, is synchronous to helper but dispatched safely to main/UI threads with bounded cancellation. Parent can adjust this contract only through one coordinated handoff before either side relies on a replacement.L6 — Parallel units launched: native N1
mv4enxjk-4-r8eq, UI U1mv4enxnl-5-jnj9. Their source surfaces are disjoint; parent alone edits design/feature docs and owns generated builds and Git. Parent updated S24.6/S28 design descriptions provisionally to match the authorized behavior; no verification pass is claimed yet.L7 — User selected "Un único cambio integral" (single-pr) in the review-size decision. Keep the coherent feature and tests together; accept the forecast above400 authored lines without artificial splitting. This is local organization only, not authorization to publish a PR or transfer repository data.
L8 — User requirement verbatim: "probemos antes de pr". Added S7; T1 remains in progress. No remote/publishing actions while writers or functional proof are pending.
L9 — Native N1 reported computer::working 13/13 and computer::mcp 72/72 GREEN (worker-observed, not yet rechecked by parent). Its new ACL test was RED because the ack command lacked a Tauri permission. Parent, not the writer, added
computer_working_readyto build.rs COMMANDS andallow-computer-working-readyonly to theglowcapability in capabilities/default.json; dot/panel capabilities unchanged. Runtime label/operation validation in the handler remains required.L10 — Integrated checks: cargo test 406 passed/0 failed exit0; clippy exit0; UI vitest exit0, UI tsc exit0, biome exit0 (6 pre-existing warnings). Full-repo vitest/tsc fail only in daemon project because the worktree does not link packages/daemon node_modules (environmental, unrelated). Release build UI_BUILD=0/TAURI_BUILD=0 (harmless rust-objcopy strip warning), ad hoc signed.
L11 — Isolated native probe (job-11, PID 28261, exit0, no clicks/keys, user approved native grant): screenshot OK; Dot 1836,504,72,72 restored after screenshot; during wait(4000) Dot absent from on-screen windows and glow covered 1920x1080 display; Dot restored after wait; frontApp Ghostty unchanged across calls. Glow window stays ordered in while the session is active (pre-existing session-scoped behaviour). Not yet verified: visual appearance of rings (needs human observation), Stop/panic mid-call, multi-monitor, full-screen, panel-visible case.
L12 — User request verbatim: "cambia los circulitos a algo que concuerde mas con la app y el diseño actual". Parent (inline, UI-only) replaced arcs with the in-control rose disc. RED: glow.test.tsx 2 failed/17 passed with old arcs; GREEN: packages/ui vitest 24 files 259 tests passed exit0, UI tsc exit0, biome check exit0. design.md S24.6/S28 updated. Rebuild and native visual check pending.
L13 — Native probe with the rose (job-13) failed dotRestored checks: its 'before' sample (924,252) was taken while the app was still positioning the Dot at startup; after-call positions matched the default 1836,504 from the first run. Probe fixed to wait for a stable Dot position; rerun job-14 PASS (hidden during call, restored to settled position, front app unchanged, no input).
L14 — User request verbatim: "hmm algo mejor, no reusar el logo". Parent replaced the rose with a top-edge neon line + traveling light. RED: 3 failed/16 passed against the rose; GREEN: packages/ui vitest 24 files 259 passed exit0, UI tsc exit0, biome check exit0. design.md updated. Rebuild and visual check pending.
L15 — Parent truncated docs/design.md through a whole-file read/write (50KB read cap); restored from baseline and reapplied the two paragraph edits with the edit tool (diff +2/-1). Native probe with the top-edge light (job-16, PID 43123 gone): PASS, all checks true, no input. Visual confirmation by the user pending.
L16 — User visual approval verbatim: "mucho mejor, vamos con esa". S9 top-edge light accepted. Remaining: native Stop/panic mid-call check, independent verifier verdict, local commit (no PR/push, S7).
L17 — Native panic probe (job-17, PID 45044 gone): wait completed normally after 5344 ms, so no stop was observed; Dot restored; glow still ordered in (consistent with an active session). Cause undetermined: key not pressed in time, global shortcut not registered under isolation, or a real defect. Asked the user.
L18 — Independent verifier mv4fai48-6-4tib: no blockers on the final S9 snapshot. S1/S3/S4 PASS; S2/S8/S9 PASS structurally; S5 PASS in unit tests and 8/8 scratch probes (Stop during ack wait, stale ack, hide timeout then late hide, Drop restore on refusal/decline/panic mid-batch, 200-iteration concurrent Stop, happy path, baseline dump identical). Re-ran Rust 406/0, clippy 0, UI 259/259, tsc 0. design.md confirmed +2/-1 only. To commit as regression tests: probes 1, 2, 4, 6 (fewer iterations) and the Control notify -> session_ended wiring. Advisories: screenshot does not recheck still_running between prepare and capture (baseline), panel reopened+closed mid-call is shown again on restore, rAF throttling fails closed, glow test names still say rings, non-macOS build not compile-checked.
L19 — User had not pressed the shortcut in job-17 ("no no sabia qeu tenia que hacerlo"). Retry job-18 (PID 46776 gone) with a 15 s batch of waits: PASS — panic ⌥⇧Esc stopped the call early, Dot restored, glow gone, no input.
L20 — Verifier probes 1, 2, 4 and 6 committed as
computer::mcp::tests::preparation_races(concurrent Stop at 50 iterations). Regression tests, written after the behavior existed, so no RED phase: they passed on first run (4/4). Full Rust 410 passed/0 failed/4 ignored, clippy exit0. UI test names moved from "rings" to "edge": UI vitest 259/259, tsc 0, biome 0. Control notify -> session_ended wiring in app.rs remains without a unit test (needs a Tauri app handle); covered natively by job-18.L21 — Work-unit commit
c48afb5onfeat/computer-working-rings(15 files, +1690/-37, single-pr). Local only: no push or PR (S7). Not verified natively: multiple displays, full-screen apps, panel visible during a call. Risk: items 2 and 4 (visible safety state, native/IPC ordering); independent verifier found no blockers.