Issues

Bugs and tech debt discovered during work.

Scope

An issue can belong to:

• A feature (optional) - usually the feature where it was discovered
• A session (auto-linked) - which session surfaced it

Fields

• title, description
• severity - low / medium / high / critical
• status - open / inProgress / resolved
• sessionId - auto-set to the active session when reported

Why structured (vs just a note)

Notes are unstructured free text. Issues are:

• Triaged by severity
• Tracked through resolution
• Linked to the discovery context (session + feature)
• Surfaced in get_feature_context so they don't get forgotten

Reporting

Via natural language:

• "Found a bug: [description]"
• "Tech debt: this should use the new API"
• "Critical issue: data loss if user closes tab mid-save"

your agent picks the severity based on your wording (e.g., "critical", "minor") or asks if unclear.

Surfacing

Issues show up in:

• The feature's screen in the menu bar panel - "Issues (N)" with severity badges
• get_feature_context response when loading a feature
• Session timeline - a yellow triangle event when reported

Lifecycle

update_task doesn't apply to issues - there's no update_issue tool yet. To resolve an issue, edit the underlying index or ask your agent for a specific fix and it will manage state via update_feature_context descriptions.