Choose the boundary once
Put the supervision policy with the project, not in a checklist each developer has to remember. The same rules follow every session opened there.
Saggar for teams
Any agent. Your policy.
Let developers use the agents, tools, and workflows that make them effective. Keep supervision rules where the team owns them: at the project level.
Saggar gives every terminal and coding agent one place on the Mac. Its planned Teams tier will let teams set project-level supervision policies without turning developer choice into an exception process.
Teams controls are planned, not shipped. The Mac app is available to evaluate now.
payments-apiProject policy
ClaudeCodexAntigravityShell
- Read and edit project files
- Allow
- Run project commands
- Supervise
- Write outside the project
- Block
- Publish or deploy
- Supervise
One boundary, whichever tool opens the session.
The tradeoff is false
Standardize the rules, not the craft.
Growing teams need shared rules while developers choose the tools that work for them. Saggar’s direction is a stable project boundary around a changing set of tools, so each developer can work without rebuilding the rules for every session.
Keep the developer’s tools
Claude, Codex, Antigravity, ordinary shells, and the next useful agent can work side by side. The policy governs the work without prescribing the tool.
Make exceptions visible
Sensitive actions stop for a person. Routine actions keep moving. Teams can inspect the decisions instead of relying on a blanket yes or no.
Available now
A common place to run the work
Native Mac terminals, projects, worktrees, attention states, and per-session supervision across supported agents and ordinary shell tools. Code and sessions stay on the developer’s Mac.
Planned for Teams
A common policy for the project
Enforced project-level supervision, shared agent playbooks, organization defaults, team billing, security review support, and a managed rollout across your Macs.
Questions worth settling early
- Can we limit teams to one agent?
- That is not the premise. Saggar is designed to let developers choose their agent while the project owns the supervision policy. If your organization needs an approved-provider list too, that belongs in the rollout conversation.
- Does Saggar send code through its own model service?
- No. Agents run through the CLIs and provider accounts your developers configure. Saggar organizes their local terminal sessions; it does not sit between an agent and its model provider.
- Are team policies available today?
- Not yet. Project-level policy enforcement, shared playbooks, team billing, and rollout support are planned Teams capabilities. We are talking to teams now so the controls fit real security work.
- What can we evaluate now?
- The Mac app is free. Your developers can run supported agents, manage worktrees and sessions, and use Saggar’s current per-session supervision controls before discussing a team rollout.