Skip to main content

Workspace Commands

A workspace is an owned namespace (yours or a team’s) for native notes plus included primitives (artifacts — a table is an artifact). Notes are markdown content you write directly in Tokenrip; included artifacts are either owned (the workspace is their home — deleting the workspace destroys them) or linked (a reference — only unfiled on delete). See Workspaces for the full concept guide.
The rip workspace group is aliased rip ws — every command below works with either form (rip ws note list research).
Workspace slugs are scoped to you or a team you belong to. Explicit members of a personal workspace reach it by its id, not slug. If a slug is ambiguous across reachable workspaces, the CLI returns AMBIGUOUS_WORKSPACE_SLUG — pass the workspace id instead.

rip workspace create

Create a workspace.
ArgumentDescription
<slug>Unique workspace identifier (scoped to you or the team)
OptionDescription
--name <name>Display name (defaults to the slug)
--description <text>Optional description
--team <team-slug>Make this a team-owned workspace instead of personal

rip workspace list

List the workspaces you can access — owned, team-owned, or ones you’re an explicit member of.

rip workspace show

Show a workspace by id or slug.

rip workspace archive

Archive a workspace (admin only). A soft hide — nothing is destroyed.

rip workspace delete

Delete a workspace (admin only). One clean operation: owned items are destroyed (storage reclaimed), linked items are only unfiled, and all native notes, links, and memberships are removed.

Notes

Notes are markdown content native to the workspace. Slugs are date-prefixed (YYYY-MM-DD-<kebab-title>), with a numeric suffix on same-day collisions.

rip workspace capture

Zero-friction capture — the title is derived from the first line.

rip workspace note set

Create a note, or update one by slug.
OptionDescription
--title <title>Note title (derived from the body’s first line if omitted)
--body <body>Note body (markdown)
--slug <slug>Existing note slug to update (omit to create)
--maturity <state>Set the note’s maturity — must be in the workspace’s configured ladder
--source-artifact <publicId>Create only — link the note as an atom of that source artifact (the document it was extracted from). Ignored on update

rip workspace note get

Get a single note by slug.

rip workspace note list

List the notes in a workspace. Archived notes are hidden by default.
OptionDescription
--archivedList only archived notes
--include-archivedInclude archived notes alongside active ones

rip workspace note archive / unarchive

Archive a note to drop it from the default list (and an agent’s eager agent_load tiers) without deleting it; unarchive to restore. Find archived notes with note list --archived.

rip workspace note delete

Permanently delete a note. Its note→note links are removed too.
Full-text search over note bodies (PostgreSQL FTS), ranked, with **-delimited snippets.

Maturity & consolidation

These apply when a workspace has a maturity ladder — most often an agent’s memory workspace. The platform enforces only the mechanics; what a state means (“evergreen”) is the brain’s job.

rip workspace note promote

Advance a note one step along the configured maturity order. A min-backlinks-N rule requires the note to have ≥ N backlinks first (else PROMOTION_BLOCKED).

rip workspace worklist

The consolidation work-list — four candidate sets from cheap indexed scans. It’s a read; the harness (not the backend) decides what to do, using the write commands above.
OptionDescription
--stale-capture-days <n>Captures untouched longer than N days count as stale (default 7)
--stale-top-tier-days <n>Top-tier notes untouched longer than N days count as stale (default 30)
When the workspace is a brain (semantic indexing on), the worklist also returns brain refinement candidate-sets — unAtomizedSources (sources with no atoms yet, ranked by retrieval hotness), staleAtomSources (sources changed after their atoms were last touched), recurringSignals (recent signal-zone notes to fuse into a thesis), and pendingInbox (staged items, editor+ only). These are brain-membership-scoped and drive the rip brain atomize / rip brain consolidate rituals.
Connect one note to another to build a small graph. Each note tracks how many notes link to it (backlinkCount).

Members

Members are accounts with a role. An artifact you include becomes reachable by the workspace’s members (the same way team-shared artifacts work); team-owned workspaces grant every team member admin-equivalent access automatically.
RoleCan
viewerRead and search notes and items
editor…plus write notes and add/remove items
admin…plus manage members, archive, and delete
The <account> accepts an account id or a saved contact name.

Items (include artifacts)

Include an existing artifact two ways: link it (a reference that persists when the workspace is deleted) or own it (move it in — destroyed with the workspace). At most one workspace can own a given artifact (409 ALREADY_OWNED otherwise); any number can link it.
OptionDescription
--ownership <owned|linked>linked (default) references the item; owned moves it in
--kind <kind>Item kind (default artifact)
rip workspace item remove only unfiles an item — it never destroys a linked artifact.

Across surfaces

Workspaces work identically across the CLI (rip workspace … / rip ws …), the MCP workspace_* tools, and the REST API (/v0/workspaces) — all backed by the same service layer. Add --json (or TOKENRIP_OUTPUT=json) for machine-readable output.