CodeAFTeams

Teams

Many agents become a few outcomes you can name and steer.

Group agents by the outcome they serve, not the window they happen to live in.
  • a release crew
  • a bug-bash squad
  • a docs team

Group agents by the outcome they serve, not the window they happen to live in. A team in CodeAF is a named, coloured group of conversations. It is a grouping, not a place: one conversation can be in several teams at once, and making or changing a team never opens, closes or stops any work.

Try it in CodeAF

Where

On Teams (/teams or Alt+2).

Press
  1. Click + New team below the sidebar.
  2. Enter a name and choose a colour. Select existing conversations from the searchable Name/Project list, or leave it empty.
  3. Press Enter to create the team.
You see

The team appears in the sidebar and All teams overview. + Add chat adds a new or existing conversation; + Add subteam creates a team beneath it.

Living with teams

A conversation can belong to more than one team without being copied. Selecting a team in Teams selects its overlay in Chats. In Chats, the team chip's name switches teams and its separate x clears the overlay. The ▦ All conversations grid always shows the full saved conversation library; selecting a team does not filter that grid.

You can also create a team in Chats: open ▦ All, choose + New team (or press S), select the conversation cards, then choose Create team. Canceling changes no memberships.

The teams page

All teams shows nested team cards, saved updates, activity counts and the optional Global manager. Deep or narrow hierarchies become expandable tree rows. Select a team to see its manager, member previews, recent interactions and questions waiting on you. Prev and Next page through six recent interactions at a time. Opening a preview continues in Chats; simply browsing runs nothing.

Use Settings for the selected team's name, colour and inherited settings. Organize suggests groupings and waits for Apply. Removing a member leaves its conversation and current work intact. A manager must be reassigned before it can be removed. Disband ends coordination for the team and its descendants while retaining history; it does not delete their conversations.

A team on its own only groups work. Give it a manager and it becomes a unit that takes one goal and reports back; nest teams and give each a manager, and the tree on this page is your org chart.

Things to build

  • A team per project: Organize turns a window of unrelated chats into named teams, one per folder, in one pass. Organize a messy window
  • A shared chat: one conversation filed in two teams, so both walls show it without a copy.
  • A capped sandbox: a team with its own daily cap on its Settings card, so its work stops at the cap and asks you once.
  • A tree of teams: a platform team with api and infra under it, each with its own manager, drawn as one tree. Your org chart

Go further

Managers: give a team an agent that runs it.

Coming soon: describe the org you want and CodeAF builds it: teams, managers, budgets, standing orders.