Free
- 1 profile
- no card
Change providers on a Tuesday afternoon.
When the model you prefer is unavailable, choose another connected model for the session, or a local one, and carry on in the same project. You make the choice; the notes, history and approvals stay where they were.
What changes
Now
The provider has a bad day and your project notes are in its chat app, so switching means copying context into a stranger.
With Bandicot
Model choice is separate from project state. Nothing switches for you and nothing is promised on uptime, but when you decide to move, the work does not have to.
Chat box or workspace
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.
Worth it, in four lines
- What you get
- Change the provider without rebuilding the project.
- Why it holds
- Hosted providers and local models work in the same project, and Versions leaves out ignored build output so history stays small.
- How soon
- Choose another connected model for the session.
- What you stop doing
- No moving project notes into another provider's chat app.
The receipt for one session
Hosted providers and local models work in the same project, and Versions leaves out ignored build output so history stays small.
bandicot
- Asked
- Keep the project intact while deliberately choosing a different provider
- Before it wrote
- It asked, and waited for your answer
- Files kept
- modelsversion kept
- historyversion kept
- projectversion kept
- Stands behind
- Hosted providers and local models can work in the same project
- Before downloading a model, Bandicot checks memory needs and disk space
- Versions follows .gitignore rules to leave out ignored build output, logs and caches
- Paid to Bandicot
- Free
- Model bill
- from your provider
Change the provider without rebuilding the project.
Model choice is separate from project state. Nothing switches for you and nothing is promised on uptime, but when you decide to move, the work does not have to.
Provider Choice Kit
Every line below is already in the plan. Nothing here is an extra you pay for.
- Connections to several providersincluded
- Local model alternatives from the one-click catalogincluded
- Durable project sessions that outlive any one modelincluded
- A version of every file editincluded
- 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.
Read this before you start
Made for
Developers who want a deliberate alternative to provider lock-in.
Developers keeping project work independent of provider availability
Not yet for
Teams seeking guaranteed uptime or automatic model failover.
Change providers on a Tuesday afternoon.
Free for one person on your Mac, no card. Your model provider bills you directly.