--- title: "Agents that work as a team · Frazer" description: "Run your own sessions, or give agents a standing job. A squad takes an objective with measured key results: a manager agent plans the work, workers run in their own sandboxes on the Frazer harness or a harness you choose, a verifier checks, and the accountable person approves the plan and what ships." url: https://frazer.ai/agents index: https://frazer.ai/llms.txt tokens: 3119 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # Agents that work as a team · Frazer **Agents** frazer.ai # Agents that work as a team. Inside your rules, on your servers. Run your own sessions, or give agents a standing job. A squad takes an objective with measured key results: a manager agent plans the work, workers run in their own sandboxes on the Frazer harness or a harness you choose, a verifier checks, and the accountable person approves the plan and what ships. Start from a preconfigured image; talk to them from any client. [Create an agent](https://frazer.ai/start?product=agents) [Read the agent docs](https://frazer.ai/docs/agents) `frazer agents create --template frazer/on-call` Frazer app Console Slack Teams Email Web widget Telegram Hermes Desktop VS Code · JetBrains · Zed OpenClaw apps MCP · API 00 · An agent squad at work Fig. 1 · product UI, demo organization *The squad platform-ops of the demo organization Acme: the objective Calm on-call by December with a key result and a guardrail, the manager ops-manager with an approved plan and the squad budget, a board of tasks in Ready, In progress, Review and Done, and a Needs a person column with a merge approval and a grant request.* Fig. 1: an agent squad at work, product UI with a demo organization. A **An objective, measured by Frazer** Key results come from real sources, with a guardrail beside each. Agents never write the numbers. B **A manager that cannot approve** It plans inside a plan a person approved. It can never approve, grant access or change budgets. C **A verifier on every result** Another model family, or the Reviewer, passes or rejects work at the exact commit, with proof. D **People stay in charge** Merges, production writes and grants wait for a person with step-up. Budgets stop work before spend. 01 · How a squad works Fig. 2 ## One objective in. Verified, measured work out. **Fig. 2** The squad loop, with the gates that bound it designed behavior Role May May never **Accountable person** Approves the objective and the plan, raises budgets, resumes stopped campaigns, receives escalations Is replaced by an agent for an approval **Approvers** Resolve Ask cards and grant requests, with step-up Approve from a chat message or a client token **Manager agent** Plans, assigns, reviews, re-plans inside the approved budget; hires and releases workers inside your hiring policy; writes standups and reports Approve, grant, change rules, budgets or its own hiring policy, buy servers, lift a quarantine **Worker agents** Claim tasks that fit their role in their own sandbox; delegate to sub-agents within limits; attach proof Hold more than min(own ceiling, manager’s grants, sponsor’s rights); treat another agent’s message as approval **Verifier** Passes or rejects results at the exact commit; three rejections escalate to the accountable person Verify its own work **Frazer** Runs the control loop and the measurer; enforces grants, nested budgets, lane caps and the kill switch; records every step Let an agent write a key result, or hold a stored credential 02 · Objectives and campaigns Fig. 3 ## Give agents an outcome. Frazer measures it, not the agents. An objective has key results read from real sources (incidents, deploys, CI, your tools) and a guardrail from a different source beside each. The manager turns it into campaigns that run in waves with their own budgets and kill switches. If a guardrail breaks, or nothing moves for three check-ins, the campaign stops and a person decides. **Fig. 3** From an objective to tasks on the board demo organization 03 · Agent images Fig. 4 ## Start from an image. Change what you need. Four Frazer tiers, or your own image layered on one. Packages and the harness are baked and cached; skills, tools, knowledge and models are an overlay applied at wake, so changing them needs no rebuild. Every image is built in an isolated builder, scanned, signed and promoted from dev to staging to prod. **Lite** No browser; Python, Node, git, the frazer CLI lite-1 · 0.5 vCPU · 1 GiB **Standard** Lite + headless browser and document tools std-2 · 2 vCPU · 4 GiB **Full** The devbox toolchain, Docker inside the VM, coding agents full-4 · 4 vCPU · 16 GiB **GPU** Full + CUDA; weights on volumes, never in the image gpu-l4 · 1 × L4 Same image family as CI runners and devboxes: an agent taking over a box session finds the same tools. ``` kind: AgentImage metadata: {name: acme/coding} spec: from: frazer/agent-full@2026.10.1 # a Frazer tier, or another image of yours harness: claude-agent-sdk@0.9.4 # or frazer-agent, openclaw packages: {apt: [protobuf-compiler], go: [golangci-lint@v2.6]} class: {default: full-4} warm: {pool: 1, snapshot: after-ready} overlay: # applied at wake, never baked skills: [acme/go-upgrade@3.1] mcpServers: [frazer, github, linear] knowledge: [acme-engineering] models: {main: balanced, subagents: fast} ``` ``` # Plan → ImageBuild in an isolated builder $ frazer agents images build acme/coding -f image.yaml # dev → staging → prod, moved by digest $ frazer agents images promote acme/coding@v24 --to prod ``` Terminal ``` $ frazer agents images build acme/coding -f image.yaml Plan isolated build · SBOM · scan · sign · smoke eval ✓ acme/coding@v24 · 0 fixable critical or high · signed $ frazer agents images promote acme/coding@v24 --to prod ``` **Fig. 4** An image spec and its promotion 04 · Any harness, one set of rules Fig. 5 ## Your harness or ours, inside. Same cell, same gates. Bring the agent framework your team already uses. Frazer runs it in a microVM per agent and keeps everything with authority outside: channels, model keys, tool tokens and secrets are reached through Frazer’s gateways, never stored where the agent can read them. **Frazer harness** default Frazer’s own agent engine, written in Rust, and the engine of the Frazer app: any model for each step, and the plan, execute and verify roles squads use. **OpenClaw** first-class Managed cells: one gateway per microVM per trust boundary, Frazer’s identity in front, our channel plugin, control UI never exposed, a security audit at every start. **Popular harnesses** certified Claude Code, Codex, Gemini CLI, GitHub Copilot, OpenCode, Hermes and more, each tested against a compatibility suite, with Frazer plugins for harnesses such as Hermes. Vendor harnesses run on your own vendor credential; your own harness runs through the runtime contract. **Fig. 5** What sits inside the sandbox, and what never does 05 · Bring your own client ## One session, wherever you are. Start in Slack, finish in your editor. Every client reads and continues the same sessions with one of three access levels: Chat, Drive (take over a terminal or browser) or Operate (pause, restart, edit). Approvals never travel through a client token or a chat message; they open in a signed-in Frazer surface with step-up. Client Chat Drive Operate Approve How **Console and Frazer app** Yes Yes Yes Yes Inbox, squads, sessions; step-up for approvals **Slack, Teams, email, web, Telegram** Yes No No opens Frazer business channels; unknown senders paired first **Hermes Desktop, CLI, TUI** Yes Yes Yes opens Frazer remote gateway per agent; 1-hour token **VS Code, JetBrains, Zed** Yes Yes No opens Frazer ACP through frazer acp; the Frazer extension **OpenClaw apps** Yes Yes No opens Frazer through Frazer’s proxy with your Frazer sign-in **MCP clients** Yes No No opens Frazer send\_message, list\_sessions, get\_status **Your code** Yes No Yes No event stream and REST; API key or OIDC 06 · In control ## Autonomy you can bound. And stop in one click. ### Grants Each agent is a principal with its own roles, tools and knowledge scopes; it acts for a person, never as them. ### Ask before Production writes, merges, secret access and outbound messages can require a person, with step-up. ### Budgets Task, campaign, objective, squad and project, each checked before the next call; nothing is spent past a cap. ### Limits By default 25 agents per person, 12 per manager, squads two levels deep, sub-agents two levels deep. ### Kill switch For a campaign, a wave, an agent or the whole organization; quarantine keeps the evidence. ### On the record Every step is traced and every write is a plan with an audit entry; memory is readable and editable. 07 · Templates ## Agents and whole squads. Each one a template you can edit. - ### Personal assistant Mail, calendar and reminders over Telegram, Slack or email. always-on · personal - ### On-call agent Reads alerts and deploys; restarts and rollbacks wait for you. always-on · team - ### PR shepherd Keeps pull requests moving: rebases, fixes CI, asks reviewers. triggered · team - ### Support triage Answers from your handbook; drafts replies for a person to send. always-on · team - ### Research agent Browses and reads, writes a sourced report to one channel. triggered · team - ### Coding agent From an issue to a draft pull request with proof. triggered · project - ### Squad manager Runs an objective with workers; reports every evening. squad · team - ### Overnight orchestration Works a signed goal overnight; morning report first. supervisor · team 08 · Pricing ## No seats. Pay while agents work. An agent costs runtime while it is awake and tokens when it thinks. Asleep, it costs only its storage. On your own servers the runtime is part of the server fee. [See every price](https://frazer.ai/pricing) Lite, Standard Shared fleet hosts: **$0.05** per active vCPU-hour + $0.004 per GiB-hour Full, on dedicated hosts **$0.075** per active vCPU-hour + $0.006 per GiB-hour; GPU agents add the fleet GPU price A dedicated host **$1.50** an hour for 16 vCPU, 64 GiB, 1-hour minimum; Lite and Standard agents on it pay no runtime Runtime, your servers **Included** in the server fee Suspended or asleep Snapshot and volume storage only Squads, objectives **No charge** · their budgets cap the meters Tokens Provider price + 5 %, or your own key at no markup Questions ## Agents, answered. Can I run my existing OpenClaw agent? Yes. OpenClaw is a first-class harness: Frazer runs it in a managed cell, one gateway per microVM per trust boundary, with Frazer’s identity in front and the control UI never exposed. `frazer agents import openclaw` brings over its agents, channels, schedules, skills and models; secrets are entered again into the credential broker, never copied. Can I run agents for my own customers, with their own wallets? Yes. Each of your customers becomes a sub-tenant with its own cells, channels, memory and a prepaid wallet with auto-recharge and invoices. You price the usage; Frazer adds no fee on top-ups and bills your project as usual. What can a manager agent never do? Approve, grant, change rules, budgets or its own hiring policy, buy servers or lift a quarantine. It plans inside a plan a person approved, its workers act with no more than its own grants, and no agent treats another agent’s message as approval. Where do my prompts, code and memory go? Are they used for training? They stay in the agent’s sandbox and its encrypted volume, on your servers or the Frazer fleet; memory is readable, editable and can be forgotten or exported. Model calls go through Frazer’s LLM gateway, which logs metadata only by default, offers zero data retention per project, and can block any route that would send your data to a provider that trains on it. Can agents run on my own servers and models? Yes. On your own servers each agent runs in its own microVM, and the runtime is part of the server fee. Models come through the LLM gateway: frontier models with your own key at no markup, or open models you run on your own GPUs. What happens when a squad hits its budget? Work stops before the spend, not after. Budgets nest (task, campaign, objective, squad, project) and each is checked before the next model or tool call; a campaign warns at 80 % and stops at 100 %. Only the accountable person can raise the budget or resume the campaign. ## Give your agents an objective. Keep the approvals. [Create an agent](https://frazer.ai/start?product=agents) [Read the agent docs](https://frazer.ai/docs/agents)