Fermata

Introducing Fermata

A research notebook designed by scientists, for scientists. Fermata keeps your ideas and your work at the center, with thoughtfully integrated AI tools that help you refine your research during every step of the scientific method.

Good science shouldn’t be rushed. Take your time to do it right, with Fermata.

getfermata.app
1 · Before you start

You need three things

Fermata does its thinking through an agent that runs on your Mac under your own account: Claude Code with a Claude account, or OpenAI's Codex with a ChatGPT account. Set one up first and everything else is a double-click.

A Mac with Apple silicon

M1 or later. Check under Apple menu › About This Mac › Chip.

A Claude or ChatGPT account

For Claude Code, a Claude Pro or Max plan or an Anthropic Console account. For Codex, a ChatGPT plan that includes Codex. Fermata's runs count against this account.

Claude Code or Codex, signed in

The command-line tool claude or codex. Install one with the steps below if its --version doesn't work in Terminal.

Install Claude Code

Open Terminal (press ⌘ Space, type Terminal, press Return) and paste:

curl -fsSL https://claude.ai/install.sh | bash

Then start it once so it can sign you in. Follow the browser prompt, then type /exit.

claude

Already have it? Make sure it's current

Fermata is tested against recent versions of Claude Code. An old one still works, but each run shows a warning.

claude update
claude --version

The version should print as 2.1.250 or newer.

2 · Install and open

Download, drag, open

Download Fermata from getfermata.app. You get a file ending in .dmg.

01

Download the .dmg

Open it from your Downloads folder.

02

Drag to Applications

Updates only work from the Applications folder. If you skip this, Fermata offers to move itself there.

03

Double-click to open

It is signed and notarized by Apple, so it opens without a warning. Startup takes a few seconds.

04

Add your ORCID (optional)

Click your initials, top right, to open Settings, and paste your ORCID iD under Profile. Fermata learns your field from your publications through OpenAlex (no account needed), so it won't ask you basics.

No sign-up inside Fermata.The app sets you up as its user on first launch, using the name from your Mac. Your projects and runs are stored on your computer.
Using Fermata
3 · Your first run

Five steps, and you hold the pause

A run is one conversation about one question. Fermata never starts real work on its own. It waits for your go-ahead at step 3, and you can pause it at any point after that.

You

1. Ask

Type a question into the box on the home screen. That creates a project and its first run.

You + Fermata

2. Answer its questions

For a research question it asks one thing at a time and builds a summary. A simple question just gets an answer.

You

3. Press play

When the summary is ready, the play button starts the work. It is in the header and on the card that says it has enough.

Fermata

4. Directions run

One direction per idea, side by side. Each one reads, runs experiments and records findings. A checker tries to break every finding.

Fermata

5. Read the conclusion

Every run ends with one, even a paused one: the answer so far, what each direction found, what's open, and the next step.

Your moveFermata's move
Step 2, up close
What should this run settle? Say it as precisely as you can.
Whether the surface-code threshold shifts when the noise is biased toward Z errors.
What do you already have to go on?
A paperSimulation dataNothing yet

Tap an option or type your own answer. "None" is a fine answer and won't be asked again. To change the summary later, use the pencil in the header.

Tips for a good first question

"Does adding a learning-rate warmup change final accuracy for small transformers on our dataset, or only how fast they get there?"

  • Ask about something you'd like to decide, not just a topic. Fermata works best when there's a real uncertainty to resolve.
  • Mention what you already have: a dataset, a paper, a failed attempt. It will ask if you don't.
  • Start small. A first run that finishes in an hour teaches you more about the app than a big one that runs all day.
4 · What it shows you along the way

Nothing it assumes is hidden

From the first question to the conclusion, the panel on the right of every run shows what Fermata is taking for granted, what it still doesn't know, and where the work could go. Check it as the run goes. Correcting an assumption early is cheaper than correcting a conclusion.

Open questions 2

Does the decoder's run time grow with bias, or stay flat?
Is Z-bias above 100 realistic for our hardware?

Where this could go 3

AThreshold vs. bias, standard decoder›
BTailored decoder for biased noise›
CCompare with published thresholds›

Assumptions 2

Measurement errors are unbiased.✎
Distances 3 to 11 are enough to read a threshold.✎

Assumptions

What Fermata is taking as given so it can proceed, in plain words. Each change is marked new, revised, merged or dropped, so you can see what moved since your last answer. Click one to question it in the chat, or edit its words.

Open questions

What isn't known yet and would change the answer. Click one to raise it in the conversation. A question that blocks a direction is pinned above the feed instead, so you can't miss it.

Where this could go

The directions Fermata proposes, each with its hypothesis and what it would take. Open one to talk it through and shape its plan before you press play. Once running, each has its own card under Directions.

Catch upSummaryPlanDirectionsFindingsAssumptionsFiles

Tabs down the right edge of the run. Catch up retells a long run as a short list of scenes. Files holds everything the run wrote or read.

While it runs

You see the thinking

  • Assumptions, open questions and proposed directions
  • Each direction's plan and its latest step
  • Questions waiting for you, pinned and amber
  • Each finding as it is recorded
When it finishes

You get findings and insights

  • Findings: each claim with where it holds, its limits, its evidence, and whether the checker could break it
  • Insights: what tends to hold across several findings and runs. In a project's Findings, use Look across the findings to draw them out
  • A conclusion card at the end of the feed
5 · Taking notes

Select any words to make a note

Anywhere in a run's conversation, or on a direction's plan, select text with your mouse. A small menu appears with three choices. You can also point at a figure.

Under Z-biased noise the threshold rises from about 1% to roughly 4.5% at a bias of 100, provided the decoder knows the bias.

Break it down"Bias of 100" means Z errors are a hundred times likelier than X or Y errors. The higher threshold only appears when the decoder is told this.
11 annotation waiting under the message box: "check this against our device's numbers"

Add to chat

Marks the words with a number and holds them under the message box, with an optional comment of your own. They go with your next message, so you can point at exactly what you mean. Select several passages to gather them into one message.

Break it down

Writes a short note beside the words, explaining them as this conversation means them. The words keep a dotted underline. Click it to open the note again.

Quick chat

Ask one question about the selection and get one answer in a note beside it. For a follow-up, use the message box.

Notes are private and temporary.Break it down and Quick chat notes don't change the run, and Fermata's agent never sees them. They last until you quit the app. Copy anything you want to keep.

6 · The run screen

Where things are

1 2 3 4 5
1
Play and pause. Pause holds every direction and writes a conclusion of where things stand. Resume restarts what was held.
2
The feed. Decisions, outcomes and findings, in plain sentences. The list icon in the header shows the detail: tool calls, experiments, checks.
3
A pinned question. A direction is waiting for you. Tap an option or write your own answer.
4
Directions. Click one to see its plan, experiments and files, or to talk to it directly. Amber means it's waiting for you.
5
Message box. Talk to Fermata at any time. While it's working and the box is empty, the send button becomes Stop.
runningneeds youdone
7 · Everyday moves

Things you will do often

Run · message box

Talk while it works

Write at any time. Your message waits in a queue above the box and is read at the next turn. You can delete it until it's read.

Run · message box

Stop vs. pause

Stop ends the current turn only. Your next message carries on. Pause in the header also holds every direction until you resume.

Run · right panel

Correct an assumption

Open the Assumptions tab and edit the one that's wrong, or click it to challenge it in the chat. Fermata reconciles the list on its next turn.

Header · Findings

Review and share a finding

Open a finding to see its claim, where it holds, its limits and its evidence. Share it with the project when you're happy with it.

Header · Capabilities

Connect a service or skill

Paste a URL for a literature service or a skill. It installs, checks and turns on in one step, and is available in every project.

Header · Update arrow

Update the app

When a new version is out, an arrow appears in the header. Click it. Fermata downloads, swaps itself and reopens where you were. Your runs are kept.

Summary
What the run is trying to settle, built from your answers.
Direction
One line of investigation, usually one idea or hypothesis.
Finding
A claim with its evidence and limits, tested before it counts.
Coordinator
The agent you talk to. It plans the run and starts the directions.
8 · When something goes wrong

Quick fixes

A run never starts, or says it can't find Claude Code or Codex

Fermata looks for claude on your PATH and in ~/.local/bin, and for codex on your PATH and inside the ChatGPT app. Check in Terminal that claude --version (or codex --version) prints a version and that the tool opens without asking you to sign in. Check too that Settings › Models › Agent names the one you set up. Then quit Fermata with ⌘ Q and open it again.

The run shows a version warning

Your Claude Code or Codex is outside the range Fermata was tested with. The run still works. Run claude update, or the Codex install command again, to clear the warning.

An update fails

Fermata can only update itself from the Applications folder. Accept its offer to move there, or drag it there yourself and open it again.

I quit the app in the middle of a run

Nothing is lost. When you open Fermata again, it resumes each run that was working and restarts the directions that stopped with it.

It keeps asking questions instead of working

It is building the summary. Answer "none" or "that's enough" to skip a question, or press play as soon as the card says it has what it needs.

Something else is broken and I want to report it

Open Settings, note the version, and click Open logs. Send the version, what you did, and the most recent log file to the person who gave you Fermata.

What it can do on your Mac

Fermata's agent runs through your Claude Code or Codex. It uses that tool's settings and permissions, and it can run commands on your computer the way the tool does. Experiments that go on the record run in a separate sandbox.

What it sends, and where

Your questions and files go to Claude or OpenAI under your account, like any Claude Code or Codex session. Runs and findings are stored on your Mac. Usage data counts clicks and screens, never what you type, and you can turn it off in Settings › Usage data.