Which assumption drove that result? It is written down.

Written for economists revisiting empirical working papers.

Open the permitted analysis and text folder and record the model's assumptions as project notes. Usage per session is on the ledger, a large project is fine, and every edit to the paper or the code is a version.

Assumptions live in readable notes beside the paper. The agent works in the real files, you check the method with your own tools, and the history shows what changed and when.

bandicot

Open the paper Explore projects

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

Same work, different week

Now

The result changed between drafts, and the assumption that moved it is somewhere in a month of chat threads.

With Bandicot

Assumptions live in readable notes beside the paper. The agent works in the real files, you check the method with your own tools, and the history shows what changed and when.

A day with it

No reconstructing the model assumptions from old chat threads.

First thing
The job lands
The result changed between drafts, and the assumption that moved it is somewhere in a month of chat threads.
Mid-morning
You hand it over
Assumptions live in readable notes beside the paper. The agent works in the real files, you check the method with your own tools, and the history shows what changed and when.
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.
Before you close the lid
You read what changed
Keep the working paper's assumptions with its files.

What you get, and what it asks of you

What you get: Keep the working paper's assumptions with its files.
Why it holds: Readable project notes and versioned edits preserve working context, and a Versions project holds a very large number of files.
How soon: Open the permitted analysis and text project folder.
What you stop doing: No reconstructing the model assumptions from old chat threads.

In our own words

An agent with write access is only useful if a mistake costs one click.

Readable project notes and versioned edits preserve working context, and a Versions project holds a very large number of files.

A chat box, and then this

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.

See what every turn spent
Tokens, cache reads and cost are recorded per turn, session, profile and model, and the Habits tab shows the patterns.
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
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
One Versions project can hold up to 100,000 files.
Saving a version of one still takes a few hundredths of a second.
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
A restore stops before changing files if two names would collapse into one on your Mac.
A Mac’s disk usually treats README.md and readme.md as the same name.
Available now

Working Paper Desk

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

Readable project notes for assumptions and specificationsincluded
A version for every agent edit to code or textincluded
Tokens and cost for each sessionincluded
A local model or a hosted provider, chosen per projectincluded
Saved git history brought back as it wasincluded

Free1 profileFree

Open the paper Explore projects

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.

What people ask first

Does it reproduce or validate my findings?

No. Use your own tools and methodology to check results. The workspace keeps context and records the agent's work.

Where do my prompts go?

A local model runs on your Mac. A hosted provider receives the prompts you send it and bills you directly. Choose the route the work permits.

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.