A personal assistant that lives on your desktop, remembers what matters, and can use your Mac for you.
TypeScript
docs(odd): record the conversation switch bug and inline errors spec
Alan Buscagliac277673e18b5
diff --git a/odd/tasks/gentle-dot.md b/odd/tasks/gentle-dot.mdindex f3bc9b4..9796f8b 100644--- a/odd/tasks/gentle-dot.md+++ b/odd/tasks/gentle-dot.md@@ -64,6 +64,9 @@ Branch: `feat/gentle-dot` · Delivery strategy: `single-pr` (user choice, L7; fo- **S19 — Add any other MCP by asking the assistant.** User (L33): "Notion, Linear, Atlassian tmabien, esta bueno, y pon un apartado de conectar mcp extra, que directamente se lo pida al agente, creo que podria hacerlo no? es mas podriamos reconocer los mcps del user o no ?". The Connectors screen has an "Add another connector" option that starts a chat request. The assistant drafts the server configuration (name, command or URL, required credentials), but it never writes `mcp.json` itself: the daemon applies the draft only after the user approves a card that shows every detail. The same approval applies whenever the assistant tries to change connectors on its own initiative.- **S20 — Recognize the user's existing MCP servers.** Same quote. The assistant detects MCP configurations from common clients (for example Claude Desktop, Claude Code, Cursor, VS Code, and Gentle Shell), reads them read-only, and offers "Found these servers: which ones to import?". Import is an explicit per-server choice; secrets go only into the assistant's private home, and the source files are never modified.+- **S21 — Switching conversations while the assistant answers, and errors in the chat.** User (L34): "y creo que encontre un bug, si mientras el agente esta respondiendo un mensaje, abro otra conversacion, da error y no dice que hubo error en el mismo chat".+ - Acceptance: opening another conversation or starting a new one while the assistant is answering asks first ("The assistant is still answering. Stop it and open the other conversation?" with Stop and switch, or Cancel). On confirm, the run is stopped and the switch happens, with no error shown for that intentional stop. Errors while answering appear inline in the conversation where they happened, in plain words, not only as a toast. A user-initiated stop shows a neutral "Stopped." note. History requested before the agent is ready waits for it instead of failing.+## Tasks| ID | Specs | Route | Status | Commit / evidence | Scope |@@ -84,7 +87,7 @@ Branch: `feat/gentle-dot` · Delivery strategy: `single-pr` (user choice, L7; fo| T14 | S13 | delegated writer (after T15, shares apps/desktop) | pending | — | Linux port of the desktop app: per-platform window effects, tray icon, Wayland fallbacks, AppImage/deb bundles || T15 | S6, S7, S11, S12, S9 | delegated writers (parallel: daemon/isolation vs. Dot circle) | done | `8626a7d`, `05000c8`, `ac86f64`; limited recheck PASS (L31) | One correction batch for verifier blockers B1–B4 and the S9 circle change, then a recheck limited to them || T16 | S10 | inline | done | `7337b52` RED 4 failing → GREEN 14/14 | Accounts in two steps: method first, then provider |-| T17 | S14–S17 | delegated writer (context backstop) | in progress | — | Queue display, gentlemanprogramming.com style, typing closes options, header icons |+| T17 | S14–S17, S21 | delegated writer (context backstop) | in progress | — | Queue display, gentlemanprogramming.com style, typing closes options, header icons || T18 | S18–S20 | explore (delegated, read-only) → spec details → implement | in progress | — | Connectors: map the engine's MCP integration and the providers first || T9 | S1–S6, S9–S12 | delegated verifier (high risk: process supervision, auth) | done | L24 + L31 | Full verification: unit, integration, Playwright, `@real-agent`, `tauri build` + launch, manual macOS checklist with observed results |@@ -125,4 +128,5 @@ Environment notes: Node v24.14.1 and pnpm are present. `cargo` is on PATH but `r- **L31 (2026-10-08, limited recheck):** An independent verifier (scratch copy, temp HOMEs, ports away from the user's 4317/7437/7438) passed B1, B2, B3, B4, L25, and L26 at `ac86f64`, and each failure reproduced at baseline `deeb33a`. B2 probe: the seeded HOME hash is identical before and after a first start (`b5f7056…`). L25: 42 providers, 8 OAuth, none Anthropic, and Anthropic OAuth is refused with no runtime call. Regression: 197 tests, typecheck, lint, e2e 9/9, cargo 39/39. No blockers remain. Advisories for later: (1) the assistant's Engram server outlives the daemon (orphaned after stop); (2) deploy-vps telemetry opt-out line likely does not work in the container (pre-existing); (3) old daemon.log files from earlier builds still hold the token (now 0600; the token was not rotated); (4) e2e does not re-check the method buttons after "Back to accounts" (UI test covers it); (5) a small TOCTOU window between realpath and write in the frontmatter sync. With L24 (S1/S9 confirmed on the user's Mac: tray, menu, panel, 72×72 window), T9 is complete for S1–S12 except the items not verifiable here (live animation in WKWebView, real OAuth subscription sign-in).- **L32 (2026-10-08, user):** "como podemos hacer para un apartado de conectores, por ejemplo gmail, slack, discord, etc". The parent verified that the engine reads `<agentHome>/mcp.json` (`mcpServers`) and keeps `mcp-auth.json` and `mcp-cache.json` there, and that `@earendil-works/pi-mcp` provides stdio and Streamable HTTP transports plus an MCP OAuth client (`pi-mcp/oauth`; it does not open a browser or choose storage). The proposal was accepted: "dale me gsuta )".- **L33 (2026-10-08, user):** "Notion, Linear, Atlassian tmabien, esta bueno, y pon un apartado de conectar mcp extra, que directamente se lo pida al agente, creo que podria hacerlo no? es mas podriamos reconocer los mcps del user o no ?". Decision recorded: the assistant drafts and the daemon applies after user approval (prompt-injection guard). Import of the user's MCP servers is read-only, per server, and explicit. The explorer was asked to extend its map.-- **Next step:** T18 read-only map (extended); T17 (UI writer running); then T14 (Linux).+- **L34 (2026-10-08, user):** "y creo que encontre un bug, si mientras el agente esta respondiendo un mensaje, abro otra conversacion, da error y no dice que hubo error en el mismo chat". Reproduced from the user's `~/.gentle-dot/daemon.log` (error lines only): `12:17:05 assistant error: This operation was aborted`. Pi's `switch_session` aborts the active run (`agent-session-runtime.js` teardownCurrent → `session.abort()`); the bridge turned the aborted `message_end` into a generic error toast outside the chat. Also, `command get_history failed: Agent is not ready` repeats at every startup (history requested before the agent is ready). Both were added to T17 (same files: bridge.ts and UI).+- **Next step:** T18 read-only map (extended); T17 (UI writer running, now including S21); then T14 (Linux).