Free Bandicot core
Available nowSolo is free with every capability for one profile. Bring a provider key, a local model, or both; a provider's own bill stays yours.
Paid plans add profiles to an account. Bandicot does not resell model tokens.
For teams that are rarely in one room
A Bandicot setup file carries providers, skills and settings. A new teammate drops it on the window, types their keys at a hidden prompt, and lands where everyone else is.
Solo is free for one profile · providers bill you directly
The problem
Every remote teammate configures their AI tools differently, so the same request gives different results on different machines.
The promise
One setup file, applied the same way everywhere. Keys stay out of the file. Syncing projects across machines is in development, and we say so.
The picture
The plan
Every card names its status. Available now means you can use it today; in development and direction mean it is not shipped yet.
Solo is free with every capability for one profile. Bring a provider key, a local model, or both; a provider's own bill stays yours.
Paid plans add profiles to an account. Bandicot does not resell model tokens.
Bandicot gives every agent a project, tools, a session that survives restarts, approvals, and a clear place to stop.
The native host owns execution facts. The model proposes work; it does not certify a write, spend, or success.
Keep files, context, plans, and decisions with the project instead of losing them in a disposable chat.
A session is anchored to a project boundary so a pivot starts from an intentional context, not accidental history.
Close a client or reconnect after a pause without turning the work into a brand-new conversation.
The host records session state and clients reattach to it. A browser view does not become the source of truth.
When work can change files or systems, Bandicot makes the decision visible before the effect lands.
The approval boundary fails closed when an action is not allowed. The model cannot grant itself permission.
Give each person or role a profile with its own projects, memory and settings.
Profiles share one Mac and one account. Your plan sets how many profiles the account holds.
Keep a legible trail of the turn and its effects so a pivot can be reviewed instead of guessed at.
The host treats state changes as recorded events. Reverting is itself part of the history.
Package a way of working once, and every agent in the project can use it.
Skills load on demand, so an unused skill costs no tokens in the prompt.
See the tokens, cache reads and cost of every turn, per session, profile and model, and the habits behind them.
Bandicot reports what the provider or local runtime exposes. A provider that hides usage shows a dash, never a guess.
The direction is to pick up a project from another surface without forking its authority.
Cross-surface handoff is being built; this campaign layer does not claim a finished phone or device-sync product.
People on different Macs working from one shared project and roster.
Today a team's roster and agent runs live on one Mac. Syncing across machines is in development.
For you if
Distributed teams who want the same agent setup everywhere.
Not for you if
Teams that need live editing across machines today: that is in development.
The offer
Team · $8.99 a month · up to 3 profiles
No contract. Cancel any time from your account and keep the plan until the end of the period you paid for.
Solo is free for one profile · providers bill you directly
Left off this page
Bandicot does these too, but they are not why this page exists. Anything marked in development or direction is not shipped yet.
Questions
Not yet. Team sync across machines is in development. Today the setup file keeps everyone's configuration the same.
No. Each person types their keys at a hidden prompt; the file never stores them.
$8.99 a month for up to 3 profiles in one account.
Same Setup
Solo is free for one profile · providers bill you directly
Explore another angle
Solo is free for one profile · providers bill you directly
Start free