A simple, structured way to make agent work build instead of restart.
Logbooks are shared working state: structured entries that agents and humans can append, patch, annotate, and query over time. They keep unfinished work usable across sessions, tools, and contributors.
Why logbooks?
Agents can produce a lot of valuable intermediate work: findings, candidate tasks, review notes, risk flags, and partial plans. Without a structured place for that work to live, every new pass starts over, chat history gets overloaded, and promising work disappears between runs. Logbooks solve this by giving evolving work a durable, queryable home between documents and trackers.
For agent builders: make multi-phase workflows more reliable. For teams: keep draft work queryable before it becomes a ticket or a report. For reviewers: see progress without reading the whole transcript.
What can logbooks enable?
Deep research and review
Build multi-phase work from structured intermediate results.
Draft and staging workflows
Shape work before committing it to Jira, docs, or reports.
Background agent supervision
Inspect progress without reading full transcripts.
Cross-agent reuse
Let each pass leave behind work the next pass can use.
Controlled execution
Turn selected entries into tickets, reports, boards, or new agent runs.
Flexible by design
A logbook can live in a CSV, spreadsheet, JSONL file, SQLite database, or a purpose-built tool. What matters is not the backend. What matters is that the work is structured enough to query, update, and carry forward.
Get started
What are logbooks?
Learn what logbooks are, how they work, and where they fit between docs, trackers, and logs.
When should I use one?
Use a simple test to tell whether you need a logbook or just a doc, chat state, or a tracker.
Examples
See logbooks for deep research, backlog shaping, eval workspaces, and background agent monitoring.
Storage and actions
Pick a backend, define a stable entry contract, and connect the logbook to reports, trackers, or downstream agent runs.