# A lab notebook your script fills in

Every run arrives with its parameters, table and plot. Your chapters link to the run behind each claim.

## At a glance

- **For:** PhD and master’s students.
- **You keep:** A Thesis folder with a thread per chapter, an Experiments thread and a Supervisor thread shared with your supervisor.
- **Files itself:** At the end of each run, your analysis script adds a note with the parameters, a results table and the plot.
- **The moment:** Writing the methods chapter in May, every run has its date, parameters and plot, and each claim links to the run behind it.
- **Plan:** Pro · From USD 7.99 a month. 14 days free, no card. Writing alone is free in this browser. The script, sync and sharing need Pro.

## Before

One eighty-page document, a folder of plots called final_v3_new.png, and your supervisor’s comments spread across email and PDF margins. Six months later nobody remembers why the threshold is 30 °C.

## Why a thread, not a document and a folder of plots

### Each run is a dated note

The script can only add, never change. Version history keeps your own edits.

### Claims link to evidence

A Note reference in the chapter opens the exact run.

### Your supervisor writes where you work

Comments go into the shared Supervisor thread instead of a seventh email.

## A thread, over time

Your workspace starts empty.

### Experiments

Thesis · Active

#### Thu 12 Mar

*The script adds the run: parameters, table and plot.*

via **Analysis script** · 17:44

Run 14 · 35 °C · 6 h

| Sensor | Drift | Error |
|---|---|---|
| A | 0.42 | ±0.03 |
| B | 0.39 | ±0.04 |

[Image: Plot of drift over time for run 14]

*Your reading, right under the data.*

**You** · 18:10

Drift starts above 30 °C. Use in 3.2. #drift

#### Fri 13 Mar

*A reference to the comment in the shared Supervisor thread.*

**You** · 09:20

Prof. Koval asks me to compare with Li et al. before I claim it.

↳ Supervisor · 13 Mar

#### Mon 16 Mar

via **Analysis script** · 16:20

Run 15 · 25 °C control · 6 h

[Image: Plot of drift over time for run 15, flat]

*A reference back to the run it’s about.*

**You** · 16:41

The control is flat. The claim holds.

↳ Run 14 · 35 °C · 6 h

## It files itself. You read.

Your tools write into the threads you choose, with only the access you give them.

[Script or API](https://thread.page/help/connections/custom.md)

### Results from your script

Two calls at the end of your analysis script: one uploads the plot, one adds the note with a Markdown table.

#### Set it up

Automation Add only Experiments

1. In **Settings → Connections → Automations**, choose **Connect an automation** → **Script or API** with **Add only** for the Experiments thread: it can add notes and can’t read or change any, so it’s safe in a shared script.
2. At the end of the script, upload the plot to the thread’s images and add a note whose Markdown holds the parameters, the table and the image.
3. Give each run the same operation id when you retry: it is added once. [Notes](https://thread.page/help/connections/api/notes.md) in the developer reference shows both calls.

## Limits

- No citation manager and no equations.
- Files a script sends can be up to 2 GB each.

## Start with one thread.

[Start free trial](https://thread.page/auth/sign-up?returnTo=%2Fapp%2Fsettings%2Fbilling%23trial)

14 days of Pro, no card. Then from USD 7.99 a month.

[Start a thread](https://thread.page/app)

More use cases

### [A residence permit and a mortgage, at once](https://thread.page/use-cases/paperwork.md)

Each letter, call and photo goes into its thread, and Waiting marks what’s out of your hands. “I sent it on 7 August” is a fact.

Free · nothing to set up

### [Where your coding agent stopped](https://thread.page/use-cases/agent-work-log.md)

Claude Code hits its limit on Monday afternoon. You write to @codex, and it carries on from the pinned plan and the last note.

Pro · Claude Code and Codex

[All use cases](https://thread.page/use-cases.md)