@gobi-ai/cli 2.0.39 → 2.0.41

package/.claude-plugin/marketplace.json

@@ -4,12 +4,12 @@
     "name": "gobi-ai"
   },
   "description": "Claude Code plugin for the Gobi collaborative knowledge platform CLI",
-  "version": "2.0.39",
+  "version": "2.0.40",
   "plugins": [
     {
       "name": "gobi",
       "description": "Manage the Gobi collaborative knowledge platform from the command line. Publish vault profiles, create posts and replies, generate images and videos.",
-      "version": "2.0.39",
+      "version": "2.0.40",
       "author": {
         "name": "gobi-ai"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "gobi",
   "description": "Manage the Gobi collaborative knowledge platform from the command line",
-  "version": "2.0.39",
+  "version": "2.0.40",
   "author": {
     "name": "gobi-ai"
   },

package/README.md

@@ -53,9 +53,9 @@ gobi vault publish
 # Sync local files with the webdrive
 gobi vault sync
 
-# Browse the global feed and create a personal post
-gobi global feed
-gobi global create-post --title "Hello" --content "Trying gobi"
+# Browse your personal feed and create a private post
+gobi personal feed
+gobi personal create-post --title "Hello" --content "Trying gobi"
 ```
 
 Each setup step unlocks a different family of commands — run only the ones the workflow needs:
@@ -74,7 +74,7 @@ Everything below applies whether you're building a Claude Code skill, an autonom
 
 ### JSON envelope
 
-Pass `--json` as a **global flag** (before the subcommand) and every command returns a structured envelope:
+Pass `--json` as a **top-level flag** (before the subcommand) and every command returns a structured envelope:
 
 ```sh
 gobi --json space list-posts
@@ -165,7 +165,7 @@ Public vaults are accessible at `https://gobispace.com/@{vaultSlug}`.
 
 ### Spaces
 
-A *Space* is a community knowledge area. A *Space Post* lives in one space. The same `Post` data type, in a different scope, is a *Personal Post* (see Global feed below) — so anything you can do to a Space Post you can do to a Personal Post.
+A *Space* is a community knowledge area. A *Space Post* lives in one space. The same `Post` data type, in a different scope, is a private *personal-space post* (see Personal space below) — so anything you can do to a Space Post you can do to a personal-space post.
 
 > Space and member administration (creating spaces, inviting/approving members, joining/leaving) is web-UI only and not available in the CLI.
 
@@ -184,34 +184,16 @@ A *Space* is a community knowledge area. A *Space Post* lives in one space. The
 | `gobi space edit-reply <replyId> [--content <c>] [--rich-text <json>]` | Edit a reply you authored. |
 | `gobi space delete-reply <replyId>` | Delete a reply you authored |
 
-### Global feed (personal posts)
-
-A *Personal Post* surfaces in the public global feed. Same `Post` model as a Space Post, scoped to the user instead of a space.
-
-| Command | Description |
-|---------|-------------|
-| `gobi global feed [--following]` | List the global public feed (posts + replies, newest first). `--following` limits to authors you follow. |
-| `gobi global list-posts [--mine]` | List personal posts; filter to your own |
-| `gobi global get-post <postId> [--full]` | Get a personal post with its ancestors and replies. `--full` shows reply content without truncation. |
-| `gobi global create-post [--title <t>] (--content <c> \| --rich-text <json>) [--artifact <artifactId>]… [--repost-post-id <id>] [--attach <file>]…` | Create a personal post. `--artifact` attaches an existing artifact to the post (repeatable). `--repost-post-id` reposts an existing post. `--attach` uploads local media for inline rendering (see `gobi space create-post` above for the mix rule). |
-| `gobi global edit-post <postId> [--title <t>] [--content <c>]` | Edit a personal post you authored. |
-| `gobi global delete-post <postId>` | Delete a personal post you authored |
-| `gobi global create-reply <postId> (--content <c> \| --rich-text <json>) [--attach <file>]…` | Create a reply to a personal post |
-| `gobi global edit-reply <replyId> [--content <c>] [--rich-text <json>]` | Edit a reply you authored. |
-| `gobi global delete-reply <replyId>` | Delete a reply you authored |
-
 ### Personal space (private posts)
 
-> Naming note: a **Personal Post** (under `gobi global`, above) is the public-feed kind — it lives on your vault profile and surfaces on the global feed. A **personal-space post** (this section, under `gobi personal`) is the private kind — same `Post` data model, but scoped via `personalSpaceUserId` so only you can see it.
-
-Private posts and replies visible only to you. Same `Post` data model and subcommand shape as `gobi global`, but scoped to a personal space — they never appear on the public global feed.
+Private posts and replies visible only to you. Same `Post` data model and subcommand shape as a Space Post, but scoped to a personal space — they never appear in any public feed.
 
 | Command | Description |
 |---------|-------------|
 | `gobi personal feed` | Your personal-space feed (posts + replies, newest first) |
 | `gobi personal list-posts` | List personal-space posts |
 | `gobi personal get-post <postId> [--full]` | Get a personal-space post with its ancestors and replies |
-| `gobi personal create-post [--title <t>] (--content <c> \| --rich-text <json>) [--artifact <artifactId>]… [--repost-post-id <id>] [--attach <file>]…` | Create a private post in your personal space. `--artifact` attaches an existing artifact to the post (repeatable). `--attach` works the same as on `gobi global create-post`. |
+| `gobi personal create-post [--title <t>] (--content <c> \| --rich-text <json>) [--artifact <artifactId>]… [--repost-post-id <id>] [--attach <file>]…` | Create a private post in your personal space. `--artifact` attaches an existing artifact to the post (repeatable). `--attach` works the same as on `gobi space create-post`. |
 | `gobi personal edit-post <postId> [--title <t>] [--content <c>]` | Edit a personal-space post you authored |
 | `gobi personal delete-post <postId>` | Delete a personal-space post you authored |
 | `gobi personal create-reply <postId> (--content <c> \| --rich-text <json>) [--attach <file>]…` | Reply to a personal-space post (inherits the parent's private scope) |
@@ -236,7 +218,7 @@ Like posts and artifacts, Sense data is **scoped to a space**: the subcommands l
 | `gobi <scope> conversations transcript <conversationId>` | Get a conversation's transcript and summary |
 | `gobi <scope> conversations audio <conversationId>` | Get a signed URL for the recording (owner-only) |
 
-`gobi space …` lists are a complete, fully-paginated per-space history (every member's records); add `--mine` to restrict either `list` to records you recorded. `gobi personal conversations list` is filtered from the user-global conversations feed, so it shows your recent personal conversations rather than a fully paginated history (`gobi personal activities list` is fully paginated).
+`gobi space …` lists are a complete, fully-paginated per-space history (every member's records); add `--mine` to restrict either `list` to records you recorded. `gobi personal conversations list` is filtered from the cross-scope conversations feed, so it shows your recent personal conversations rather than a fully paginated history (`gobi personal activities list` is fully paginated).
 
 ### Artifacts
 
@@ -277,7 +259,7 @@ Image, video, and avatar generation. See the `gobi-media` skill for full workflo
 | `gobi media list-videos` / `gobi media get-video <id>` | List or get videos |
 | `gobi media upload <file>` | Upload a local file and get a media id |
 
-### Global options
+### Top-level options
 
 | Option | Scope | Description |
 |--------|-------|-------------|
@@ -313,7 +295,7 @@ The CLI ships a `.claude-plugin/` manifest with skills that wrap the command gro
 |-------|--------|
 | `gobi-core` | Auth, update, space list/warp |
 | `gobi-vault` | `gobi vault init/list/publish/unpublish/sync` |
-| `gobi-space` | `gobi space …`, `gobi global …`, and `gobi personal …` |
+| `gobi-space` | `gobi space …` and `gobi personal …` |
 | `gobi-artifact` | `gobi personal artifact …` and `gobi space artifact …` |
 | `gobi-media` | `gobi media …` |
 | `gobi-sense` | `gobi personal activities/conversations …` and `gobi space activities/conversations …` |

package/commands/login.md

@@ -4,7 +4,7 @@ description: Log in to Gobi via Google OAuth
 argument-hint: ""
 ---
 
-Always use the globally installed `gobi` binary (not via npx or ts-node).
+Always use the installed `gobi` binary on your PATH (not via npx or ts-node).
 
 Log the user in to Gobi using device code flow:
 

package/commands/logout.md

@@ -4,7 +4,7 @@ description: Log out of Gobi and remove stored credentials
 argument-hint: ""
 ---
 
-Always use the globally installed `gobi` binary (not via npx or ts-node).
+Always use the installed `gobi` binary on your PATH (not via npx or ts-node).
 
 Run `gobi auth logout` to log out of Gobi.
 

package/commands/post.md

@@ -5,7 +5,7 @@ argument-hint: "[approval|bypass]"
 disable-model-invocation: true
 ---
 
-Always use the globally installed `gobi` binary (not via npx or ts-node).
+Always use the installed `gobi` binary on your PATH (not via npx or ts-node).
 
 ## Argument: permissionMode
 

package/commands/space-explore.md

@@ -4,17 +4,15 @@ description: Explore what's happening in the active Gobi space — posts and lea
 argument-hint: "[topic or keyword]"
 ---
 
-Always use the globally installed `gobi` binary (not via npx or ts-node).
+Always use the installed `gobi` binary on your PATH (not via npx or ts-node).
 
 Explore the active Gobi space to surface posts, topics, and learnings from others:
 
-1. Run these three commands in parallel:
+1. Run these two commands in parallel:
    - `gobi --json space list-posts` — recent posts in the space
    - `gobi --json space list-topics` — available topics in the space
-   - `gobi --json global feed` — recent posts and replies shared by members across the platform
-2. Display results in a readable summary, grouped by type (Topics / Space posts / Global feed).
+2. Display results in a readable summary, grouped by type (Topics / Space posts).
 3. If `$ARGUMENTS` is provided, filter or highlight entries relevant to that topic or keyword. If a matching topic is found, also run `gobi --json space list-topic-posts <topicSlug>` to show posts tagged with that topic.
 4. Ask the user if they'd like to read anything in full:
    - For a topic: run `gobi space list-topic-posts <topicSlug>` and show the posts.
    - For a space post: run `gobi space get-post <postId>` and show it with ancestors and replies.
-   - For a global feed post: run `gobi global get-post <postId>` to show it with ancestors and replies.

package/commands/space-share.md

@@ -1,10 +1,10 @@
 ---
 name: space-share
-description: Summarize recent learnings from this session and draft a personal post to share to the global feed.
+description: Summarize recent learnings from this session and draft a post to share to a Gobi space.
 argument-hint: "[context]"
 ---
 
-Always use the globally installed `gobi` binary (not via npx or ts-node).
+Always use the installed `gobi` binary on your PATH (not via npx or ts-node).
 
 ## Pre-flight check
 
@@ -16,7 +16,7 @@ gobi --json auth status
 
 Check that `.gobi/settings.yaml` exists. If you plan to publish to a Space (`gobi space create-post`), it must contain `selectedSpaceSlug` — otherwise stop and ask the user to run `gobi space warp` first.
 
-## Draft a personal post
+## Draft a post
 
 If `$ARGUMENTS` is provided, treat it as additional context or emphasis to guide the draft (e.g. "Emphasize the auth fix" or "Focus on the API design decision").
 
@@ -36,16 +36,16 @@ Focus on:
 
 Format the draft as a short post (2–5 bullet points max). Show it to the user and ask for confirmation before posting.
 
-Once confirmed, post it to the global feed:
+Once confirmed, post it to the active space:
 
 ```bash
-gobi global create-post --title "<short title>" --content "<confirmed content>"
+gobi space create-post --title "<short title>" --content "<confirmed content>"
 ```
 
-Or to the active space:
+Or keep it private in your personal space:
 
 ```bash
-gobi space create-post --title "<short title>" --content "<confirmed content>"
+gobi personal create-post --title "<short title>" --content "<confirmed content>"
 ```
 
 Confirm success and show the user the result.

package/commands/warp.md

@@ -6,7 +6,7 @@ argument-hint: "[spaceSlug]"
 
 Warp to a Gobi space:
 
-Always use the globally installed `gobi` binary (not npx or ts-node).
+Always use the installed `gobi` binary on your PATH (not npx or ts-node).
 
 - If a space slug is provided as `$ARGUMENTS`, run `gobi space warp $ARGUMENTS` directly.
 - If no argument is given:

package/dist/commands/personal.js

@@ -33,8 +33,8 @@ export function registerPersonalCommand(program) {
     const personal = program
         .command("personal")
         .description("Personal-space commands (private posts and replies visible only to you). " +
-        "Mirrors the `global` subcommand shape — posts/replies live in the same data " +
-        "model, scoped via personalSpaceUserId so they never surface on the public feed.");
+        "Posts/replies live in the same data model as space posts, scoped via " +
+        "personalSpaceUserId so they never surface on the public feed.");
     // ── Feed (unified) ──
     personal
         .command("feed")
@@ -166,13 +166,13 @@ export function registerPersonalCommand(program) {
     });
     // ── Get post (with ancestors and replies) ──
     //
-    // Same `/posts/:id` and `/posts/:id/ancestors` routes the global command
-    // uses — the server gates these by `viewerUserId`, so private rows
-    // resolve for the owner and 404 for everyone else. Personal-space posts
-    // and global posts share this endpoint without ambiguity.
+    // The shared `/posts/:id` and `/posts/:id/ancestors` routes — the server
+    // gates these by `viewerUserId`, so private rows resolve for the owner and
+    // 404 for everyone else. Personal-space and public posts share this
+    // endpoint without ambiguity.
     personal
         .command("get-post <postId>")
-        .description("Get a personal-space post with its ancestors and replies (paginated). Same endpoint as `gobi global get-post`; only the owner can resolve a private id.")
+        .description("Get a personal-space post with its ancestors and replies (paginated). Only the owner can resolve a private id.")
         .option("--limit <number>", "Items per page", "20")
         .option("--cursor <string>", "Pagination cursor from previous response")
         .option("--full", "Show full reply content without truncation")
@@ -246,9 +246,9 @@ export function registerPersonalCommand(program) {
     // ── Create post ──
     //
     // Targets `POST /posts/personal-space`, the only endpoint that stamps
-    // `personalSpaceUserId` on the row. Body shape is identical to the
-    // global `POST /posts` create (same CreatePostDto). The server skips the
-    // `@gobi` mention dispatch and the notification fan-out for this lane —
+    // `personalSpaceUserId` on the row. Body shape is identical to the public
+    // `POST /posts` create (same CreatePostDto). The server skips the
+    // agent mention dispatch and the notification fan-out for this lane —
     // private posts have no audience.
     personal
         .command("create-post")
@@ -258,7 +258,7 @@ export function registerPersonalCommand(program) {
         .option("--rich-text <richText>", "Rich-text JSON array (mutually exclusive with --content)")
         .option("--artifact <artifactId>", "Attach an existing artifact to the post (repeatable). Create artifacts with `gobi personal artifact create`.", (value, prev = []) => [...prev, value], [])
         .option("--attach <file>", "Local media or document file to attach. Repeatable. Mix rule: up to 4 photos + up to 4 document files (pdf/md/txt/csv) OR 1 GIF OR 1 video. Size ceilings: 10MB photos / 15MB GIFs / 512MB video / 250MB files.", (value, prev = []) => [...prev, value], [])
-        .option("--repost-post-id <postId>", "Wrap an existing top-level post as the embedded card on this new private post. The referenced post must be visible to you (your own personal-space post, a global-feed post, or a post in a space you're a member of). Reposting someone else's personal-space post returns 404.")
+        .option("--repost-post-id <postId>", "Wrap an existing top-level post as the embedded card on this new private post. The referenced post must be visible to you (your own personal-space post, a public post, or a post in a space you're a member of). Reposting someone else's personal-space post returns 404.")
         .action(async (opts) => {
         // A post is substantive if it has a text body OR carries an attachment
         // (artifact card / media) OR embeds a repost. Only block the truly empty
@@ -316,9 +316,9 @@ export function registerPersonalCommand(program) {
     });
     // ── Edit post ──
     //
-    // Same `PATCH /posts/:postId` route the global command uses — the server
-    // gates on `authorId === userId` and the read-path guard runs first, so
-    // a non-owner can't edit (or even discover) a private post.
+    // The shared `PATCH /posts/:postId` route — the server gates on
+    // `authorId === userId` and the read-path guard runs first, so a non-owner
+    // can't edit (or even discover) a private post.
     personal
         .command("edit-post <postId>")
         .description("Edit a post you authored in your personal space.")
@@ -386,8 +386,8 @@ export function registerPersonalCommand(program) {
     //
     // `POST /posts/:postId/replies` inherits scope from the parent on the
     // server — reply to a personal-space parent → reply is scoped to that
-    // personal space. The same command works for global and personal; we
-    // expose it here for discoverability/symmetry with `gobi global`.
+    // personal space. The same server route backs space and personal replies;
+    // we expose it here for discoverability under `gobi personal`.
     personal
         .command("create-reply <postId>")
         .description("Reply to a personal-space post. The reply inherits the parent's private scope automatically.")
@@ -516,7 +516,7 @@ export function registerPersonalCommand(program) {
                 pagination: resp.pagination,
             };
         },
-        // `/app/conversations` is user-global (all scopes, newest ~50, no paging);
+        // `/app/conversations` spans all the user's scopes (newest ~50, no paging);
         // filter to the personal scope (spaceId 0). Params are ignored — the endpoint
         // takes none.
         listConversations: async () => {

package/dist/commands/sense.js

@@ -109,7 +109,7 @@ export function registerActivitiesSubcommands(parent, scope, description) {
 //
 // Registers the `conversations` subcommand tree under `parent`. The `space`
 // group lists via `/spaces/:slug/conversations` (every member's, keyset-paged);
-// the `personal` group lists via the user-global `/app/conversations` filtered
+// the `personal` group lists via the cross-scope `/app/conversations` filtered
 // to the personal scope. Replaces the old top-level `gobi sense list-transcriptions`.
 export function registerConversationsSubcommands(parent, scope, description) {
     const conversations = parent.command("conversations").description(description);

package/dist/commands/space.js

@@ -732,7 +732,7 @@ export function registerSpaceCommand(program) {
         "human-owned; revisions form a draft/published tree (one published per artifact).");
     // ── Sense: activities + conversations (scoped to this space) ──
     //
-    // The conversations list endpoint is user-global (returns the caller's recent
+    // The conversations list endpoint spans all the user's scopes (returns the caller's recent
     // conversations across all scopes, each tagged with spaceId), so the scope
     // resolves this space's numeric id — via GET /spaces/:slug — to filter it.
     const senseScope = {

package/dist/commands/update.js

@@ -28,8 +28,8 @@ function detectInstallMethod() {
         return "brew";
     }
     try {
-        const npmGlobalDir = execSync("npm root -g", { encoding: "utf-8" }).trim();
-        if (gobiBin && gobiBin.includes(npmGlobalDir.replace("/lib/node_modules", ""))) {
+        const npmRootDir = execSync("npm root -g", { encoding: "utf-8" }).trim();
+        if (gobiBin && gobiBin.includes(npmRootDir.replace("/lib/node_modules", ""))) {
             return "npm";
         }
     }

package/dist/commands/utils.js

@@ -5,7 +5,7 @@ import { getSpaceSlug, getVaultSlug } from "./init.js";
 export function readStdin() {
     return readFileSync(0, "utf8");
 }
-// The global `--json` flag lives on the root program. Walk up the ancestry so
+// The top-level `--json` flag lives on the root program. Walk up the ancestry so
 // this works regardless of how deeply the calling command is nested (e.g. a
 // leaf under `gobi space artifact …`, not just a direct child of the program).
 export function isJsonMode(cmd) {

package/dist/main.js

@@ -5,7 +5,6 @@ import { ApiError, GobiError } from "./errors.js";
 import { registerAuthCommand } from "./commands/auth.js";
 import { commandRequiresSpace, commandRequiresVault, readSettings, } from "./commands/init.js";
 import { registerSpaceCommand } from "./commands/space.js";
-import { registerGlobalCommand } from "./commands/global.js";
 import { registerPersonalCommand } from "./commands/personal.js";
 import { registerVaultCommand } from "./commands/vault.js";
 import { registerUpdateCommand } from "./commands/update.js";
@@ -56,7 +55,6 @@ export async function cli() {
     // Register all command groups
     registerAuthCommand(program);
     registerSpaceCommand(program);
-    registerGlobalCommand(program);
     registerPersonalCommand(program);
     registerVaultCommand(program);
     registerUpdateCommand(program);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gobi-ai/cli",
-  "version": "2.0.39",
+  "version": "2.0.41",
   "description": "CLI client for the Gobi collaborative knowledge platform",
   "license": "MIT",
   "type": "module",

package/skills/gobi-artifact/SKILL.md

@@ -11,12 +11,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.39"
+  version: "2.0.40"
 ---
 
 # gobi-artifact
 
-Gobi artifact commands for versioned, post-attachable creations (v2.0.39).
+Gobi artifact commands for versioned, post-attachable creations (v2.0.40).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 
@@ -51,7 +51,7 @@ Markdown bodies can reference vault notes with `[[wikilinks]]`. Resolution again
 
 ## Important: JSON Mode
 
-For programmatic/agent usage, always pass `--json` as a **global** option (before everything else):
+For programmatic/agent usage, always pass `--json` as a **top-level** option (before everything else):
 
 ```bash
 gobi --json personal artifact list --limit 20

package/skills/gobi-artifact/references/personal.md

@@ -3,8 +3,8 @@
 ```
 Usage: gobi personal [options] [command]
 
-Personal-space commands (private posts and replies visible only to you). Mirrors the `global` subcommand shape — posts/replies live in the same data model, scoped via personalSpaceUserId so they
-never surface on the public feed.
+Personal-space commands (private posts and replies visible only to you). Posts/replies live in the same data model as space posts, scoped via personalSpaceUserId so they never surface on the public
+feed.
 
 Options:
   -h, --help                       display help for command

package/skills/gobi-core/SKILL.md

@@ -8,12 +8,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.39"
+  version: "2.0.40"
 ---
 
 # gobi-core
 
-Core CLI commands for the Gobi collaborative knowledge platform (v2.0.39).
+Core CLI commands for the Gobi collaborative knowledge platform (v2.0.40).
 
 ## Prerequisites
 
@@ -38,7 +38,6 @@ brew tap gobi-ai/tap && brew install gobi
 ## Key Concepts
 
 - **Vault**: A filetree-backed knowledge home. A local directory becomes a vault when it contains `.gobi/settings.yaml` with a `vaultSlug`. Each vault has a slug (e.g. `brave-path-zr962w`); public profile is configured by a `PUBLISH.md` document at the vault root and pushed via `gobi vault publish`.
-- **Personal Post**: A post on the author's profile that surfaces in the public global feed. Same `Post` data model as a Space Post — only the scope differs.
 - **Space Post**: A post inside a community space.
 - **Space**: A shared community knowledge area. A user can be a member of one or more spaces; each space contains posts, replies, and connected vaults.
 - **Artifact**: A versioned, human-owned creation (image, video, gif, markdown, or meeting_summary) attached to posts. Its revisions form a draft/published tree (at most one published). See the **gobi-artifact** skill.
@@ -78,14 +77,13 @@ gobi auth status
 | `vault init` | no (it sets it up) | no | – |
 | `space list` / `warp [slug]` / `get [slug]` | no | no | – |
 | `space list-topics` / `feed` / `list-posts` / `get-post` / `create-post` / `edit-post` / `delete-post` / `create-reply` / `edit-reply` / `delete-reply` / `list-topic-posts` | no | **yes** | parent `--space-slug <slug>` |
-| `global feed` / `list-posts` / `get-post` / `create-post` / `edit-post` / `delete-post` / `create-reply` / `edit-reply` / `delete-reply` | no | no | – |
 | `personal feed` / `list-posts` / `get-post` / `create-post` / `edit-post` / `delete-post` / `create-reply` / `edit-reply` / `delete-reply` | no | no | – |
 
 When a command needs vault or space and neither `.gobi` nor an override flag provides it, the CLI prints a one-line warning before the command runs (e.g. `Vault not set. Run 'gobi vault init' first, or pass --vault-slug.`). The warning is suppressed under `--json`.
 
 ## Important: JSON Mode
 
-For programmatic/agent usage, always pass `--json` as a **global** option (before the subcommand) to get structured JSON output:
+For programmatic/agent usage, always pass `--json` as a **top-level** option (before the subcommand) to get structured JSON output:
 
 ```bash
 gobi --json space list

package/skills/gobi-homepage/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.39"
+  version: "2.0.40"
 ---
 
 # Gobi Homepage Developer Guide

package/skills/gobi-media/SKILL.md

@@ -10,18 +10,18 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.39"
+  version: "2.0.40"
 ---
 
 # gobi-media
 
-Gobi media generation commands (v2.0.39).
+Gobi media generation commands (v2.0.40).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 
 ## Important: JSON Mode
 
-For programmatic/agent usage, always pass `--json` as a **global** option (before the subcommand):
+For programmatic/agent usage, always pass `--json` as a **top-level** option (before the subcommand):
 
 ```bash
 gobi --json media generate-image --prompt "a sunset over mountains"
@@ -52,7 +52,7 @@ The `-o` flag implies `--wait` and downloads the image when done.
   gobi space create-reply <postId> --content "<BODY>" --attach media/<NAME>.png
   ```
   This uploads to the CDN and renders the image as a slider on the post card. `--attach` is repeatable; mix rule is **4 photos OR 1 GIF OR 1 video**.
-- **Post-mention reply** (you were `@`-mentioned on a thread — `@gobi` / `@space:<slug>` — and your assistant body is auto-posted as the reply): **just write the text reply. Do not include the image as wiki-link, markdown image, or any URL.** The runtime detects every `gobi media generate-image` call you ran this turn and attaches those images to your auto-posted reply automatically. Embedding the image yourself either dangles (the workspace path doesn't resolve publicly) or duplicates the slider.
+- **Post-mention reply** (you were `@`-mentioned on a thread — `@space:<slug>` — and your assistant body is auto-posted as the reply): **just write the text reply. Do not include the image as wiki-link, markdown image, or any URL.** The runtime detects every `gobi media generate-image` call you ran this turn and attaches those images to your auto-posted reply automatically. Embedding the image yourself either dangles (the workspace path doesn't resolve publicly) or duplicates the slider.
 
 ### Key rules
 - Replace `<NAME>` with a descriptive slug — NEVER use example names like `sunset.png` literally.

package/skills/gobi-sense/SKILL.md

@@ -10,12 +10,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.39"
+  version: "2.0.40"
 ---
 
 # gobi-sense
 
-Gobi Sense commands for browsing activities and conversations (v2.0.39).
+Gobi Sense commands for browsing activities and conversations (v2.0.40).
 
 Requires gobi-cli installed and authenticated. See the **gobi-core** skill for setup.
 
@@ -39,7 +39,7 @@ The old `gobi sense list-activities` / `gobi sense list-transcriptions` commands
 
 ## Important: JSON Mode
 
-For programmatic/agent usage, always pass `--json` as a **global** option (before the subcommand):
+For programmatic/agent usage, always pass `--json` as a **top-level** option (before the subcommand):
 
 ```bash
 gobi --json personal activities list --limit 30
@@ -67,7 +67,7 @@ gobi --json space --space-slug my-team conversations transcript 12345
 gobi --json space --space-slug my-team conversations audio 12345
 ```
 
-Both list commands are newest-first and page with `--limit` / `--before` (pass a previous response's `nextCursor` to `--before`). Scope difference: **`gobi space … activities/conversations list`** is a complete, fully-paginated per-space history (every member's records). **`gobi personal … conversations list`** is filtered from the user-global conversations feed, so it shows your recent personal conversations rather than a fully paginated history (`gobi personal activities list` is fully paginated).
+Both list commands are newest-first and page with `--limit` / `--before` (pass a previous response's `nextCursor` to `--before`). Scope difference: **`gobi space … activities/conversations list`** is a complete, fully-paginated per-space history (every member's records). **`gobi personal … conversations list`** is filtered from the cross-scope conversations feed, so it shows your recent personal conversations rather than a fully paginated history (`gobi personal activities list` is fully paginated).
 
 ## Available Commands
 

package/skills/gobi-sense/references/personal.md

@@ -3,8 +3,8 @@
 ```
 Usage: gobi personal [options] [command]
 
-Personal-space commands (private posts and replies visible only to you). Mirrors the `global` subcommand shape — posts/replies live in the same data model, scoped via personalSpaceUserId so they
-never surface on the public feed.
+Personal-space commands (private posts and replies visible only to you). Posts/replies live in the same data model as space posts, scoped via personalSpaceUserId so they never surface on the public
+feed.
 
 Options:
   -h, --help                       display help for command