claude_agent_teams_ui

• Task creation with attachments — send a message to the team lead with any attached images. The lead will automatically create a fully described task and attach your files directly to the task for complete context.

• Auto-resume after rate limits — when the lead hits a Claude rate limit and the reset time is known, the app can automatically nudge the lead to continue once the cooldown has passed

• Deep session analysis — detailed breakdown of what happened in each agent session: bash commands, reasoning, subprocesses

• Smart task-to-log/changes matching — automatically links session logs/changes to specific tasks

• Advanced context monitoring system — comprehensive breakdown of what consumes tokens at every step: user messages, Claude.md instructions, tool outputs, thinking text, and team coordination. Token usage, percentage of context window, and session cost are displayed for each category, with detailed views by category or size.

• Recent tasks across projects — browse the latest completed tasks from all your projects in one place

• Zero-setup onboarding — built-in runtime detection and provider authentication

• Built-in code editor — edit project files with Git support without leaving the app

• Branch strategy — choose via prompt: single branch or git worktree per agent

• Team member stats — global performance statistics per member

• Attach code context — reference files or snippets in messages, like in Cursor. You can also mention tasks using #task-id, or refer to another team with @team-name in your messages.

• Notification system — configurable alerts when tasks complete, agents need your response, new comments arrive, or errors occur

• MCP integration — supports the built-in mcp-server (see mcp-server folder) for integrating external tools and extensible agent plugins out of the box

• Post-compact context recovery — when the active runtime compacts its context, the app restores the key team-management instructions so kanban/task-board coordination stays consistent and important operational context is not lost

• Task context is preserved — thanks to task descriptions, comments, and attachments, all essential information about each task remains available for ongoing work and future reference

• Workflow history — see the full timeline of each task: when and how its status changed, which agents were involved, and every action that led to the current state

Developer architecture docs

For feature architecture and implementation guidance:

• Canonical standard - docs/FEATURE_ARCHITECTURE_STANDARD.md
• Repo working instructions - CLAUDE.md
• Feature root guidance - [src/features/README.md](src/fe