bandicot

Try the redesign. Keep the component you started from.

Ask for a plan, let the agent edit your interface code, and review the diff in Bandicot. Versions keeps what you had, so the experiment costs nothing and the old component is one restore away.

Now

You copy a component to Button.old.tsx before every experiment, and by Friday the folder is a museum of files nobody dares delete.

With Bandicot

sessionyouA plan to read before any editplan- A diff and a restore for every…- A timeline that marks agent runs…readinterface-iteration/plan.mdaskwrite interface-iteration/modelsyouallow oncedoneversion kept

Experiment in the real files. Every edit is a version with a diff, the timeline shows which dots were the agent and which were you, and restoring is a reviewed step, not a gamble.

Three steps to a first result

Open the interface project, ask for a plan, review the diff.

  1. Say what the job is

    Review agent edits to interface code without losing the previous version.

    interface-iteration/
  2. It works, you stay in charge

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

  3. Take the result or undo the run

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

What you get, and what it asks of you

What you get
Try an interface change and keep the code you started from.
Why it holds
Versions records file edits in enrolled projects, with diffs and restore, and large files such as design assets are saved and put back piece by piece.
How soon
Open the interface project, ask for a plan, review the diff.
What you stop doing
No copying components to a backup file before every experiment.

What is true today

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

  • 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
  • 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
  • Any model, one project

    Switch between hosted providers and local models without rebuilding the project around one lab.

    Available now
  • You can bring saved git history back to the project.

    The saved history goes back into the project exactly as it was, with your commits, branches and tags.

    Available now
  • 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
  • Versions shows the size of a very large file instead of its text.

    A file over 128 MB is saved and put back piece by piece, up to 16 GB.

    Available now

Is this for you?

Made for

Frontend engineers who review the code an agent changes.

Frontend engineers building web interfaces

Not yet for

People looking for a hosted visual site builder.

Interface Workbench

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

  • A plan to read before any editincluded
  • A diff and a restore for every file the agent changesincluded
  • A timeline that marks agent runs apart from your own editsincluded
  • Large design assets saved and restored piece by pieceincluded
  • The model of your choice for each sessionincluded
  • 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 copying components to a backup file before every experiment.

  1. First thing

    The job lands

    You copy a component to Button.old.tsx before every experiment, and by Friday the folder is a museum of files nobody dares delete.

  2. Mid-morning

    You hand it over

    Experiment in the real files. Every edit is a version with a diff, the timeline shows which dots were the agent and which were you, and restoring is a reviewed step, not a gamble.

  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

    Try an interface change and keep the code you started from.

Straight answers

Does it replace checking the page in my browser?

No. Review and test the interface in your own browser and tools. Bandicot records the agent's file work.

Can the agent change my components without asking?

Writes, commands and spend outside your permissions file wait for approval. The model cannot grant itself permission.

Can I take back an agent's edits?

Yes. In projects you enrol in Versions, file changes are recorded. Restore a file or undo a whole run, with or without Git.

Try the redesign. Keep the component you started from.

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