People and agents, one workspace
What Bandicot is for: one workspace where people and agents work on the same projects, with approvals, versions and costs you can read.
Available now. A current user-facing path exists within the stated scope.
The idea
Agents are useful when they work inside your projects, and trustworthy when you can see what they did. Bandicot gives people and agents one workspace: the same files, the same history, the same rules.
Agents do the work inside your projects. You approve what lands and see what every turn spent.
Three things stay in view
Approvals. An agent asks before it writes, runs or spends outside the rules you set; the rules live in one permissions file.
Versions. Every file an agent changes is recorded, with diffs, restore and undo of a whole run.
Tokens and cost. Tokens, cache reads and cost are recorded per turn, session, profile and model, and the Habits tab shows the patterns.
Any model, one project
Switch between hosted providers and local models without rebuilding the project around one lab.
Local models are one option among providers. They suit private, light work; small models are not a match for frontier models. Remote providers receive the prompts sent to them and bill you directly.
Fewer tokens, by mechanism
The prompt prefix is frozen, history is append-only, compaction runs at thresholds, and skills load on demand. You see every token either way.
Status: In development. No whole-task saving is claimed until the fixed-corpus measurement lands; the mechanisms ship, the number does not yet exist.