ThreadPage
Open threadsBack to threadsBack to searchBack to draftsBack to trashBack to archiveBack to imagesBack to shared placesBack to storageBack to settings

All use cases

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.

See the thread

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 Free for writing in this browser; export a backup now and then. Pro for the script, sync and sharing.

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

  1. Each run is a dated note

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

  2. Claims link to evidence

    A Note reference in the chapter opens the exact run.

  3. Your supervisor writes where you work

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

A thread, over time Example

Your workspace starts empty.

Thesis

Experiments

Active

  1. Thu 12 Mar

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

      via Analysis script17:44

      Run 14 · 35 °C · 6 h

      SensorDriftError
      A0.42±0.03
      B0.39±0.04

    2. Your reading, right under the data.

      You18:10

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

  2. Fri 13 Mar

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

      You09:20

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

      Supervisor · 13 Mar

  3. Mon 16 Mar

    1. via Analysis script16:20

      Run 15 · 25 °C control · 6 h

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

      You16: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.

Custom connections and API

  • 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

    Custom connectionAppend onlyExperiments

    1. In Settings → Connections, choose Add connection → Automation or API with Append 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. Custom connections and API shows both calls.

Limits

  • No citation manager and no equations.
  • Images a script sends can be up to 5 MB each.

Start with one thread.

Open threads

Free in your browser. No account needed to start.

More use cases

All use cases