Context Docs

EXAMPLES

One small app.
Three walkthroughs.

Start with Reading Queue to learn the full workflow. Then try handing unfinished work from one coding agent to the other through the files saved in your project.

For Codex and Claude Code · Authored teaching examples
Shared app: Reading Queue. Context Docs itself needs no server or cloud account.

  1. Learn the full workflow

    Reading Queue

    Run a small app locally, inspect its context setup, audit it, scope a feature, leave a handoff and resume in a fresh session. Deploying your own copy is optional.

    One client · Local practice · Optional Cloudflare deploy

    Work through Reading Queue

  2. Switch clients

    Codex to Claude Code

    Codex builds and tests the export API, saves what is done and pending, then stops. A fresh Claude Code session reads the files and adds the browser button.

    Two clients · Local only · No deployment

    Start in Codex

  3. Switch clients

    Claude Code to Codex

    The same split in reverse: Claude Code builds and tests the export API, then a fresh Codex session recovers the status from the files and continues.

    Two clients · Local only · No deployment

    Start in Claude Code

ABOUT THE SWITCHING WALKTHROUGHS

Hand off through files, not chat.

Both directions use the existing Reading Queue app and the same feature, split at the same point. The first client implements and tests the JSON export API, records what is complete and what is pending, and stops. A fresh session in the other client reads the saved project context, checks it against the current files and continues with the browser button.

The receiving prompt does not repeat the feature scope. The point is to see whether the saved files carry it: the requirement, the reason for exporting the whole queue, the API work that is done, the browser work that is not, and what the checks do and do not cover.

Only project files carry over. Chat history, native memory such as Claude Code auto memory or Codex memories, and the other client’s runtime state do not. Keep one writer at a time: stop the first client before the second starts. There is no sync, file locking or exclusive ownership.

Install the two Context Docs skills in each client first; see the installation guide. New to the workflow? Reading Queue introduces each step more slowly.

These are authored walkthroughs. Any observed checks of them are described, with their scope and limits, in the switching examples record. They do not establish general reliability or time or token savings.

NOT SURE IT FITS?

Start with what you already have.

Codex and Claude Code already provide instructions and memory. Context Docs is an optional starting workflow for keeping decisions, current work and next steps in project Markdown.

Compare approaches