Skip to main content
Every CLI command operates on one of a small set of objects. This page is the map; each object’s commands live on its own page.

Two scopes

gobi personal is your Home. Everything you capture lands here, and only you can read it. Your artifacts live here too. gobi space is a shared space. What you write there is visible to its members. Both groups expose the same posting surface: feed, create-post, create-reply, react, search-posts. Home adds what the apps captured, and spaces add channels. One space is active per directory, chosen with gobi space warp and saved in .gobi/settings.yaml. Any command takes --space-slug to target another space one-off. Nothing crosses spaces on its own.

Content objects

The [p:N] / [r:N] labels in feed output are the ids every other command takes. Posts, replies, and reactions are editable and removable only by their author.

Captured context

What the apps capture surfaces in the CLI as two browse-only groups. You can read them; you can’t create them.
  • Conversations. Captured conversations: transcript, summary, audio.
  • Activities. Ambient activity records.
Both live in your Home only. A capture lands there whatever space was on screen when it happened, so gobi personal conversations and gobi personal activities are the only places they are listed. Transcript and audio stay with the person who recorded.

Files

A vault is a local directory synced to Gobi’s webdrive, with PUBLISH.md as an optional public profile at gobispace.com/@{slug}. It sits outside the Home-and-spaces model entirely, and it is experimental. See vault.

Where to go