Docs / Getting started

From install to first report in five minutes.

TeamLaboration is one process. It installs to a per-user directory, starts at login, and serves a dashboard at http://localhost:7842. The steps below take you end to end.

Before you start

· Windows 10/11 (x64) or macOS 13+ on Apple Silicon. No admin rights needed on either.
· Claude Code installed and logged in (claude login) with an active Claude subscription (Pro or Max). Summaries run on that subscription via the local claude CLI, no API key.

Step 01

Install

Grab the installer for your OS. No admin elevation prompt. The app registers itself for at-login start automatically, Task Scheduler on Windows, LaunchAgent on macOS.

↓ Download for Windows

Windows

· Installs to %LOCALAPPDATA%\TeamLaboration
· Data lives in %APPDATA%\TeamLaboration
· Tray icon in the system tray

macOS

· Drag from the DMG to /Applications
· Data lives in ~/Library/Application Support/TeamLaboration
· Runs headless under launchd

Step 02

Open the dashboard

The daemon binds to localhost only - never the open network. Click on system tray icon it will open page:

http://localhost:7842

Step 03

Log in to Claude Code

TeamLaboration summarizes by shelling out to your local claude CLI, so it runs on your existing Claude subscription, there is no API key to paste. If you haven't already, install Claude Code and run claude login once.

claude login

The dashboard shows a setup card until it detects the CLI is installed and authenticated. Prefer to drive summarization yourself? Set ai_enabled = false in Settings, see step 5.

Step 04

Wait for the first poll

Every five minutes (configurable) the collector walks sessions, and queues any new or changed sessions for summarization. The daemon then summarizes pending sessions on an interval (every 4 hours by default, set in Settings), plus a catch-up run at startup.

If you want results now, open the Week view and click Generate Report. This runs both summarization and the weekly rollup immediately for the selected week.

Step 05 · optional

Register the MCP server

TeamLaboration exposes an MCP server at /mcp/ on the same local port. Register it once with Claude Code:

claude mcp add --transport http teamlaboration http://localhost:7842/mcp/

Keep the trailing slash on /mcp/, without it Starlette returns a 307 redirect that the MCP HTTP client doesn't follow, and the handshake fails. Verify with claude mcp list.

After registration you can ask Claude Code things like "summarize my week," "flag the auth session as a highlight," or "what did I work on in project X?", and Claude will call the right tools. More on MCP.

The mcp__teamlaboration__summarize_pending and mcp__teamlaboration__weekly_report slash commands let the Claude Code session you're in act as the summarizer, handy if you'd rather not have the daemon run the CLI on its own.

Troubleshooting

No sessions show up after a poll

Confirm Claude Code has actually written files to ~/.claude/projects/. The collector only sees the JSONL session files it produces, a fresh install with no session history will be empty until you use Claude Code.

Summarization stays "pending"

Either Claude Code isn't installed or logged in (check the dashboard's setup card), ai_enabled is false, or the interval hasn't fired yet. Click Generate Report in the Week view to force it.

Dashboard doesn't load

Check logs/agent.log in the data directory. Common causes: port 7842/7843/7844 all bound by other apps, or the daemon hasn't autostarted. Launch the app manually to register the autostart entry.

Set TEAMLABORATION_DEBUG=1 for verbose logs

Restart the daemon after setting it. Logs will include the full collect/summarize pipeline traces.

← All docs Next: Configuration →