NOTCHPAD PROJECTS

Project memory for Codex and Claude

Bring the brief, the chat, and the decision into one project. Give the next session a source it can check.

The Studio launch project in NotchPad, showing an accepted decision with its source chat

ONE PROJECT, TWO SESSIONS

Keep the decision when the chat changes.

  1. 01 Import a chat
    Migration planningClaude Code · imported chat
    “Keep staging separate so we can test redirects before the domain switches.”
    Import Codex or Claude Code chats
  2. 02 Review the decision
    Keep staging separateNotchPad · accepted decision

    Save the reason and link it to the original message.

    Review a sourced decision
  3. 03 Use it in a new session
    What needs to happen before launch?Codex · new session

    Ask Codex to check the shared project and cite the decision it uses.

    Connect an agent with MCP
Memory Map with a saved relationship between the staging decision and the redirect check

MEMORY MAP

See which decisions depend on each other.

Link a decision to the rule it relies on. Open either record to check the evidence behind it.

Explore the Memory Map guide

Keep editing the files you already have

Link a Markdown folder and add existing NotchPad notes. Linked files stay on disk.

Link project sources

Give each agent the right access

Choose which projects and sources a connected app can read. Share instructions from your Skills Library when they’re useful to the task.

Share a skill with an agent

Keep building your workspace

Work with linked Markdown files and connected notes, or follow the project-context handoff workflow.