Add a "Notes" tab next to Diff/Logs for task-specific note taking or writing down reminders

Resolved 💬 2 comments Opened Feb 27, 2026 by zterefe Closed Apr 3, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

Web

What feature would you like to see?

I’d love to see a new "Notes" tab added to the top navigation bar, right alongside the existing Diff and Logs tabs. When I'm reviewing a big implementation across different tasks, I often come across things I need to double-check or questions I want to ask the AI later(especially if I'm reviewing it on my phone), so it would be nice to have a note tab that will serve as a scratchpad for each tasks.

What I would expect this tab to allow:

  1. Quick Jotting: A place to write down "Don't forget to update the README" or "Check if this client handles timeouts" while looking at the code.
  2. AI Follow-ups: A spot to draft specific questions for the AI so I don't lose my train of thought while jumping between different tasks.
  3. Pre-PR Checklist: A way to keep track of what’s left to do before I actually hit "Create PR."

<img width="1347" height="906" alt="Image" src="https://github.com/user-attachments/assets/358ba2c6-4210-496d-82a5-c381f4fd1405" />

Additional information

_No response_

View original on GitHub ↗

2 Comments

etraut-openai contributor · 4 months ago

This feature request hasn't received enough upvotes, so closing.

jeemitsha · 4 months ago

Just a courtesy follow-up on this closed issue: refiled the idea with extended scope as #20138, for the desktop app this time.

The new proposal keeps your "user scratchpad" use case (pre-PR checklist, quick jotting, AI follow-up drafts) as a private region — UI-only, never sent to the model — and adds a second shared region that's read-write by both the user and the agent, auto-injected into the model's context every turn so the notes survive compaction.

Cross-linking in case you or anyone tracking this issue wants to follow the new one. Credit to the original framing here — the user-scratchpad intent is still the core.