Skip to content

A personal assistant that lives on your desktop, remembers what matters, and can use your Mac for you.

TypeScript

docs(odd): add the continuous chat spec

Alan Buscaglia03dbab95e553
diff --git a/odd/tasks/gentle-dot.md b/odd/tasks/gentle-dot.md
index c76c5c0..011e8bb 100644
--- a/odd/tasks/gentle-dot.md
+++ b/odd/tasks/gentle-dot.md
@@ -67,6 +67,9 @@ Branch: `feat/gentle-dot` · Delivery strategy: `single-pr` (user choice, L7; fo
- **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.
+- **S22 — One continuous chat.** User (L38): "por ahora entonces si es una sola sesion no pongas la capacidad de hacer nuevos chats, dejalo como esta pero ocultalo que sea un solo chat continuo te parece? mi unico miedo es que pasa cuando compacta mucchas veces y asi, si no sera mucho contexto".
+ - Acceptance: the UI hides "New conversation" and the conversations list (the code and protocol stay, behind a flag, so they can return), and the header shows the assistant instead of a conversation title. The chat feels endless: the daemon rotates the underlying session transparently when it grows past a threshold (default 20 MB or 10 compactions), starting a fresh session seeded with a handoff summary, and the UI shows the previous session's recent messages above a subtle "Earlier messages" divider. The UI loads only recent messages, with "Show earlier" for more. Engram stays the durable memory, so compaction detail loss does not lose decisions.
+
## Tasks
| ID | Specs | Route | Status | Commit / evidence | Scope |
@@ -89,6 +92,7 @@ Branch: `feat/gentle-dot` · Delivery strategy: `single-pr` (user choice, L7; fo
| T16 | S10 | inline | done | `7337b52` RED 4 failing → GREEN 14/14 | Accounts in two steps: method first, then provider |
| 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 |
+| T19 | S22 | inline or delegated after T17 (same files) | pending | — | Single continuous chat: hide conversations, transparent session rotation, recent-only history |
| 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 |
Environment notes: Node v24.14.1 and pnpm are present. `cargo` is on PATH but `rustc` is not, so T7 must first install or repair the Rust toolchain (rustup) and asks before installing. Xcode is present.
@@ -132,4 +136,5 @@ Environment notes: Node v24.14.1 and pnpm are present. `cargo` is on PATH but `r
- **L35 (2026-10-08, T18 map + web verification):** MCP is a built-in pi-coding-agent 1.0.4 extension that reads `<agentDir>/mcp.json` only at `session_start` and stores OAuth in `mcp-auth.json` (keys `mcp__<ns>|<url>`, locked writes); new tokens are picked up on the next turn. Headless OAuth runs as a separate process (`pi mcp login <name>` with the assistant's agent dir and HOME), because `/mcp login` in RPC sends the URL as an info notice that the sanitizer hides. The assistant disables codemode, so each server needs `exposure: "direct"|"deferred"`. Approval is enforced by an extension loaded with `-e` that hooks `tool_call` (it can block, covers nested calls, and asks through `ctx.ui.confirm` → ask card). Pi documents agents running `pi mcp add` through bash, so the daemon must be the only writer of `mcp.json` and must validate it against the approved set (hash) before each start; `propose_connector` returns drafts only. Tool annotations are kept, so read-only means `readOnlyHint` AND a curated list (fail closed). Providers, from official docs on 2026-10-08: Notion `https://mcp.notion.com/mcp` (OAuth + PKCE); Linear's official remote server (OAuth 2.1 with dynamic client registration, or an API key); Atlassian Rovo `https://mcp.atlassian.com/v2/mcp` (OAuth 2.1, or an API token; the explorer's v1 URL was outdated); Slack's official hosted server requires a registered Slack app with client_id + client_secret; Gmail's official `https://gmailmcp.googleapis.com/mcp/v1` is in Developer Preview and needs the user's own Google Cloud project and consent screen; Discord has only community servers (bot token). The import map (S20) found configs for Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, OpenCode, and Gentle Shell on this Mac (key names only).
- **L36 (2026-10-08, user decision):** Slack and Gmail: "Guía paso a paso ahora (Recomendado)" — each user creates their own Slack app or Google Cloud project with an in-app guide; no Gentle Dot-owned OAuth apps for now.
- **L37 (2026-10-08, user):** "ah no puede atender mas de una conversacion a la vez?" The assistant answers one conversation at a time (one RPC agent process with one active session). An agent pool (one process per active conversation, capped at 3) was proposed with its costs; user: "dejemos uno solo por ahora". Decision: keep a single active conversation; no spec added.
-- **Next step:** T17 (UI writer running, now including S21); then T18 implementation (it shares the bridge, protocol, and UI with T17, so it starts after T17); then T14 (Linux).
+- **L38 (2026-10-08, user):** "por ahora entonces si es una sola sesion no pongas la capacidad de hacer nuevos chats, dejalo como esta pero ocultalo que sea un solo chat continuo te parece? mi unico miedo es que pasa cuando compacta mucchas veces y asi, si no sera mucho contexto". Evidence (pi-coding-agent docs/compaction.md:20-45, session-format.md "Context Building" and "CompactionEntry"): auto-compaction triggers when context > window - reserveTokens (16384) and keeps about 20k recent tokens plus the latest summary, so the model context stays bounded. Detail degrades with repeated summaries (Engram mitigates that), and the session file keeps every entry, so it grows forever on disk. Hence S22 rotation.
+- **Next step:** T17 (UI writer running, now including S21); then T19 (continuous chat) and T18 (connectors), both after T17 because they share files; then T14 (Linux).