bandicotgo-maintenance/

A work log for the Go tool, kept as you maintain it.

Open the tool's repository and describe the chore. The plan holds the scope, the ledger records the usage, and the agent's edits land as versions you can print as JSON from the command line.

A plan with checks on every stepincluded
Checks that run in a copy, without your secrets, and ask again if the checks file changesincluded
Tokens and cost for every sessionincluded
Versions of every agent edit, readable as JSON from the command lineincluded
Free for one profileincluded

plan: Free
profiles: 1 profile

todayFree

Open the repository Read about projects

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

Each chore gets a plan with checks on every step. The log of what changed and what it cost sits beside the work, not in a separate note.

What it takes to begin

No keeping a work log apart from the agent conversation by hand.

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.
go-maintenance/
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.

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.

What is true today

Each line says whether it ships now or is still being built, so you never buy a promise.

See what every turn spent
Tokens, cache reads and cost are recorded per turn, session, profile and model, and the Habits tab shows the patterns.
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.
Available now
The /also command adds work to the plan without stopping the current work.
/also adds whatever follows it to the session plan without stopping the work in progress.
Available now
The Versions command line can return JSON.
It prints plain text by default and JSON with --json.
Available now
Command-line restore and undo preview changes before applying them.
Restore and undo show what would change first, and change files only when run again with --yes.
Available now

Tool Upkeep Pack

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

A plan with checks on every stepincluded
Checks that run in a copy, without your secrets, and ask again if the checks file changesincluded
Tokens and cost for every sessionincluded
Versions of every agent edit, readable as JSON from the command lineincluded
Free for one profileincluded

Free1 profileFree

Open the repository Read about projects

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

The /plan command researches the repository and writes a plan with checks on every step, and a project can define its checks in bandicot.checks.json.

bandicot

Session in go-maintenance/

Asked: Keep agent maintenance work bounded to a Go tool's repository
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
The Versions command line can return JSON
Command-line restore and undo preview changes before applying them

Paid to Bandicot: Free
Model bill: from your provider

Small maintenance tasks with a visible scope and cost.

Each chore gets a plan with checks on every step. The log of what changed and what it cost sits beside the work, not in a separate note.

A day with it

No keeping a work log apart from the agent conversation by hand.

First thing
The job lands
The tool is small and useful, so maintenance arrives in small, endless chores, each one a new chat with no memory of the last.
Mid-morning
You hand it over
Each chore gets a plan with checks on every step. The log of what changed and what it cost sits beside the work, not in a separate note.
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
Small maintenance tasks with a visible scope and cost.

Questions before you start

Does it bring a Go toolchain?

Use your installed Go tools. Commands run on your Mac under the permission rules you set.

Can the agent change files without asking?

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

Do I need a paid plan?

The free plan has every capability for one profile. Paid plans add profiles, and hosted providers bill you separately.