Runbooks an agent can run, and you can audit.

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.

Let an agent inspect, plan, and use tools inside the project you selected instead of an unbounded chat transcript.

The host controls tool calls, cancellation, permissions, and the final recorded result.

Connect MCP servers to a project when the work needs their tools or data.

MCP tools are called through the host, so approvals and versions cover them too.

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.

Turn a vague request into an inspectable sequence of steps before tools begin changing the project.

The harness tracks dependencies and blocked steps. A conversation alone does not silently advance execution.