Name the packages in scope and read the plan before an edit.
Open the repository, say which packages are in play, and ask for a plan. Searches skip what your ignore files exclude, work with parts can split into sub-sessions, and every edit is a version.
Free for one person on your Mac, no card. Your model provider bills you directly.
What is in the app for you
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.
Worth it, in four lines
- What you get
- Package-spanning work with an explicit plan and file trail.
- Why it holds
- Project searches skip what your ignore files exclude, and an agent script can compare two versions of a file.
- How soon
- Open the repository and name the packages in scope.
- What you stop doing
- No copying context between an agent chat for each package.
Read this before you start
Made for
Engineers coordinating edits across related packages.
Engineers working across packages in a monorepo
Not yet for
Teams seeking distributed builds or shared compute scheduling.
In our own words
A loop over many files becomes one short script that returns only the answer.
The Package Map
Every line below is already in the plan. Nothing here is an extra you pay for.
- A plan that spans the packages in scopeincluded
- Sub-sessions offered for each part, up to four at onceincluded
- Searches that skip what your ignore files excludeincluded
- One script instead of fifty tool calls for repetitive workincluded
- A diff for every edit across packagesincluded
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
Project searches skip what your ignore files exclude, and an agent script can compare two versions of a file.
bandicot
- Asked
- Keep package-spanning agent work planned and inspectable
- Before it wrote
- It asked, and waited for your answer
- Files kept
- scriptversion kept
- historyversion kept
- projectversion kept
- Stands behind
- The /also command adds work to the plan without stopping the current work
- The /plan command researches and writes a session plan with checks on every step
- An agent script can compare two versions of a file
- Paid to Bandicot
- Free
- Model bill
- from your provider
Package-spanning work with an explicit plan and file trail.
One project holds the plan across packages. Ask for something with parts and Bandicot offers a sub-session for each, while the diffs land in one place.
A day with it
No copying context between an agent chat for each package.
First thing
The job lands
Every package gets its own chat, and the context you built for one has to be pasted into the next.
Mid-morning
You hand it over
One project holds the plan across packages. Ask for something with parts and Bandicot offers a sub-session for each, while the diffs land in one place.
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
Package-spanning work with an explicit plan and file trail.
Name the packages in scope and read the plan before an edit.
Free for one person on your Mac, no card. Your model provider bills you directly.