Team rules

Where to set them

In the web dashboard, open Team and then the Rules tab.

What can be locked

• Clearing an Agent Mode chat, or deleting one of its tasks
• Starting a new Agent Mode chat
• Deleting captured prompts (and their recorded file changes)
• Creating or deleting project notes
• Deleting a project and its history
• Pausing monitoring of a project
• Creating, editing or deleting named @agents
• Connecting an agent CLI, or changing the model it runs
• Signing in to GitHub
• The IDE integration, and team agents with a remote (A2A) URL
• Turning a capture source off, IDE monitoring off, or usage sync off
• Exporting a project’s prompts to a file

Approved agents

Allow any agent, or only these: Claude, Codex, Cursor, Antigravity and GitHub Copilot. An agent left off the list does not appear in the app’s rosters and cannot be connected.

Approved repositories

Allow any folder, or only a list of GitHub repositories (up to 100, as owner/repo or a URL). A folder is then accepted only if it is a git repository with a remote pointing at a listed repository. New Repository is off, and Clone offers only the listed ones; an existing local clone of a listed repository can still be added.

The check runs when folders are added to a project. A folder a project already had stays.

Team defaults and per-person rules

The Team defaults card holds the switches, the agents list and the repository list. The Per person card gives one seat its own switches and agents list, replacing the team’s outright rather than merging with them, so one person can be given more or less than the rest. The repository list is always the team’s.

How rules are enforced

Rules travel with each seat holder’s session. The app locks the controls a rule turns off, and refuses the action itself with a message saying the team turned it off, so a control can’t slip through. Settings → Plan shows a “Managed by your team” card listing what is off.