bandicot

New Mac, same setup, and no keys in the file.

Written for engineering enablement staff preparing new Mac setups.

Put the providers, skills and settings you want in one setup file and share it. Each developer applies it on their own Mac and types the keys at a hidden prompt, so the file never carries a credential.

Configuration travels in the file. Secrets stay with the person who owns them, and each Mac ends up with the provider list, the skills and the settings you meant.

bandicot

Max holds up to 25 profiles. Every plan has every capability. Your model provider bills you directly.

bandicoton your Macshareablekeys-enteredprofilesmodelnew-hire-setup/Engineering enablement staff…

From this to this

Now

Every new developer gets the same walk through the same settings, and the shortcut of pasting a key into a shared document is a risk nobody signed off on.

With Bandicot

Configuration travels in the file. Secrets stay with the person who owns them, and each Mac ends up with the provider list, the skills and the settings you meant.

What a chat box leaves to you

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.

  • One setup file for a whole team

    A setup file carries providers, skills and settings, so a second person lands on the same setup.

    Available now
  • Skills, plugins and MCP servers

    Install skills, plugins and MCP servers per project, with their tools under the same approvals.

    Available now
  • Profiles with their own memory

    Each person or role gets a profile with separate projects, memory and settings; profiles can nest.

    Available now
  • The /council command brings two more models beside the session’s model.

    /council seats two more models beside the session's own, the ones you name after it.

    Available now
  • Making room for a new model does not unload one that is answering.

    When a new model needs room, Bandicot unloads the one you used least recently, never one that is answering.

    Available now
  • Models opens with a shortlist for each job and your Mac’s memory.

    Models opens on a short list for each job, such as chat, code or speech, picked for your Mac's memory.

    Available now

The Onboarding Setup

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

  • A shareable setup file for providers, skills and settingsincluded
  • Keys entered at a hidden prompt, never stored in the fileincluded
  • Up to 25 profiles for the people you onboardincluded
  • A model shortlist for each job, picked for the Mac in front of youincluded
  • Priority supportincluded
MaxUp to 25 profiles$49.99 a month

Max holds up to 25 profiles. Every plan has every capability. 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.

Is this for you?

Made for

Enablement staff who want a consistent starting configuration.

Engineering enablement staff onboarding Mac-based developers

Not yet for

Teams seeking centralized device management or live shared projects.

A day with it

No walking each developer through the same settings by hand.

  1. First thing

    The job lands

    Every new developer gets the same walk through the same settings, and the shortcut of pasting a key into a shared document is a risk nobody signed off on.

  2. Mid-morning

    You hand it over

    Configuration travels in the file. Secrets stay with the person who owns them, and each Mac ends up with the provider list, the skills and the settings you meant.

  3. 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.

  4. Before you close the lid

    You read what changed

    A repeatable agent setup for each new Mac.

New Mac, same setup, and no keys in the file.

Max holds up to 25 profiles. Every plan has every capability. Your model provider bills you directly.