Prepare the release by checklist. Publish by hand.
Load the release skill in the project that holds the files. The agent walks the checklist, every command follows your approval rules, and allowing a risky command remembers only that exact line.
Free for one person on your Mac, no card. Your model provider bills you directly.
- What you get
- Release preparation with repeatable steps and explicit gates.
- Why it holds
- Skills hold the method, commands follow your approval rules, and allowing a risky command remembers only that exact line.
- How soon
- Load the release skill in the project that holds the files.
- How much work
- No retyping the preparation checklist into each new chat.
Same question, different tool
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.
What we say about it
An agent with write access is only useful if a mistake costs one click.
Release Preparation
Every line below is already in the plan. Nothing here is an extra you pay for.
- A release skill that loads on demandincluded
- Command approval by rule, one exact line at a timeincluded
- Git commands that can lose work stop for an approval cardincluded
- A version of every release file, with a restore that previews firstincluded
- A plan you can extend with /also mid-runincluded
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.
Try it with the door open
No contract. Cancel any time from your account and keep the plan until the end of the period you paid for.
Your files stay yours
The agent does its work in your own folders on your Mac, so the files are yours to keep.
Start without paying
The free plan has every capability for one profile, and asks for no card.
Put a run back
Every changed file is a version, so a run you regret is one click from undone.
Everything on one slip
Skills hold the method, commands follow your approval rules, and allowing a risky command remembers only that exact line.
bandicot
- Asked
- Keep release preparation repeatable without giving agents publishing consent
- Before it wrote
- It asked, and waited for your answer
- Files kept
- plan.mdversion kept
- historyversion kept
- projectversion kept
- Stands behind
- The /also command adds work to the plan without stopping the current work
- A restore stops before changing files if two names would collapse into one on your Mac
- Command-line restore and undo preview changes before applying them
- Paid to Bandicot
- Free
- Model bill
- from your provider
Release preparation with repeatable steps and explicit gates.
The method lives in a skill, the gate lives in your permissions file, and approving one risky command never approves its cousins.
Is this for you?
Made for
Release managers who separate preparation from publishing.
Release managers preparing checklists and release files
Not yet for
People seeking an unattended deployment platform.
Prepare the release by checklist. Publish by hand.
Free for one person on your Mac, no card. Your model provider bills you directly.