# ClaudeDo A desktop task management app that executes tasks autonomously via Claude CLI in isolated git worktrees. ## Architecture Two-process system communicating over SignalR (`127.0.0.1:47821`): - **ClaudeDo.App** — Avalonia desktop entry point, DI container setup - **ClaudeDo.Ui** — Views, ViewModels, SignalR client (MVVM with CommunityToolkit.Mvvm) - **ClaudeDo.Data** — SQLite data layer, repositories, models, GitService - **ClaudeDo.Worker** — ASP.NET Core hosted service, task queue, Claude CLI runner - **ClaudeDo.Localization** — `locales/en.json` + `locales/de.json` and the lookup service - **ClaudeDo.Installer** — WPF (`UseWPF`) setup app; install/update/uninstall step pipeline - **tests/** — six xUnit projects (Worker, Data, Ui, Localization, Installer, Releases); Worker.Tests run real SQLite and real git Each project has its own `CLAUDE.md` — those are the living per-project docs. ## Tech Stack - .NET 8.0, Avalonia 12.0.0 (Fluent theme) - SQLite (WAL mode) via Entity Framework Core (Microsoft.EntityFrameworkCore.Sqlite) - SignalR for real-time IPC - CommunityToolkit.Mvvm (`[ObservableProperty]`, `[RelayCommand]`) - Git worktrees for task isolation ## Key Paths - DB: `~/.todo-app/todo.db` - UI config: `~/.todo-app/ui.config.json` - Worker config: `~/.todo-app/worker.config.json` - Logs: `~/.todo-app/logs/` - Worktrees: configured per worker (sibling or central strategy) ## Conventions - Repository pattern — each entity has its own async repository - All data operations are async with CancellationToken support - EF Core migrations manage schema (Migrations/ folder in ClaudeDo.Data) - `IDbContextFactory` used by singleton consumers (e.g. Worker) - Entity configuration via `IEntityTypeConfiguration` in Configuration/ folder - Task status flow: Idle | Queued -> Running -> WaitingForReview -> Done | Failed | Cancelled. A task that spawns/has children passes through WaitingForChildren first, then surfaces for review once every child is terminal — this is the single parent model for both planning and improvement parents (planning/improvement *children* themselves go straight to Done, only the parent is reviewed). From review you can approve, reject-rerun (Queued, resumes the session with feedback), reject-park (Idle), or cancel. Approve is the single review+merge action: a childless task merges its own worktree then Done (conflicts keep it in WaitingForReview); a task with children drives the unit merge (parent worktree if any + each Done child in order, with conflict continue/abort). Tasks with no active worktree (sandbox run) approve straight to Done. - Worktree state flow: Active -> Merged | Discarded | Kept - The queue picker claims tasks by `Status=Queued` (with `BlockedByTaskId IS NULL`); the legacy tag system was removed - Interfaces live in an `Interfaces/` subfolder beside their consumers (namespace unchanged) - Small single-consumer helper types live in their consumer's file, not standalone files - Commit messages use conventional format: `{commitType}(slug): title` - Views use compiled bindings (`x:DataType`) - ViewModels use `[ObservableProperty]` and `[RelayCommand]` source generators ## Working style (autonomous) For any non-trivial feature, bug, or change, run this loop without hand-holding: 1. **Brainstorm first** (superpowers:brainstorming) — ask clarifying questions one at a time, propose 2–3 options with a recommendation, present a short design, get approval before building. 2. **Write it down** — a spec in `docs/superpowers/specs/YYYY-MM-DD--design.md` and a step-by-step plan in `docs/superpowers/plans/` (superpowers:writing-plans). Commit the docs. 3. **Implement on main** with superpowers:subagent-driven-development — one subagent per task, TDD, build + test, commit per task with Conventional Commits. Once the plan is approved, do NOT pause for re-approval between tasks; only stop for genuine decisions or blockers. 4. **Trust but verify** — read each subagent's diff and run the build/tests yourself before marking a task done. 5. **Bugs** → superpowers:systematic-debugging (find the root cause before any fix). 6. **Never claim UI works without running it** — explicitly flag visual-verification gaps for the user to check. Commit freely (per task + the spec/plan docs). Never push without asking. ## Building & Testing `dotnet build ClaudeDo.slnx` requires .NET 9; on .NET 8 build individual projects with `-c Release` (a running Worker locks the `Debug` output). ```bash dotnet build src/ClaudeDo.App/ClaudeDo.App.csproj -c Release # pulls in Ui + Data dotnet build src/ClaudeDo.Worker/ClaudeDo.Worker.csproj -c Release dotnet test tests/ClaudeDo.Worker.Tests/ClaudeDo.Worker.Tests.csproj -c Release # also: Data.Tests, Ui.Tests, Localization.Tests, Installer.Tests, Releases.Tests ``` ### Gotchas - **Subagents:** use the `sonnet` model; stage files explicitly by path — never `git add -A` (parallel sessions often leave unrelated WIP in the tree). - **Icons:** `PathIcon` *fills* its geometry. Line-art/stroke icons must be authored as filled geometry, or rendered with a stroked `Path` — otherwise they render invisible. - **Localization:** `locales/en.json` and `locales/de.json` keys must stay in parity (Localization.Tests enforces it). - **Test fakes:** changing `IWorkerClient` / `WorkerHub` / ViewModel constructors breaks hand-rolled fakes in both test projects — update them. ## Docs - `docs/open.md` — open verification items and remaining code TODOs (the only doc kept current besides the CLAUDE.md files) - `docs/plan.md` — original design spec (historical; tag-queue/schema.sql parts are outdated) - `docs/improvement-plan.md` — improvement snapshot from 2026-04-13 (historical) - `docs/prompts-inventory.md`, `docs/mailbox-proposal.md` — reference material (mailbox integration is parked) - `CHANGELOG.md` — Keep a Changelog format, maintained on release