Everything TeamLaboration does, in detail.
A long-scroll breakdown of every feature in the Solo tier. If you skim only the headlines you'll still get the shape of it.
Every Claude Code session becomes a structured entry.
When a session finishes, TeamLaboration captures a title, the key topics, decisions made, and the outcome, usually 1–3 sentences. Stored locally in SQLite. Raw logs are never modified or copied.
One narrative across your whole week.
Session records roll up into one readable account of the week, themes, accomplishments, and notable decisions. Generated on demand, so the AI cost is bounded. Re-runnable for past weeks.
Ask Claude Code about your own week.
TeamLaboration exposes 13 MCP tools, list weekly reports, search past records, flag highlights, regenerate a record. Any MCP client can use them. Configuration mutations (model, interval, polling) are intentionally not exposed.
claude mcp add --transport http teamlaboration http://127.0.0.1:7842/mcpSolo tier has no server. Period.
The daemon, the database, and the dashboard all run on your machine. The only outbound call is your local Claude Code CLI, running on your own Claude subscription. No analytics, no telemetry, there is no TeamLaboration server in Solo tier.
Read it where you already work.
In-app dashboard at localhost, plus Markdown and HTML files written to a folder you choose, point it at a synced folder (Dropbox / iCloud / Drive) to mirror reports across machines. All local, all optional.
No API key. No per-token bill.
Summaries are produced by shelling out to your local Claude Code CLI, so they run on your existing Claude subscription (Pro or Max), no API key, no metered cost. Pick the model in Settings (default Haiku to conserve your plan limits).
Sensible defaults. Tunable if you want.
Polls ~/.claude/projects/ every 5 minutes (configurable). Stores 4 weeks of records by default; raise or lower the cap as you like. Working-hours / week boundaries default to Mon–Sun. Export to JSON or Markdown before purge.