Bandicot is a native Mac workspace where people and AI agents work on the same projects. Agents ask before they write, every change becomes a version, and every turn shows the tokens and cost it spent.

Yes, for one person: Solo is free with every capability for one profile. Team is $8.99 a month for up to 3 profiles, Family $14.99 for up to 6, Business $49.99 for up to 25, and Enterprise starts at $50 for 26 profiles plus $1.92 per seat.

Does Bandicot reduce token costs?

It is built to, and it shows you every token either way. A frozen prompt prefix keeps caches warm, history is append-only, compaction runs only at thresholds and skills load on demand. No whole-task saving is claimed until the fixed-corpus measurement is published.

Can several people use Bandicot together?

Yes, on one Mac today: profiles keep each person's projects and memory apart, and a team roster puts agents next to people. Syncing a team across machines is in development.

Does the AI change files without asking?

No. Writes, commands and spend outside your permissions file wait for approval, and every file change is recorded so it can be restored.

Which models does Bandicot work with?

Hosted providers you connect, and local models. A pinned catalog of 8 small chat models for Apple Silicon Macs, from Gemma 3 270M to SmolLM3 3B, each checked against the Mac's GPU memory budget before download. Larger work goes to a hosted provider you connect. Remote providers receive the prompts sent to them.

Does Bandicot run automations?

Yes. Automations are agents that run on a schedule or on request inside a project, on your Mac while Bandicot is open, under the same approvals as a chat.

Does Bandicot claim SOC 2 or GDPR credentials?

No external certification is claimed. Read the privacy and security docs for the actual boundaries.

Is Bandicot the same as Bandicoot?

Yes. The brand is Bandicot, one o. Bandicoot is a common misspelling.

Chapter IIIWork · Available now

Versions and history

A version for every change an agent makes, with diffs, restore and undo of a whole run.

Available now. A current user-facing path exists within the stated scope.

Every change leaves a version

Every file an agent changes is recorded, with diffs, restore and undo of a whole run.

Files inside projects you enrol; restoring is itself recorded in the history.

Undo a whole run

When an agent run goes the wrong way, undo it as one step instead of reverting files by hand. Restoring is itself recorded, so history only grows.

History is not truth

A visible history does not make an answer correct. It makes the proposed work, the approved change and the next decision easier to question. It does not replace source control.