Hand students the setup file, not a walkthrough.
Put the providers, skills and settings for your demonstration in one setup file. Each person applies it on their own Mac and enters their own keys, and the exercise starts with a plan and an approval, not with configuration.
Free for one person on your Mac, no card. Your model provider bills you directly.
- What you get
- A repeatable demonstration setup with the keys kept out.
- Why it holds
- Setup files carry providers, skills and settings, and the timeline marks agent runs, edits and restores for the class to read.
- How soon
- Apply the setup file and enter each user's own keys.
- How much work
- No repeating the same configuration walkthrough before every exercise.
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 it does for this job
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.
Start in three moves
Apply the setup file and enter each user's own keys.
Name the folder and the job
Make class demonstration setup repeatable without bundling credentials.
lab-setup/It asks before it writes
Turn a vague request into an inspectable sequence of steps before tools begin changing the project.
Keep it, or put it back
Every changed file is recorded, and undoing a run puts its files back with one click.
What you bring
No repeating the same configuration walkthrough before every exercise.
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.
lab-setup/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 we say about it
An agent with write access is only useful if a mistake costs one click.
Lab Demo Setup
Every line below is already in the plan. Nothing here is an extra you pay for.
- A reusable setup file for providers, skills and settingsincluded
- Keys entered by each person, never carried in the fileincluded
- A plan written before tool work beginsincluded
- /council to seat two more models for a second opinionincluded
- A history slider with one step per versionincluded
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.
Hand students the setup file, not a walkthrough.
Free for one person on your Mac, no card. Your model provider bills you directly.