Remembering Context and Tracking Follow-Up Work

CodeBot can preserve context and follow-up work beyond one response. The right place depends on how durable the information should be and who should see it later.

Ask CodeBot to Remember Project Context

Project memory is for durable facts, preferences, decisions, and context that should help future chats about the current solution or workspace.

Typical prompts:

  • "Remember that this project uses the new API style."
  • "Save this decision as project memory."
  • "Remember that tests should be run with this command."

Use memory for context, not task lists.

Ask CodeBot to Remember User Preferences

User memory applies across work for the developer, not just the current project.

Typical prompts:

  • "Remember that I prefer concise PR descriptions."
  • "Remember that I want review findings grouped by severity."

Only save durable preferences or facts that should shape future work.

Ask CodeBot to Create Local Action Items

Action items are short-lived CodeBot follow-ups stored in the local CodeBot cache for the current solution or workspace.

Typical prompts:

  • "Add these review follow-ups as action items."
  • "List open action items."
  • "Close the action item about updating docs."

Use action items for private, local follow-up work that does not need to live in the project repository.

Ask CodeBot to Track Durable Backlog Work with Beads

Beads are durable project backlog items stored with the project repository. They are useful when follow-up work should be visible to collaborators or future agents.

Typical prompts:

  • "Create Beads for these three cleanup tasks."
  • "List ready Beads for this project."
  • "Close this Bead with a resolution comment."
  • "Add a dependency between these two Beads."

Use Beads when the work should travel with the repository rather than staying in a local CodeBot cache.

Choosing the Right Place

Use memory for context that should influence future conversations.

Use action items for local follow-up tasks.

Use Beads for durable project backlog items.

Do not store the same thing in all three places. Pick the persistence level that matches who should see it and how long it should live.