On your machine
For anyone using Claude Code or Codex.
- Routing rules from your own logs
- Sub-agents pinned to cheaper models
- Savings ledger and statusline
- doc2md for Office files and PDF
- Nothing leaves your machine
License
The Sprag CLI is open source, and free.
The CLI is released under Apache-2.0.
It runs on your machine, needs no account and sends nothing anywhere.
For the team features, get in touch.
Apache License 2.0
Applies to the Sprag CLI. The team features are not covered by this licence.
You can use the CLI at work, change it and share it. When you share a copy, keep the LICENSE and NOTICE files with it and mark what you changed.
- Personal and company use
- Changes and your own builds
- Sharing copies, with the license and notices kept
- A patent license from every contributor
The free CLI and the team features
The CLI is free under Apache-2.0 and works on its own on one machine.
For the team dashboard and prompt monitoring, get in touch.
Team dashboard
For organizations that want one view of AI use.
- Team dashboard with a 30-day chart
- A virtual office with an animal for each person
- Seat roster with each machine's status
- Team rules applied at session start
- Rollout with
sprag team join - Owner and admin roles, activity log
Prompt monitoring
For organizations that also review how prompts are written.
- Prompt capture, secrets redacted
- Nothing from before the policy was on
- Per-user prompt usage and 30-day trend
- Each user's prompt list with search
- Capture policy visible to every member
Off unless the organization turns it on.
Contact sales@sprag.ioWorks with your agents, however you connect them
The CLI and the team features read the same local session logs, so they work the same way in every setup below.
Agents
Anthropic Claude CodeOpenAI Codex
First party (1P)
Personal subscriptions (Claude Pro and Max, ChatGPT)Anthropic and OpenAI API keys
Third party (3P)
AWS Bedrock
Gateway model IDs are mapped back to the model, so spend and savings use the right price.
How a team gets started
- Get in touchEmail your organization name, the owner and admin emails and roughly how many people will use it to sales@sprag.io.
- We open your organizationSprag opens the organization and invites the owner and admins. They sign in at sprag.io/team with an email code.
- Invite the teamThe owner creates teams and shares the invite. Each member runs
sprag team joinonce; a machine that joins again keeps its seat.
The team features in 30 seconds
Recorded from the demo dashboard with sample data.
Questions
Is anything uploaded by default?
No. The CLI on its own sends nothing and never needs an account. A machine that joins a team sends one aggregate row per day plus its OS name and version, never prompts, paths or hostnames. sprag team status --show-payload prints exactly what is sent.
Who consents in a company rollout?
For an organization deployment, the organization's decision counts as the consent. Members can still see what is sent with sprag team status. SPRAG_NO_TEAM_SYNC=1 stops usage uploads, though the seat stays until an admin removes it, and sprag team leave wins over the env var.
Who decides on prompt capture?
Only an organization owner or admin. It is off by default, and the policy is visible to every member. Capture starts the moment it is turned on, with no history before it.
How are machines counted?
One machine that was active in the last 30 days, or paused with the upload switch, counts once. A person's second machine can be merged into the same seat.
Where is the data stored?
In Supabase, in the ap-northeast-2 (Seoul) region.
Can we stop using the team features?
Yes. Run sprag team leave on a machine, or tell us to close the organization. The CLI keeps working as before.