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 · Verified core

Sessions

Sessions belong to the Mac app, not the window: each turn records intent, tool calls, approvals, changes and cost, and survives a closed window.

Verified core. Implemented and tested as a foundation; not necessarily a complete public journey.

The host owns the session

A session belongs to the native host and its project, not to a window. The window can close and reopen without losing accepted work.

This also means the website never implies a cloud agent: sessions run on your Mac.

A visible turn boundary

A turn separates intent, model output, tool calls, approvals and the resulting changes. A pending approval stays part of the session until you decide.

Every turn records its cost. Reports what the provider or local runtime exposes; a provider that hides usage shows a dash, never a guess.

What durability does not mean

Context limits and provider behavior still vary. An interrupted provider request cannot be made to finish, and not every model supports every tool.