Your methods travel. Your clients stay apart.

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.

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.

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.

Agents keep notes per project and profile that you can read, edit and forget.

Memory stays on your Mac with the profile it belongs to.

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.

Install plugins that add tools, with their boundaries visible before you turn them on.

Plugin tools run under the same approval rules as built-in tools.