update
May 10, 2026
By Teun
Draft adds persistent product context for Claude, Codex, Cursor
Draft is a plugin that adds persistent product context to Claude Code, Codex CLI, and Cursor sessions. The project says it injects a live snapshot of product information at session start and records changes in an append-only log so the context does not go stale.
Draft is a new plugin for Claude Code, Codex CLI, and Cursor that tries to stop AI assistants from starting every session with a blank slate. The project says it gives each session a persistent “PM brain” that loads product context automatically, so users do not have to re-explain their company, priorities, or recent changes each time.
The tool is aimed at people using AI assistants for product work. According to the project description, Draft loads a live snapshot of workspace context at the start of each session, including company, product, team, priorities, and memory. It is designed to keep the assistant oriented without requiring users to paste the same background over and over.
⚡ New to this?
This news is about making AI coding and product assistants remember the project you are working on, even after the session ends. A session hook is a script that runs when an editor or agent starts, and a POSIX shell is the standard Unix-style command environment used on macOS and Linux.
For non-experts, the big idea is that the plugin tries to keep the assistant from forgetting your product context or relying on outdated notes. That matters because AI tools often work better when they know the current state of the project instead of starting fresh every time.
🦞 OpenClaw angle
If you run self-hosted agents, treat persistent context as a first-class system component, not a prompt snippet. Keep a shared workspace or memory store outside any one editor, and update it through a dedicated write path so the agent is not reasoning from stale notes.
Also add a startup hook that injects a small, current snapshot of project state before each session. If you support multiple clients, make the hook detect existing installs so you do not duplicate context sources or create conflicting memories.
Draft says it addresses two problems. The first is “context amnesia,” which the project describes as the blank-slate problem: a new session does not remember what happened in previous sessions. The second is “context rot,” where local documents such as CLAUDE.md files drift away from reality as products change.
To deal with that, Draft uses an append-only log and a persistent index of recent changes. When something meaningful happens - such as a decision, a scope change, something shipped, or something dropped - the draft-learner agent records it and updates the index, according to the project description. That index is loaded automatically in later sessions.
The plugin uses an orchestrator-plus-sub-agents setup. Draft says the main pm-agent handles the overall product-management flow, while three specialist agents split the work: draft-researcher gathers information, draft-executor writes artifacts and updates files, and draft-learner records what should be remembered.
The project also ships two slash commands for keeping the workspace updated. /draft:setup runs an onboarding interview to initialize the PM brain. /draft:learn captures a decision, priority shift, product change, or other note that should persist across sessions.
Installation depends on the editor. For Claude Code, Draft can be loaded as a plugin or from a local directory. For Codex, the project says setup is a direct install script that writes into ~/.codex/ and registers a SessionStart hook. For Cursor, Draft installs into ~/.cursor/ and uses a sessionStart hook to inject context into new Agent tab sessions.
The project says the same workspace at ~/.draft/workspace/ is shared across editors. It also says setup scripts detect other installed editors and skip duplicate context pieces when needed, so Cursor does not create a second “PM brain” if Claude Code or Codex is already present.
Platform support is limited to macOS and Linux, according to the project. Draft says its session hook is a bash script and requires a POSIX shell environment. Windows, including WSL, is not currently supported or tested.
Draft also includes an automatic update check on session start. According to the project, when a new version is available, the assistant will mention it and offer to apply the update, while leaving the PM brain data in ~/.draft/workspace/ untouched.
