A refactor is a plan and a run you can take back.
Describe the boundary and read the proposed steps. Several edits to one file land as a single step that still gets its own version, and you can undo the run, or keep the good half of an edit.
Free for one person on your Mac, no card. Your model provider bills you directly.
A chat box, and then this
A chat box answers. Bandicot does the work in your folders, asks before it writes, and keeps a version of every change.
In a chat boxA model and a text box, with no gate before a write.
In BandicotA trusted harness around the modelBandicot gives every agent a project, tools, a session that survives restarts, approvals, and a clear place to stop.
In a chat boxA conversation. The files stay wherever you copied them from.
In BandicotProjects that hold the workKeep files, context, plans, and decisions with the project instead of losing them in a disposable chat.
In a chat boxClose the tab and the thread is somewhere in a list.
In BandicotDurable work sessionsClose the window, restart, or pick up from another of your Macs without turning the work into a brand-new conversation.
In a chat boxIt suggests an edit and you apply it yourself, so there is no gate to read.
In BandicotA human gate for writesWhen work can change files or systems, Bandicot makes the decision visible before the effect lands.
Same work, different week
Now
You cut a backup branch just to see whether an agent's restructuring is worth keeping, and the diff is too big to read in one sitting.
With Bandicot
The run is the unit. Review it as steps, keep what is good, put back what is not, and let your own checks decide whether behaviour held.
Three steps to a first result
Describe the boundary and review the proposed steps.
Point it at the folder
Review a refactor as a plan and a recoverable run.
structural-change/You answer, it carries on
Turn a vague request into an inspectable sequence of steps before tools begin changing the project.
Read what changed
Every changed file is recorded, and undoing a run puts its files back with one click.
What it takes to begin
No manual backup branch just to inspect an agent experiment.
A Mac
Bandicot is a Mac app. The work happens in your folders, on your machine.
A folder
Keep files, context, plans and decisions with the project instead of losing them in a disposable chat.
structural-change/A model
A local model, an OpenAI-compatible endpoint, or a hosted provider you sign in to. The provider bills you directly.
Free
For one person on your Mac. Every plan has every capability.
What is true today
Each line says whether it ships now or is still being built, so you never buy a promise.
- Available now
A version for every change
Every file an agent changes is recorded, with diffs, restore, undo of a whole run, and a slider that puts a folder back to any moment.
- Available now
Approval before writes
An agent asks before it writes, runs or spends outside the rules you set; the rules live in one permissions file.
- Verified core
A native host owns the work
Bandicot's Zig host runs tools, sessions, approvals and versions around whichever model you pick.
- Available now
Restoring from the timeline reviews changes and checks that the folder has not moved on.
Put it back opens the usual review, which checks the folder has not moved on.
- Available now
You can bring saved git history back to the project.
The saved history goes back into the project exactly as it was, with your commits, branches and tags.
- Available now
A restore stops before changing files if two names would collapse into one on your Mac.
A Mac’s disk usually treats README.md and readme.md as the same name.
The Refactor Review
Every line below is already in the plan. Nothing here is an extra you pay for.
- A plan with its steps to read firstincluded
- A diff for every edit, several edits in one file shown as one stepincluded
- Undo for a whole run, or choose parts of a file to keepincluded
- Restores that check two names will not collapse into one on your Macincluded
- Free for one profileincluded
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.
What a session leaves behind
Versions records enrolled project edits, supports undo for a whole run, and a multi-edit step still gets a version you can return to.
bandicot
- Asked
- Review a refactor as a plan and a recoverable run
- Before it wrote
- It asked, and waited for your answer
- Files kept
- plan.mdversion kept
- agentsversion kept
- projectversion kept
- Stands behind
- Restoring from the timeline reviews changes and checks that the folder has not moved on
- You can bring saved git history back to the project
- 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
A structural change with a plan and a way back.
The run is the unit. Review it as steps, keep what is good, put back what is not, and let your own checks decide whether behaviour held.
A refactor is a plan and a run you can take back.
Free for one person on your Mac, no card. Your model provider bills you directly.