Skip to content

Launch and Run a Team

Teams are launched from the Teams library, not by navigating directly to a team URL. The library is the primary entry point for all team work.

Click Teams in the sidebar. The library lists every available launcher split into two sections: Standing Companies (persistent teams that keep their state between sessions) and Teams (ad-hoc launchers for a specific outcome).

Use the search box or the sort control to narrow the list by name, number of roles, or weekly schedule.

  1. Click a team card. Wayland opens the launcher screen for that team.
  2. Review the roster. The launcher pre-fills the leader and specialists from the team definition. Each row shows the member’s name and its assigned model backend.
  3. Adjust models if needed. Open the model selector on any row to switch that member to a different backend.
  4. Edit the team name if you want to distinguish this run from others.
  5. Click Launch team.

Wayland creates the team and navigates to the active team page.

  1. Click Build my own team (top right of the library, or the card at the end of the Teams section).
  2. The launcher opens in an empty state. Enter a team name.
  3. Pick a leader using Pick leader, then add teammates with Add teammate. Each pick opens a specialist browser showing the available specialists.
  4. Optionally: type a goal description in the goal box and click Suggest. Wayland analyses the text and fills in a recommended roster of up to five members. You can adjust after.
  5. Set models for each member.
  6. Click Create team.

On the active team page:

  • The leader sits at the top. Give it the goal, and it directs the specialists.
  • Each specialist is a tab. Open a tab to see that member’s work in detail.
  • The right rail tracks overall team state.
  • The activity tab shows a log of what every member has done.

Team members ask before using tools that touch your system. Pending permissions surface on the team page so you can approve or deny them as work proceeds.

  1. In the Teams library, click Import team.
  2. Select a .json team export file.
  3. Wayland shows a Capability Review listing the permissions the team requests: file read, file write, agent spawning, network requests, and cross-team messaging.
  4. Grant or restrict each capability, then confirm. The imported team opens on the active team page.

When an ad-hoc team proves its worth, keep it:

  1. From the active team page, open the promote option.
  2. Wayland checks that the team is eligible.
  3. Confirm in the Promote to Standing dialog.

The team now persists between sessions, keeps its place in the active-teams area, and appears as a Standing Company card in the library. See Promote a Team to a Standing Company for more detail.

Wayland has an older multi-user team surface that is accessed at /team/:id directly and is controlled by the TEAM_MODE_ENABLED flag in the application config. It is a separate code path from the launcher library described above. If you are reading internal documentation or build notes that refer to this flag, note that the Teams library (the /teams routes) is the current user-facing path. Do not navigate to /team/:id manually to start new work; use the library.