Skip to content

docs: writes honour the per-call workspace override #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chicagobuss merged 1 commit into from
Aug 3, 2026
Merged

docs: writes honour the per-call workspace override #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions web/usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,9 +98,16 @@ tags and search results in other workspaces are invisible to you, and slugs only
have to be unique within yours. `list_workspaces` shows what exists;
`create_workspace` registers one, but does not move you into it.

To read elsewhere without reconnecting, pass `workspace` to any read tool —
`list_docs {"q":"...","workspace":"other"}`. Writes ignore it and always target
your own workspace, and it is refused if your token is confined to one.
To act elsewhere without reconnecting, pass `workspace` to any tool —
`list_docs {"q":"...","workspace":"other"}`. Since #8 this applies to **writes
too**: `create_doc`, `update_doc`, `retag_doc`, `soft_delete_doc`, `restore_doc`,
`hard_delete_doc`, `create_folio` and `add_folio_file` all honour it and place
the write in the named workspace. It is refused if your token is confined to one,
and it is ignored by `list_workspaces` and `create_workspace`, which act on the
registry rather than inside a workspace.

Pinning a connection with `X-Workspace` is still the better default for sustained
work somewhere — it makes placement structural instead of per-call.

If a store looks unexpectedly empty, you are probably pointed at the wrong
workspace rather than at an empty tracker.
Expand Down
Loading