Skip to content
Fredrin
Documentation

Working the board

Notes

A markdown notebook that lives with the project. Roadmaps, launch checklists, meeting notes, the thinking that is not a ticket and does not belong in the repo.

What it is

A file explorer on the left, one live editor on the right. Create, rename, nest, and delete folders and markdown notes freely. There is no edit-versus-preview toggle: the editor is the document.

Notes are scoped to a project, so each board has its own notebook.

What it is for

The writing around the work.

  • A roadmap you keep re-reading.
  • A launch checklist you tick off.
  • Notes from a call that will become three tickets tomorrow.
  • The half-formed idea that is not ready to be a ticket.

Notes are not tickets, and not repo files

Worth being precise, because all three are markdown and it is easy to blur them.

Lives inRead byGood for
A noteFredrin, per projectYou, and agents you askYour own thinking
A ticketThe boardThe Worker that builds itOne unit of work
Project contextYour repositoryEvery Worker, automaticallyHow the codebase works

If you want every Worker to know something, it belongs in project context, in the repo. If you want a place to think, it belongs in a note.

Agents can use them

Notes are reachable from the CLI and the API, so you can ask an agent to read a note and talk about it, or to write something up as one. Notes created by an agent are marked as such, so you can always tell your own writing from generated writing.

fredrin notes list
fredrin notes read "Roadmap"
fredrin notes write "Roadmap" --file ./updated.md

Where it works

Notes work in the desktop app and in a signed-in browser. It is one of the few surfaces that does not require the desktop shell.

Next steps

  • Project memory - the context Workers read automatically.
  • The CLI - reading and writing notes from a terminal.