Plans & Specs

These are historical working documents, not reference material. Each one captures a proposal or design as it stood on the date it was written. Some have shipped, some haven’t — check the status note at the top of each page (or the linked architecture docs) for what’s actually true today.

This section is kept separate from Architecture and Standards on purpose: those describe the system as it is; these describe decisions as they were proposed. Mixing the two would make it hard to tell what’s current.

Plans

Implementation plans for specific features or refactors.

• Native Context Menu — proposal to replace the shadcn/ui ContextMenu with Tauri v2’s native menu API in the Runner panel
• Shared Chat — Implemented. The plan that produced useChat, chatStore, and the shared chat components now used across Wizard, Screens, Components, Themes, and Plans
• Tool Permission System — Implemented. Pre-implementation design proposal for the ToolPermission event and accept/reject cards; kept as the original design rationale and edge-case analysis
• Open Agent SDK Analysis — feasibility comparison of adopting open-agent-sdk v0.6.4 vs. the current hand-rolled agent loop

Specs

Design specifications written ahead of implementation.

• Shared Chat Design — component design for the shared chat layer described in the Shared Chat plan above

Where to look instead

• For how the system works today, see Architecture
• For the rules current code must follow, see Standards