Multi-session chat memory + slash commands #852

Closed
opened 2026-10-27 13:38:01 +00:00 by sam · 0 comments
Owner

Chat channels need conversation memory that persists across sessions, distinct from the existing per-task /data/memory.jsonl sketch in the v2 architecture PRD (which is task/project scoped, not conversation scoped). Also add slash-command support in chat (/status, /spawn, /approve, /cancel) per docs/prds/multi-agent-collaboration.md phase C. Depends on the chat channel interface existing first.

Acceptance Criteria

A conversation started on a chat channel retains context across the operator closing and reopening the client. /status, /spawn, /approve, /cancel are recognized slash commands with documented behavior.


Imported from beads archie-core-1786637498244-320-1e3ab1cc · GitHub #341 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08

Chat channels need conversation memory that persists across sessions, distinct from the existing per-task /data/memory.jsonl sketch in the v2 architecture PRD (which is task/project scoped, not conversation scoped). Also add slash-command support in chat (/status, /spawn, /approve, /cancel) per docs/prds/multi-agent-collaboration.md phase C. Depends on the chat channel interface existing first. ### Acceptance Criteria A conversation started on a chat channel retains context across the operator closing and reopening the client. /status, /spawn, /approve, /cancel are recognized slash commands with documented behavior. --- _Imported from beads `archie-core-1786637498244-320-1e3ab1cc` · GitHub #341 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam added the mediumtask labels 2026-10-27 13:38:01 +00:00
sam self-assigned this 2026-10-27 13:38:01 +00:00
sam closed this issue 2026-10-27 13:38:01 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#852