Session Sticky Notes: Attach persistent notes to a conversation for future work

Open 💬 0 comments Opened Jun 26, 2026 by sidiangongyuan

What variant of Codex are you using?

App

What feature would you like to see?

Motivation

When working with Codex, I often think of ideas, improvements, or future tasks that are tightly related to the current conversation but should not be executed immediately.

For example:

  • "Remember to refactor this module after the current feature is finished."
  • "We should benchmark this later."
  • "Consider supporting another API provider."
  • "Don't forget to ask about edge cases."

These thoughts are important, but interrupting the current workflow to execute them immediately is often undesirable.

Currently there is no lightweight way to keep these ideas attached to the conversation itself.

---

Proposed feature

Allow users to create persistent sticky notes inside a conversation.

Characteristics:

  • Notes belong to the current conversation/session.
  • Notes persist after closing and reopening Codex.
  • Notes can be attached anywhere in the conversation timeline (similar to comments or bookmarks).
  • Multiple notes can exist.
  • Notes are independent from the assistant messages.
  • Notes can be marked as completed or deleted once no longer needed.

Example:

💡 Sticky Note

Investigate replacing this parser after the current milestone.

or

📌 TODO

Benchmark this implementation before merging.

---

Why this is useful

Many development tasks are not immediately actionable but are highly contextual.

Without a conversation-level note system, users either:

  • interrupt the current workflow,
  • write notes in an external application,
  • or simply forget the idea.

Keeping notes inside the conversation preserves context and reduces cognitive load.

---

Possible UI

  • Small sticky-note icon in the conversation toolbar.
  • Right-click any message → "Add Note Here".
  • Notes displayed as pinned cards between messages.
  • Collapse/expand notes.
  • Checkbox for completed notes.
  • Delete/archive completed notes.

---

I believe this would make long-running coding sessions much easier to manage, especially for projects that span multiple days.

Additional information

This is intentionally different from ChatGPT Memory or project-wide TODOs.

These notes are conversation-scoped, because many ideas only make sense in the context of a specific coding session.

View original on GitHub ↗