Tasks, Memory, and Backlog Functions

These functions let CodeBot preserve follow-up work and context beyond one response.

Use the right persistence level:

  • Memory is for durable context or decisions that should help future conversations.
  • Action items are short-lived assistant follow-ups stored in the local CodeBot cache.
  • Beads are durable project backlog items stored with the project repository and visible to collaborators or future agents.

Memory

  • addProjectMemory stores a long-term memory relevant to the current project or solution.
  • addUserMemory stores a long-term memory applicable to all work for the developer.

Use memory for facts, preferences, decisions, or project context that should influence future work. Do not use memory as a task list.

Both memory functions accept a required summary, optional context, and optional timestamp flag. When timestamp is true, the saved memory includes the current UTC date and time.

Action Items

  • addActionItems creates one or more solution-specific action items for deferred follow-up work. It supports either single-item fields or an items array for batch creation.
  • listOpenActionItems lists open action items that still need follow-up.
  • getActionItemInfo returns full details for one action item by ID.
  • closeActionItem marks an action item closed and can include a resolution.

Use action items for private, short-lived assistant follow-ups such as deferred fixes, investigations, cleanup, or next steps from a review. When several items should be added, prefer one addActionItems call with the items array instead of repeated one-item calls.

Adding and closing action items are mutating actions and use approval.

Beads

  • getBeadsInfo reports whether Beads are available for the current solution or workspace.
  • listBeads lists Beads using semantic filters such as status, priority, assignee, label, text, ready-only, and limit.
  • getBead returns full details for one bead by ID.
  • createBeads creates one or more durable Beads backlog items.
  • updateBead updates, closes, reopens, comments on, labels, or changes dependencies for a bead.

Use Beads when follow-up work should be tracked with the project repository and visible to collaborators or future agents. CodeBot should prefer these functions over terminal commands or raw br calls when Beads support is available.

Creating and updating Beads are mutating actions and use approval.

When To Use Which Tool

Use addProjectMemory or addUserMemory for context that should shape future conversations.

Use action items for local follow-up work that should stay in CodeBot's cache.

Use Beads for durable project backlog work that should live with the repository.

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.