bandicot

Free

  • 1 profile
  • no card

Read the pipeline change before any data moves.

Ask for a plan, read it, then let the agent edit the pipeline code. Every edit is a version, restores preview first, and the tools you connect through MCP stay under the host's approval rules.

bandicoton your Macplan-readversion-filerestoremcp-tools-ownpipeline-trail/Data engineers maintaining…

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.

The Pipeline Trailjoinedplan-readversionrestoremcp-toolshistorytoolsprojectsessionspermissio…plan.mdnotes.mddraft.md

How the first run goes

Start from the pipeline repository you already maintain.

  1. Name the folder and the job

    Keep pipeline edits and tool calls traceable without promising data rollback.

    pipeline-trail/
  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.

Worth it, in four lines

What you get
Pipeline code changes with a visible plan and file history.
Why it holds
The host records tool work and versions agent-edited files, and restore and undo show what would change before they change anything.
How soon
Start from the pipeline repository you already maintain.
What you stop doing
No separating an agent's reasoning from its source edits.

Chat box or workspace

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.

The Pipeline Trail

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

  • A plan to read before the first editincluded
  • A version of every file the agent changesincluded
  • Restore that previews first and applies only after --yes on the command lineincluded
  • MCP tools for your own stack, under approval rulesincluded
  • 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.

Read the pipeline change before any data moves.

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