← toolbox

Docket

v0.1

A ledger that files every AI chat and session under the project it belongs to, with its status and next action, a notes tray, and a 2D map. Early mock-up with sample data.

experimentmajor tool

At a glance

Status
work in progressActively changing; expect things to move.
Being worked on?
Being worked on
Version
v0.1
Shelf
Prototypes and projects
Added
Last updated
Known bugs
None noted
Runs
Here, at /docket
Saves your data
Browser storage (localStorage)

What it does

What's next

What changed

  1. v0.1

    First mock-up: board, notes, 2D map, sweep, Sync lab simulation, backup and restore, installable.

STORAGE — Browser storage (localStorage)

Chats, projects and notes are saved in this browser only (key docket.state.v1). Nothing is sent anywhere yet, and the Sync lab uses pretend data. Clearing site data or switching devices loses them: use Settings → Download backup.

Export: JSON download available · Import: supported

The write-up

Docket

Goal

Docket is a ledger that files every AI conversation under the project it belongs to, and says what state each one is in: still going, waiting on someone, finished and ready to archive, or holding work that has not been done yet. The work is split across Claude chats on the web, Claude on a phone, Claude Code sessions on the web, and soon a command-line Claude on another machine inside a container or a code sandbox. No single screen can answer "which chats belong to this project, and are any of them unfinished?" Docket is the thin layer that answers it.

It is deliberately a ledger and not another assistant. It stores titles, links, a one-line next action and a short handoff note per conversation. It does not store the conversations themselves.

The wider idea (added 2026-11-15) is a small cockpit of one's own: drop a note the moment an idea arrives, before it belongs to any chat or environment; open a new chat on whichever platform fits, with the note ready; see every conversation on a board and on a 2D map grouped by project, with a 3D view possible later; and have the same picture on the computer and the phone, kept in sync. Docket opens and files the conversations. It never sends anything for you and never keeps what was said in them.

The problem

The model

Three things, kept small:

Environments (a browser, a phone, a machine, a container, a sandbox) are a short list so a thread can say where it lives and when that place last checked in.

The life of a thread

Inbox, then active, then either waiting (on me, on an agent, or on something outside), parked on purpose (with a next action and a day to look again), or done, and finally archived. "Does this chat have more work in it?" is not a separate flag: it means the thread has a next action. A thread marked done that still has a next action is flagged as a contradiction instead of being quietly archived.

How threads get in, from least effort to most

  1. By hand: paste the link and a title, pick a project. Works everywhere today, including from a phone.
  2. A naming habit: start each chat with the project tag, such as [toolbox] fix the card layout. Docket reads the tag from the title, so filing needs no tool at all.
  3. An export file: Claude lets you export your account data. Choosing that file in Docket (a normal file picker, nothing reads your disk on its own) would backfill history in bulk and let you file hundreds of old chats in a few batches. The file layout needs checking before the importer is built.
  4. A browser extension: on the Claude pages, a small "file under a project" menu that reads only the page title and address and saves them to Docket on the device. Opt-in, like the other extensions here.
  5. Command-line hooks: Claude Code can run a script at the start, the end and each stop of a session and hands it a session id and the working directory. A ten-line script can report those to Docket. The working directory points at a repository, and the repository points at a project, so filing is automatic.
  6. Containers and sandboxes: the same script baked into the image, with a label for the machine. Each environment checks in, so Docket can show which ones went quiet.
  7. Agents that report themselves: the automatic agents that already ask TokenEcon "may I work?" can say which project and thread the work is for, and Docket records it.

Capture, launch, see and sync

Suggestions

Other things like this

Claude's own Projects group chats, but only inside claude.ai and with no notion of done. Claude Code can resume sessions, listed per folder. Task trackers such as Linear or a Notion database are good at status but know nothing about the chats behind it. Hermes Agent, an open-source agent from Nous Research, remembers across sessions and can search its own past conversations, which solves the agent forgetting rather than the person losing track of which chat is for what; it could be one more source of threads. The gap Docket aims at is a ledger that spans all of them, with a lifecycle per chat.

How it will be built, one slice at a time

Current state

An early mock-up (v0.1) you can open right now. It has a board, a notes tray, a 2D map, a sweep list, backup and restore, and it installs on a phone. It starts with sample data (clearly marked, removable in one click) and saves only in this browser. The Sync lab is a simulation with pretend devices that shows how sync will be kept safe from a laptop waking up with an old copy; it sends nothing anywhere and never touches your saved chats. Real sync, Docker reporting and the Chrome extension are later slices.

Changelog

Sources: Hermes Agent overview, Hermes Agent memory and session search, Claude Code hook inputs.