Use cases
What people do with Bandicot: developers, teams, founders, writers, designers, families, companies, private work and agents that run while you are away.
Available now. A current user-facing path exists within the stated scope.
A solo developer
A solo developer gives Bandicot a repository, lets agents change the code, and keeps a version, a cost figure and an undo for every run.
The job: change a codebase quickly without losing track of what an agent touched. Agents read, search, edit and run commands in the open folder. Reads and edits inside it go ahead without a question, so the safety net is the history, not a stream of prompts.
A big change goes better with a plan first, and a failed run costs one click to put back. The tests, lint and build can run on every saved version without you starting them.
- Open the repository with
File›Open Project(see Open a folder as a workspace). - Turn on Versions for the folder before the first run (see Turn on Versions).
- For a change that touches many files, ask for
/planand read the steps before the agent starts (see The plan). - Set up your tests, lint and build once (see Set up checks in one click).
- If a run went the wrong way, choose
Undo this run(see Undo everything an agent run changed). - Read the cost of the run on the
Contextpage (see Read an agent's tokens and cost).
A small team
A small team starts a team in Bandicot, shares project folders and notes, and asks one another's agents questions in channels.
The job: work on the same projects without passing zip files and screenshots around. A team is a group of people whose Macs share encrypted channels, and messages go directly from Mac to Mac. The Mac of the person who starts the team admits the others.
Each person keeps their own agents and history on their own Mac. What you share is a folder with its saved versions, notes you choose to send, and the channel. The owner of an agent decides who may tag it and what a tag may do.
- One person starts the team (see Start a team).
- That person invites each teammate with a link (see Invite someone).
- Share the project folder from Versions so everyone has its history (see Share a folder with teams or friends).
- Send the notes the agent should know to the team (see Share notes with your team).
- Tag an agent in a channel with
@and its handle (see Tag an agent or an automation). - Start everyone the same way with one setup file (see One setup file for a team).
A founder or operator who is not a developer
A founder or operator describes the result in plain words, lets agents work in a folder, and reads what they did without needing to read code.
The job: get documents, research, plans and small tools made without learning a programming tool. You write a task in the prompt bar, or say it aloud. If you are not sure what you want, /grill asks you one question at a time about what you will notice, such as the flow, how it feels and what done means, and it never asks you to choose technology.
You stay in control through the cards. A card says what the agent wants to do and why, and you answer Allow once, Allow this agent, Allow this workspace or Deny. A card that nobody answers counts as a denial, never as a yes.
- Choose
New project, name it after the piece of work, and let Bandicot make the folder (see Start a project). - Type the task, or press
⇧⌘Dand say it (see Dictate a message). - If the task is vague, ask for
/grillfirst, then/plan(see The command list). - Answer the cards as they come (see Answer a permission card).
- Turn a job you repeat into an automation that reports back (see Create an automaton).
A writer or researcher
A writer or researcher keeps one project per piece of work, points the agent at source files, and keeps what it learns as notes that follow the work.
The job: gather sources, draft, revise and keep every draft. Mention a file or folder with @ and the agent reads it. The agent can also read the text of a web page address. For sources that sit behind a sign-in, lend the agent one Chrome tab at a time, and you type any password yourself.
Versions keeps each draft of each file, so you can name a good draft and come back to it. Memory keeps the facts the agent should not forget, such as your house style or a source list.
- Make a project for the piece and put your sources in its folder (see Projects and workspaces).
- Point the agent at a file or folder by typing
@and picking it (see Mention files and attach pictures). - Write down what must be remembered, such as tone or sources (see Add a note yourself).
- For a page behind a sign-in, lend the tab (see Lend a tab).
- Name a draft you like so you can find it again (see Name a version).
- Turn a recording into a transcript with
/transcribe(see Built-in commands).
A designer or marketer working with files
A designer or marketer keeps campaign files in a project folder, asks agents for pictures and edits, and can undo any run that spoiled a file.
The job: turn a brief into assets and keep control of the originals. Versions saves a version of each file in the folder every time it changes, so a bad pass never costs you the earlier file. /image makes, changes or enlarges a picture, and the Canvas is a board where you and the agent lay out cards, notes and tables.
When a task needs an app on your Mac, the agent can operate it with computer use, or work in an Agent Mac of its own so your own windows stay untouched.
- Open the campaign folder as a workspace (see Open a folder as a workspace).
- Turn on Versions before the first run (see Turn on Versions).
- Ask for the asset, for example with
/image, and lay the results out on the canvas (see The canvas). - If one pass spoiled a file, restore only that file (see Restore one file).
- Give the agent a screen of its own for app work (see What Agent Macs are).
A family sharing one Mac
A family uses one profile for each person, so every person gets their own agents, memory and automations on the shared Mac.
Pro holds 5 profiles on one account, and each extra is $1.99 a month. Free holds 1. Profiles do not share memory, and a profile can have its own password.
The job: let a parent, a partner and a child each work without seeing or changing the others' work. Open Home, choose Profile, and press Switch, add or sign out to change person. A profile can also be exported as a zip and moved to another Mac or account.
- Choose a plan that holds enough profiles: Pro, with extra profiles when you need them (see What the plans cover).
- Add each person as a profile (see Switch, add and manage profiles).
- Add each person who has their own devices with
Make an invite linkon the dashboard'sFamilycard (see Older family links, and a profile a plan gave you for an invite link). - Keep each person's sign-ins in their own Passwords vault (see The Passwords vault).
A company rolling it out
A company starts a company on the website, sets the rules every Mac follows, invites its people and gives IT one installer to push.
The job: put Bandicot on every Mac with the rules you need and no loose ends. Business includes 5 people, and each person more is a small monthly price. A company sees who is in it, what changed and how much was used, and it does not see the files, prompts or agent output on a person's Mac.
Rules such as Stay in the project folder, Always ask before acting and Keep voice samples on the Mac show on every Mac as set by the company. Sign-in can use Google or your own SAML login, and directory sync adds and removes people.
- Start the company and pay (see Start a company).
- Verify your domain and choose the rules (see Company rules).
- Invite people by email and set their roles (see Invite people and set roles).
- Give IT the Mac profile and the download (see Install on every Mac).
- Read what a company can and cannot see before you announce it to staff (see What a company can and cannot see).
Someone who wants private, local-only work
Someone who wants private work uses Bandicot on this Mac without an account and runs a model on the Mac, so prompts never leave the machine.
The job: work on files that must not go to a provider. On the sign-in screen, Use on this Mac opens Bandicot with no account. A model you download runs without a network, and a prompt sent to it stays on the Mac.
Be honest about the trade: small models are not a match for the largest hosted ones, and a hosted provider you connect later receives every prompt, file excerpt and tool result a turn sends to it. Choose per project which one you use.
- On the sign-in screen, choose
Use on this Mac(see Do I need an account?). - Press
⇧⌘M, pick a model underBest for this Macand pressDownload & use(see Pick and download a local model). - Read the fit label before you download (see The fit check).
- Read exactly what leaves the Mac in each case (see What leaves your Mac).
- Keep keys and passwords in the vault, never in a prompt (see Secrets and passwords).
Someone who wants agents working while away
Someone who is away sets an automation to run on a schedule, keeps the Mac awake for it and reads the report when they are back.
The job: have the nightly check, the weekly summary or the long task done by morning. An automation wakes on a schedule, hands the work to your agents and leaves a report. With Keep working when Bandicot is closed on, it runs with no window open while the Mac is awake.
A MacBook can keep working with the lid closed. Nobody can wake a sleeping Mac from the internet, so work sent to a sleeping Mac waits and runs when it wakes. Another Mac of yours that holds the same project can cover its schedules.
- Create the automaton and add a schedule (see Create an automaton and Add a schedule).
- Turn on the
Always oncard (see Always on). - On a MacBook, keep it working with the lid closed (see Keep working with the lid closed).
- Let a second Mac cover it (see Run automations across your Macs).
- Read
Last reportwhen you are back (see Last report and runs).
Someone who compares models
Someone who compares models connects more than one provider, runs the same task on each and reads the cost and the result side by side.
The job: pick the model that is good enough for the price. You can change the model between two messages in the same agent, and the agent shows a card that says it is now on the new model and that the thread and workspace carried over. You can also start several agents, each on its own model, and watch them together on the Wall.
/council lets you and two other models you name work a question over together. In AI Gateway, Compare models on these jobs prices the real questions Decisions asked on each model, so you see what a switch would cost.
- Connect two providers (see Connect a model).
- Run the same task in two agents, each on its own model (see Choose the model an agent uses).
- Open both on the Wall (see Watch many agents at once: the Wall).
- Compare
Agent costandThis turnon theContextpage (see Read an agent's tokens and cost).
Questions
Do I need to be a developer to use Bandicot?
No. You describe the work in plain words, and /grill can ask you what you will notice before anything is built. You read what the agent did in the transcript and answer cards when it needs you. A developer gets more from the Checks and Versions pages, but nothing in the app requires code.
Which of these needs a paid plan?
Free has every capability of the app for one profile and needs no card. Several profiles need Pro, a family needs Family, and a company needs Business. The plans and billing page lists them. Your model provider bills its tokens separately.
Can I use Bandicot with no internet?
Yes, with a model you have already downloaded. Once a local model is on the Mac it runs without a network, and so do the parts of Bandicot that use only local models. A hosted model needs a connection to its provider.
Where do I start if my job is not listed?
Start with Get started, which takes you from install to a first task. Then read How-to guides for worked paths, and Best practices for habits that apply to any job.