Team Editor

Compose multi-agent teams from existing profiles and launch them together.

How teams work

A team is a set of profiles wired together. One profile is the lead. It launches in the foreground terminal and spawns the others as teammates through Claude Code's native agent-teams mechanism. Each teammate gets its own isolated CLAUDE_CONFIG_DIR and its own CLAUDE.md, plus ownership tags so delegations from the lead route to the right member.

Top bar

• The name is an inline text input.
• The members count updates as you add or remove profiles.
• The directory dropdown picks the project directory to launch the lead into.
• Launch opens the lead in a terminal with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 set, then runs the generated /start-team command. It stays disabled until a lead is designated.
• The overflow menu holds Preview Merge and Delete Team.

Info card

Same shape as the profile editor: description, tags, and imported projects that scope the team to specific directories.

Drag-and-drop composition

The main pane is split in two.

Left: Available Profiles

• Every profile that isn't already in the team.
• Search bar at the top.
• Each row shows the profile name and its plugin count.
• Drag any row to the right panel to add it to the team.

Right: Team Members

A sortable list of added profiles. Drag rows to reorder. Each member card has:

• A role field. Free-form label like "backend", "reviewer", or "researcher", used in the generated ownership tags.
• An instructions textarea. A per-member CLAUDE.md snippet that loads only in that teammate's session.
• A colour override for the member's identity colour. Optional.
• A lead toggle. Exactly one member can be the lead.
• Navigate to Profile, which jumps to the source profile's editor.
• Remove, which takes the member out of the team. The source profile is unaffected.

If no members are added yet, a drop zone reads "Drag a profile here to add".

Merge preview

The Preview Merge modal shows the team's combined plugin, skill, agent, and command set. It's the union across every member. Useful for spotting collisions like two members both owning /test, or for checking the context budget before launching.

Launch

On launch ClaudeWorks does four things:

1. Assembles a team-wide config directory at ~/.claudeworks/teams/<name>/. Contains a filtered installed_plugins.json (the union across members) and a consolidated settings.json.
2. Writes per-member CLAUDE.md fragments with ownership tags so the lead's delegations route correctly.
3. Checks for CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. If it's missing, an env var gate modal offers three options:
   • Add to Global Settings, which writes the variable into ~/.claude/settings.json.
   • Add to Project, which writes the variable into the selected project's .claude/settings.json.
   • Cancel.
4. Opens the lead in a terminal and runs the generated /start-team.

Deleting a team

Use Delete Team from the overflow menu. The source profiles stay intact. Only the team composition is removed.