summaryrefslogtreecommitdiffhomepage
path: root/packages/cli
diff options
context:
space:
mode:
authorAdam Malczewski <[email protected]>2026-06-25 11:09:21 +0900
committerAdam Malczewski <[email protected]>2026-06-25 11:09:21 +0900
commit59c481dc96aa40b8c8f0a81bb294a77d4e5aa533 (patch)
tree1e158b71950a6b15f44e4897fed961ab0f7070a3 /packages/cli
parentd4b470ca582e3c69c40438895b90748d44fc4653 (diff)
downloaddispatch-59c481dc96aa40b8c8f0a81bb294a77d4e5aa533.tar.gz
dispatch-59c481dc96aa40b8c8f0a81bb294a77d4e5aa533.zip
docs(notes): research โ€” list conversations filtered by worktree/workspace
Investigation of whether the backend supports listing open conversations filtered by a specific worktree/workspace. Findings: - 'worktree' is not a Dispatch domain concept; canonical term is 'workspace' (logical grouping) vs 'working directory' (cwd, filesystem path). - GET /conversations already supports composable ?workspaceId=, ?status=, ?q= filters. 'Open conversations in workspace X' = ?workspaceId=X&status=active,idle. - Every conversation carries a workspaceId (default 'default'); ConversationMeta is in @dispatch/wire; filter lives in conversation-store listConversations. - A literal directory (git worktree) filter (?cwd=) is NOT supported; ยง3b documents the small additive change needed across wire/store/transport-http. - Test coverage verified: store-workspace.test.ts:369, store.test.ts:1463, app.test.ts:3696. Research notes only โ€” no code/contract changes.
Diffstat (limited to 'packages/cli')
0 files changed, 0 insertions, 0 deletions