A workstream is a project-scoped container for multi-day work. It is the right place for things people may also call an epic, initiative, topic, lane, or focus area.
Use one Zharwing Memory project for a long-lived product area, then create workstreams inside it.
Example:
Project: Acme Product
Workstreams:
Search
Permissions and Roles
Post-auth Onboarding
Design System
Epic often implies a specific product-management hierarchy. Workstream is
looser: it can group sessions, docs, repositories, imported memory, and
decisions across several days without forcing an agile structure.
Workstreams are Markdown files under:
<project-memory-root>/workstreams/<slug>.md
They include frontmatter for:
idnameslugstatussummarygoaltopicsrepo_rolesrelated_tasksrelated_filespinned_doc_ids
Sessions and documents can attach explicitly with workstream_ids. The
workstream detail view also finds related sessions and documents by matching
topics, related task labels, names, summaries, and body text.
- Create or select a project.
- Open
Workstreams. - Create a workstream such as
Huddle. - Add topics like
huddle,realtime, orpermissions. - Start sessions from the Dashboard and select the workstream.
- Use the Workstream detail view to see related sessions and docs.
- Move obsolete workstreams to Trash instead of permanently deleting them.
zharwing-memory workstreams --project <project-id>
zharwing-memory create-workstream "Huddle" --project <project-id> --topic huddle,realtime
zharwing-memory workstream huddle --project <project-id>
zharwing-memory start "Huddle service contract pass" --project <project-id> --workstream <workstream-id>
The UI and authenticated daemon JSON-RPC surface support:
memory.list_workstreamsmemory.create_workstreammemory.get_workstream_detailmemory.update_workstream_statusmemory.delete_workstream
The focused MCP daily-memory surface can attach known workstream ids when starting a session, but workstream administration remains a UI/CLI operation.