Does it guarantee compatible dependencies?

No. Review release information and run your checks. Recorded agent work is not a compatibility guarantee.

Can an agent change files without asking?

Writes, commands and spend outside your permissions file wait for approval. The model cannot grant itself permission.

Can I take back an agent's edits?

Yes. In projects you enrol in Versions, file changes are recorded. Restore a file or undo a whole run, with or without Git.

bandicotupgrade-trail/

Bump it, check it, and keep the trail of both.

Ask for an update plan in the repository you already have. The plan carries a check on every step, the manifest edits become versions, and a restore opens the usual review before it changes a file.

A plan with checks on every stepincluded
A version of every manifest and lockfile editincluded
The command results recorded with the sessionincluded
A reviewed restore that checks the folder has not moved onincluded
Tokens and cost for the whole upgradeincluded

plan: Free
profiles: 1 profile

todayFree

Start free See Versions

Free for one person on your Mac, no card. Your model provider bills you directly.

The plan, the manifest edits and the command results sit in one session. If the upgrade goes wrong, the way back is a reviewed restore.

What changes

Now

The lockfile changed, the tests changed, and the session that made both is a chat you closed an hour ago.

With Bandicot

The plan, the manifest edits and the command results sit in one session. If the upgrade goes wrong, the way back is a reviewed restore.

The result, the reason, the wait, the work

What you get: Dependency updates with an inspectable file trail.
Why it holds: The /plan command researches and writes a plan with checks on every step, and Versions captures agent edits in enrolled project folders.
How soon: Ask for an update plan in the existing repository.
What you stop doing: No separating manifest edits from the session that made them.

How the work gets done

Free Bandicot core
The free plan has every capability for one profile. Bring a provider key, a local model, or both; a provider's own bill stays yours.
A trusted harness around the model
Bandicot gives every agent a project, tools, a session that survives restarts, approvals, and a clear place to stop.
Projects that hold the work
Keep files, context, plans, and decisions with the project instead of losing them in a disposable chat.
Durable work sessions
Close the window, restart, or pick up from another of your Macs without turning the work into a brand-new conversation.

The receipt for one session

The /plan command researches and writes a plan with checks on every step, and Versions captures agent edits in enrolled project folders.

bandicot

Session in upgrade-trail/

Asked: Keep dependency update edits and their verification steps together
Before it wrote: It asked, and waited for your answer
Files kept: plan.mdversion kept
usageversion kept
projectversion kept
Stands behind: Restoring from the timeline reviews changes and checks that the folder has not moved on
The /plan command researches and writes a session plan with checks on every step
A restore stops before changing files if two names would collapse into one on your Mac

Paid to Bandicot: Free
Model bill: from your provider

Dependency updates with an inspectable file trail.

The plan, the manifest edits and the command results sit in one session. If the upgrade goes wrong, the way back is a reviewed restore.

The Upgrade Trail

Every line below is already in the plan. Nothing here is an extra you pay for.

A plan with checks on every stepincluded
A version of every manifest and lockfile editincluded
The command results recorded with the sessionincluded
A reviewed restore that checks the folder has not moved onincluded
Tokens and cost for the whole upgradeincluded

Free1 profileFree

Start free See Versions

Free for one person on your Mac, no card. Your model provider bills you directly.

No contract. Cancel any time from your account and keep the plan until the end of the period you paid for.

One working day, start to finish

No separating manifest edits from the session that made them.

First thing
The job lands
The lockfile changed, the tests changed, and the session that made both is a chat you closed an hour ago.
Mid-morning
You hand it over
The plan, the manifest edits and the command results sit in one session. If the upgrade goes wrong, the way back is a reviewed restore.
After lunch
A trusted harness around the model
Bandicot gives every agent a project, tools, a session that survives restarts, approvals, and a clear place to stop.
Before you close the lid
You read what changed
Dependency updates with an inspectable file trail.