bandicot
bandicot

The agent edits source. You approve what reaches the board.

For embedded developers working on firmware repositories

Open the firmware repository with its own toolchain. Source edits are versions you can restore, and any command outside your permission rules stops for you, so a proposed flash is never consent.

allowed: write firmware-boundary/projectallowed: write firmware-boundary/agentsasks firstwritefirmware-boundary/historytaskFirmware Boundarywhyoutside your rulesaftera version is keptAllow onceDeny
Firmware Boundary

What is in it

  • Command approval by rule, in one permissions file
  • A version of every source edit, restored after a review
  • Durable work sessions
  • /also to add work to the plan without stopping the run
  • Free for one profile

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.

Command approval by rule, in one permissionsfilewaiting for youasks firstA version of every source edit, restoredafter a reviewagent at workfirmware-boundary/historyDurable work sessionskept as a versionfirmware-boundary/project

Worth it, in four lines

What you get
Firmware source edits with a clear command boundary.
Why it holds
Commands outside your permission rules stop for approval, and restoring from the timeline reviews the changes first.
How soon
Open the source repository without moving its toolchain, and add new work to the plan with /also while a run continues.
What you stop doing
No treating an agent's proposed hardware command as consent.

Three steps to a first result

Open the source repository without moving its toolchain, and add new work to the plan with /also while a run continues.

  1. Point it at the folder

    Separate reviewable source edits from commands that touch hardware.

    firmware-boundary/
  2. You answer, it carries on

    Turn a vague request into an inspectable sequence of steps before tools begin changing the project.

  3. Read what changed

    Every changed file is recorded, and undoing a run puts its files back with one click.

Checked, and labelled

Each line says whether it ships now or is still being built, so you never buy a promise.

  • Approval before writes

    An agent asks before it writes, runs or spends outside the rules you set; the rules live in one permissions file.

    Available now
  • A version for every change

    Every file an agent changes is recorded, with diffs, restore, undo of a whole run, and a slider that puts a folder back to any moment.

    Available now
  • A native host owns the work

    Bandicot's Zig host runs tools, sessions, approvals and versions around whichever model you pick.

    Verified core
  • Restoring from the timeline reviews changes and checks that the folder has not moved on.

    Put it back opens the usual review, which checks the folder has not moved on.

    Available now
  • Command-line restore and undo preview changes before applying them.

    Restore and undo show what would change first, and change files only when run again with --yes.

    Available now
  • The /also command adds work to the plan without stopping the current work.

    /also adds whatever follows it to the session plan without stopping the work in progress.

    Available now

Firmware Boundary

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

  • Command approval by rule, in one permissions fileincluded
  • A version of every source edit, restored after a reviewincluded
  • Durable work sessionsincluded
  • /also to add work to the plan without stopping the runincluded
  • Free for one profileincluded
Free1 profileFree

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.

A day with it

No treating an agent's proposed hardware command as consent.

  1. First thing

    The job lands

    An agent that can run commands can run the one that touches the hardware, and a confident message is not the same as your approval.

  2. Mid-morning

    You hand it over

    The boundary is a file. Edits to source flow freely and are recorded, and every command outside your rules waits for a yes from you.

  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

    Firmware source edits with a clear command boundary.

The agent edits source. You approve what reaches the board.

Free for one person on your Mac, no card. Your model provider bills you directly.