@gobi-ai/cli 2.0.26 → 2.0.28

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.26",
+  "version": "2.0.28",
   "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.26",
+      "version": "2.0.28",
       "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.26",
+  "version": "2.0.28",
   "author": {
     "name": "gobi-ai"
   },

package/README.md

@@ -138,10 +138,9 @@ If `.gobi/settings.yaml` is missing, `gobi vault init` and `gobi space warp` are
 
 | Command | Description |
 |---------|-------------|
-| `gobi vault create <slug> --name <n>` | Create a new vault. Does not change the configured vault — run `gobi vault init` or `gobi vault set-primary` afterwards if you want to anchor to it. |
+| `gobi vault create <slug> --name <n>` | Create a new vault. Does not change the configured vault — run `gobi vault init` afterwards if you want to anchor to it. |
 | `gobi vault rename <newName> [--vault-slug <slug>]` | Rename a vault. Defaults to the configured vault. Local display name only — does not affect `PUBLISH.md` frontmatter. |
 | `gobi vault delete <slug>` | Delete a vault. Irreversible. The API rejects if the vault still owns content; clean up posts, members, and files first. |
-| `gobi vault set-primary <slug>` | Mark a vault as your primary. Unsets primary on the others. |
 | `gobi vault publish` | Upload `PUBLISH.md` to your vault. Triggers profile/metadata refresh. |
 | `gobi vault unpublish` | Remove `PUBLISH.md` from your vault. |
 | `gobi vault status [--vault-slug <slug>]` | Show the configured vault's publish state (`isPublished`), profile fields, file count, and public profile URL. Useful as a pre-flight check before authoring a markdown artifact with `--auto-attachments`. |
@@ -178,31 +177,29 @@ A *Space* is a community knowledge area. A *Space Post* lives in one space. The
 | `gobi space list-topic-posts <topicSlug>` | List posts tagged with a topic |
 | `gobi space list-posts` | List posts in the space |
 | `gobi space get-post <postId> [--full]` | Get a post with its ancestors and replies. `--full` shows reply content without truncation. |
-| `gobi space create-post [--title <t>] (--content <c> \| --rich-text <json>) [--vault-slug <slug>] [--repost-post-id <id>] [--attach <file>]…` | Create a space post. Must provide content via `--content` or `--rich-text`. `--vault-slug` attributes it to a vault you own. `--repost-post-id` reposts an existing post (sets `repostPostId` on the new post). `--attach` uploads local media to render inline in-feed (repeatable; X-style mix rule — up to 4 photos OR 1 GIF OR 1 video). |
-| `gobi space edit-post <postId> [--title <t>] [--content <c>] [--vault-slug <slug>]` | Edit a space post. `--vault-slug ""` detaches the vault. |
+| `gobi space create-post [--title <t>] (--content <c> \| --rich-text <json>) [--artifact <artifactId>]… [--repost-post-id <id>] [--attach <file>]…` | Create a space post. Must provide content via `--content` or `--rich-text`. `--artifact` attaches an existing artifact to the post (repeatable). `--repost-post-id` reposts an existing post (sets `repostPostId` on the new post). `--attach` uploads local media to render inline in-feed (repeatable; X-style mix rule — up to 4 photos OR 1 GIF OR 1 video). |
+| `gobi space edit-post <postId> [--title <t>] [--content <c>]` | Edit a space post. |
 | `gobi space delete-post <postId>` | Delete a space post |
-| `gobi space create-reply <postId> (--content <c> \| --rich-text <json>) [--vault-slug <slug>] [--attach <file>]…` | Create a reply to a space post. `--attach` works the same as on `create-post`. |
-| `gobi space edit-reply <replyId> [--content <c>] [--rich-text <json>] [--vault-slug <slug>]` | Edit a reply you authored. `--vault-slug ""` detaches attribution. |
+| `gobi space create-reply <postId> (--content <c> \| --rich-text <json>) [--attach <file>]…` | Create a reply to a space post. `--attach` works the same as on `create-post`. |
+| `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. Pass `--vault-slug` to attribute it to a vault you own (it'll then surface on that vault's profile too); with no `--vault-slug` the post has no `authorVaultSlug` and lives only on the global feed. Same `Post` model as a Space Post, scoped to the user instead of a space.
+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] [--vault-slug <slug>]` | List personal posts; filter to your own or by author vault |
+| `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>) [--vault-slug <slug>] [--repost-post-id <id>] [--attach <file>]…` | Create a personal post. `--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>] [--vault-slug <slug>]` | Edit a personal post you authored. `--vault-slug ""` detaches the vault. |
+| `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>) [--vault-slug <slug>] [--attach <file>]…` | Create a reply to a personal post |
-| `gobi global edit-reply <replyId> [--content <c>] [--rich-text <json>] [--vault-slug <slug>]` | Edit a reply you authored. `--vault-slug ""` detaches attribution. |
+| `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 |
 
-`--vault-slug` requires that the caller hold `role: 'owner'` on the target vault. When set, it becomes the post's `authorVaultSlug`.
-
 ### 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.
@@ -214,11 +211,11 @@ Private posts and replies visible only to you. Same `Post` data model and subcom
 | `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>) [--vault-slug <slug>] [--repost-post-id <id>] [--attach <file>]…` | Create a private post in your personal space. `--vault-slug` attributes it to a vault you own. `--attach` works the same as on `gobi global create-post`. |
-| `gobi personal edit-post <postId> [--title <t>] [--content <c>] [--vault-slug <slug>]` | Edit a personal-space post you authored |
+| `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 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>) [--vault-slug <slug>] [--attach <file>]…` | Reply to a personal-space post (inherits the parent's private scope) |
-| `gobi personal edit-reply <replyId> [--content <c>] [--rich-text <json>] [--vault-slug <slug>]` | Edit a reply 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) |
+| `gobi personal edit-reply <replyId> [--content <c>] [--rich-text <json>]` | Edit a reply you authored |
 | `gobi personal delete-reply <replyId>` | Delete a reply you authored |
 
 ### Sense

package/commands/space-share.md

@@ -14,7 +14,7 @@ First, verify the user is set up:
 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. `vaultSlug` is optional for `gobi global create-post`; if missing the post is created without an `authorVaultSlug` (vault-less). Run `gobi vault init` if the user wants the post attributed to a vault they own.
+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
 

package/dist/commands/global.js

@@ -8,14 +8,7 @@ function readContent(value) {
     return value;
 }
 function buildPersonalPostUrl(post) {
-    const id = post.id;
-    const vaultSlug = post.vault?.vaultSlug ||
-        post.authorVault?.vaultSlug ||
-        post.authorVaultSlug ||
-        undefined;
-    return vaultSlug
-        ? `${WEB_BASE_URL}/@${vaultSlug}?postId=${id}`
-        : `${WEB_BASE_URL}/posts/${id}`;
+    return `${WEB_BASE_URL}/posts/${post.id}`;
 }
 function formatFeedLine(m) {
     const isReply = m.parentPostId != null ||
@@ -79,7 +72,6 @@ export function registerGlobalCommand(program) {
         .option("--limit <number>", "Items per page", "20")
         .option("--cursor <string>", "Pagination cursor from previous response")
         .option("--mine", "Only include posts authored by you")
-        .option("--vault-slug <vaultSlug>", "Filter by author vault slug")
         .action(async (opts) => {
         const params = {
             limit: parseInt(opts.limit, 10),
@@ -88,8 +80,6 @@ export function registerGlobalCommand(program) {
             params.cursor = opts.cursor;
         if (opts.mine)
             params.mine = "true";
-        if (opts.vaultSlug)
-            params.vaultSlug = opts.vaultSlug;
         const resp = (await apiGet(`/posts`, params));
         if (isJsonMode(global)) {
             jsonOut({
@@ -108,10 +98,7 @@ export function registerGlobalCommand(program) {
         for (const t of items) {
             const author = t.author?.name ||
                 `User ${t.authorId}`;
-            const vaultSlug = t.vault?.vaultSlug ||
-                t.authorVault?.vaultSlug ||
-                "?";
-            lines.push(`- [${t.id}] "${t.title}" by ${author} (vault: ${vaultSlug}, ${t.replyCount ?? 0} replies, ${t.createdAt})`);
+            lines.push(`- [${t.id}] "${t.title}" by ${author} (${t.replyCount ?? 0} replies, ${t.createdAt})`);
         }
         const footer = pagination.hasMore ? `\n  Next cursor: ${pagination.nextCursor}` : "";
         console.log(`Posts (${items.length} items):\n` + lines.join("\n") + footer);
@@ -146,9 +133,6 @@ export function registerGlobalCommand(program) {
         const replies = (data.replies || []);
         const author = post.author?.name ||
             `User ${post.authorId}`;
-        const vault = post.vault?.vaultSlug ||
-            post.authorVault?.vaultSlug ||
-            "?";
         const ancestorLines = [];
         if (ancestors.length) {
             ancestors.forEach((a, i) => {
@@ -169,7 +153,7 @@ export function registerGlobalCommand(program) {
             : `Post: ${post.title || "(no title)"}`;
         const output = [
             heading,
-            `By: ${author} (vault: ${vault}) on ${post.createdAt}`,
+            `By: ${author} on ${post.createdAt}`,
             ...(ancestorLines.length
                 ? ["", `Ancestors (${ancestors.length} items, root first):`, ...ancestorLines]
                 : []),

package/dist/commands/personal.js

@@ -93,10 +93,7 @@ export function registerPersonalCommand(program) {
         }
         const lines = [];
         for (const t of items) {
-            const vaultSlug = t.vault?.vaultSlug ||
-                t.authorVault?.vaultSlug ||
-                "—";
-            lines.push(`- [${t.id}] "${t.title ?? "(no title)"}" (vault: ${vaultSlug}, ${t.replyCount ?? 0} replies, ${t.createdAt})`);
+            lines.push(`- [${t.id}] "${t.title ?? "(no title)"}" (${t.replyCount ?? 0} replies, ${t.createdAt})`);
         }
         const footer = pagination.hasMore ? `\n  Next cursor: ${pagination.nextCursor}` : "";
         console.log(`Personal-space posts (${items.length} of ${allItems.length} feed items):\n` +
@@ -138,9 +135,6 @@ export function registerPersonalCommand(program) {
         const replies = (data.replies || []);
         const author = post.author?.name ||
             `User ${post.authorId}`;
-        const vault = post.vault?.vaultSlug ||
-            post.authorVault?.vaultSlug ||
-            "—";
         const ancestorLines = [];
         if (ancestors.length) {
             ancestors.forEach((a, i) => {
@@ -161,7 +155,7 @@ export function registerPersonalCommand(program) {
             : `Post: ${post.title || "(no title)"} (private)`;
         const output = [
             heading,
-            `By: ${author} (vault: ${vault}) on ${post.createdAt}`,
+            `By: ${author} on ${post.createdAt}`,
             ...(ancestorLines.length
                 ? ["", `Ancestors (${ancestors.length} items, root first):`, ...ancestorLines]
                 : []),

package/dist/commands/vault.js

@@ -20,7 +20,7 @@ export function registerVaultCommand(program) {
     });
     vault
         .command("create <slug>")
-        .description("Create a new vault. <slug> must be unique (use 'gobi vault list' to see existing slugs); --name sets the display name. Does not change the configured vault — run 'gobi vault init' or 'gobi vault set-primary' afterwards if you want to anchor to it.")
+        .description("Create a new vault. <slug> must be unique (use 'gobi vault list' to see existing slugs); --name sets the display name. Does not change the configured vault — run 'gobi vault init' afterwards if you want to anchor to it.")
         .requiredOption("--name <name>", "Display name for the new vault")
         .action(async (slug, opts) => {
         const resp = (await apiPost("/vault", {
@@ -61,20 +61,6 @@ export function registerVaultCommand(program) {
         }
         console.log(`Deleted vault [${slug}].`);
     });
-    vault
-        .command("set-primary <slug>")
-        .description("Mark a vault as your primary. Unsets primary on the other vaults you own. Slug must be passed explicitly.")
-        .action(async (slug) => {
-        const resp = (await apiPatch(`/vault/${slug}`, {
-            isPrimary: true,
-        }));
-        const v = unwrapResp(resp);
-        if (isJsonMode(vault)) {
-            jsonOut(v);
-            return;
-        }
-        console.log(`Set [${slug}] as primary vault.`);
-    });
     vault
         .command("list")
         .description("List vaults you own.")
@@ -96,8 +82,7 @@ export function registerVaultCommand(program) {
         const lines = [];
         for (const v of items) {
             const slug = (v.vaultId || v.slug);
-            const isPrimary = v.isPrimary ? " (primary)" : "";
-            lines.push(`- [${slug}] ${v.name}${isPrimary}`);
+            lines.push(`- [${slug}] ${v.name}`);
         }
         console.log(`Vaults (${items.length}):\n` + lines.join("\n"));
     });
@@ -122,7 +107,6 @@ export function registerVaultCommand(program) {
         const status = {
             vaultSlug: slug,
             name: v.name,
-            isPrimary: !!v.isPrimary,
             isPublished,
             title: v.title ?? null,
             description: v.description ?? null,
@@ -140,7 +124,7 @@ export function registerVaultCommand(program) {
             return;
         }
         const lines = [
-            `Vault: [${slug}] ${v.name}${v.isPrimary ? " (primary)" : ""}`,
+            `Vault: [${slug}] ${v.name}`,
             `  Published: ${isPublished ? "yes" : "no"}`,
         ];
         if (!isPublished) {

package/package.json

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

package/skills/gobi-artifact/SKILL.md

@@ -9,12 +9,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.26"
+  version: "2.0.28"
 ---
 
 # gobi-artifact
 
-Gobi artifact commands for versioned, post-attachable creations (v2.0.26).
+Gobi artifact commands for versioned, post-attachable creations (v2.0.28).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 

package/skills/gobi-core/SKILL.md

@@ -8,12 +8,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.26"
+  version: "2.0.28"
 ---
 
 # gobi-core
 
-Core CLI commands for the Gobi collaborative knowledge platform (v2.0.26).
+Core CLI commands for the Gobi collaborative knowledge platform (v2.0.28).
 
 ## Prerequisites
 
@@ -77,16 +77,8 @@ 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` / `delete-post` / `create-reply` / `edit-reply` / `delete-reply` | no | no | – |
-| `global create-post` | optional¹ | no | command-level `--vault-slug <slug>` |
-| `global edit-post` | optional² | no | command-level `--vault-slug <slug>` |
-| `personal feed` / `list-posts` / `get-post` / `delete-post` / `create-reply` / `edit-reply` / `delete-reply` | no | no | – |
-| `personal create-post` | optional¹ | no | command-level `--vault-slug <slug>` |
-| `personal edit-post` | optional² | no | command-level `--vault-slug <slug>` |
-
-¹ `global create-post` accepts `--vault-slug`, optional. With no flag and no `vaultSlug` in `.gobi`, the post is created with no `authorVaultSlug` (vault-less personal post) — same as a Space post that isn't attributed to any vault. Set `--vault-slug` to attribute it.
-
-² `global edit-post` only consults `--vault-slug` when you pass it explicitly. Use `--vault-slug ""` to detach an existing attribution; non-empty re-attaches.
+| `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`.
 

package/skills/gobi-homepage/SKILL.md

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

package/skills/gobi-media/SKILL.md

@@ -10,12 +10,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.26"
+  version: "2.0.28"
 ---
 
 # gobi-media
 
-Gobi media generation commands (v2.0.26).
+Gobi media generation commands (v2.0.28).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 

package/skills/gobi-sense/SKILL.md

@@ -7,12 +7,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.26"
+  version: "2.0.28"
 ---
 
 # gobi-sense
 
-Gobi sense commands for activity and transcription data (v2.0.26).
+Gobi sense commands for activity and transcription data (v2.0.28).
 
 Requires gobi-cli installed and authenticated. See the **gobi-core** skill for setup.
 

package/skills/gobi-space/SKILL.md

@@ -11,12 +11,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.26"
+  version: "2.0.28"
 ---
 
 # gobi-space
 
-Gobi space, global, and personal-space posts (v2.0.26).
+Gobi space, global, and personal-space posts (v2.0.28).
 
 Requires gobi-cli installed and authenticated. See the **gobi-core** skill for setup.
 
@@ -25,10 +25,10 @@ Requires gobi-cli installed and authenticated. See the **gobi-core** skill for s
 The same `Post` data type drives all three surfaces — the difference is **scope**:
 
 - **Space Post** — `gobi space …` — lives in a community space's feed.
-- **Personal Post** — `gobi global …` — surfaces in the public global feed. When attributed via `--vault-slug` it also surfaces on that vault's profile; with no vault attribution it lives only on the global feed.
+- **Personal Post** — `gobi global …` — lives on the public global feed.
 - **Personal-space Post** — `gobi personal …` — private posts and replies visible only to the author. Same shape as `gobi global`, scoped via `personalSpaceUserId` so they never surface on the public feed.
 
-Anything you can do to a Space Post (reply, edit, delete, attribute to a vault) you can do to a Personal Post or a Personal-space Post.
+Anything you can do to a Space Post (reply, edit, delete) you can do to a Personal Post or a Personal-space Post.
 
 - When the user wants to explore or catch up on what's happening in their space, invoke `/gobi:space-explore`.
 - When the user wants to share or post learnings from the current session, invoke `/gobi:space-share`.
@@ -45,9 +45,9 @@ Anything you can do to a Space Post (reply, edit, delete, attribute to a vault)
 
 The same applies to replies: a reply has only `--content` (no title), so do not synthesize a title-like heading at the top of a reply either.
 
-## Author vault attribution (`--vault-slug`)
+## Attaching artifacts (`--artifact`)
 
-`create-post` / `edit-post` across all three scopes (`gobi space`, `gobi global`, `gobi personal`) accept `--vault-slug <slug>`. When set, the slug becomes the post's `authorVaultSlug` — the vault the user is posting on behalf of. The caller must hold `role: 'owner'` on that vault. Pass `--vault-slug ""` on edit to detach.
+Posts have no vault attribution. `create-post` across all three scopes (`gobi space`, `gobi global`, `gobi personal`) accepts `--artifact <artifactId>` (repeatable) to attach existing artifacts to the post. To author a vault-anchored document, create a markdown artifact (`gobi artifact create --kind markdown --vault-slug <slug>`) and attach it via `--artifact`. See the **gobi-artifact** skill.
 
 > **Wiki-link uploads moved to artifacts.** The `--auto-attachments` flag that used to upload `[[wiki-linked files]]` from a post body now lives on `gobi artifact create` / `gobi artifact revise` (markdown kinds). To publish a markdown creation with resolvable wikilinks, create a markdown artifact with `--vault-slug` + `--auto-attachments` and attach it to the post (`--post-id`). See the **gobi-artifact** skill. Before relying on wikilink resolution, confirm the anchor vault is published: `gobi --json vault status --vault-slug <slug>` should report `isPublished: true`.
 
@@ -63,13 +63,12 @@ Use `--attach` for media you want shown in the post itself; use a markdown **art
 
 Once a post is created, you can build a shareable URL from the response:
 
-- **Personal post on a vault** — `https://gobispace.com/@{authorVaultSlug}?postId={id}` (e.g. `https://gobispace.com/@jyk?postId=144869`). This is the canonical share link for `gobi global` posts attributed to a vault.
-- **Personal post without a vault** (created with no `--vault-slug`) — use `https://gobispace.com/posts/{id}` as a direct fallback.
+- **Personal post** — `https://gobispace.com/posts/{id}` (e.g. `https://gobispace.com/posts/144869`). This is the canonical share link for `gobi global` posts.
 - **Space post** — `https://gobispace.com/spaces/{spaceSlug}?postId={id}` (overlay on the space feed) or `https://gobispace.com/spaces/{spaceSlug}/posts/{id}` (dedicated page).
 - **Vault profile** — `https://gobispace.com/@{vaultSlug}`.
 - **Vault file** — `https://gobispace.com/file/{vaultSlug}?path={path}` (e.g. `https://gobispace.com/file/jyk?path=notes/intro.md`). First-class URL for linking to a single file from a published vault — renders in the main feed chrome (not the vault homepage). Use this when a post body or reply needs to point readers at a specific vault file. URL-encode each path segment. See **gobi-vault** skill for full semantics.
 
-When you echo a "Post created!" line (or the JSON response is consumed by another agent), include the assembled URL using the fields actually returned (`id`, `authorVaultSlug`, `spaceSlug`) — don't fabricate slugs.
+When you echo a "Post created!" line (or the JSON response is consumed by another agent), include the assembled URL using the fields actually returned — `id` for global posts, `spaceSlug` + `id` for space posts. Don't fabricate slugs.
 
 ## Prerequisites & space slug
 
@@ -84,7 +83,7 @@ When you echo a "Post created!" line (or the JSON response is consumed by anothe
 
 If `.gobi/settings.yaml` has no `selectedSpaceSlug` and `--space-slug` isn't passed, the command will error.
 
-`gobi global` commands target the public global feed and have no space requirement and no `.gobi` requirement. `gobi global create-post` is symmetric with `gobi space create-post`: a vault is **optional** — pass `--vault-slug <slug>` to attribute the post; with no flag the post is created without an `authorVaultSlug`.
+`gobi global` commands target the public global feed and have no space requirement and no `.gobi` requirement. `gobi global create-post` is symmetric with `gobi space create-post`: attach existing artifacts with `--artifact <artifactId>` (repeatable).
 
 ## Important: JSON Mode
 
@@ -112,8 +111,8 @@ gobi --json space list-posts
 ### Space posts
 - `gobi space list-posts` — List posts in a space (paginated).
 - `gobi space get-post <postId>` — Get a post with its ancestors and replies (paginated). Ancestors and replies are returned together; there is no separate `ancestors` or `list-replies` command.
-- `gobi space create-post` — Create a space post. `--vault-slug` attributes it to a vault you own.
-- `gobi space edit-post <postId>` — Edit a space post. You must be the author. `--vault-slug ""` detaches the vault.
+- `gobi space create-post` — Create a space post. `--artifact <artifactId>` (repeatable) attaches existing artifacts.
+- `gobi space edit-post <postId>` — Edit a space post. You must be the author.
 - `gobi space delete-post <postId>` — Delete a space post. You must be the author.
 
 ### Space replies
@@ -126,25 +125,25 @@ gobi --json space list-posts
 `gobi global` is the same surface for Personal Posts — posts that live on the author's profile and surface in the public global feed.
 
 - `gobi global feed` — List the public global feed (posts and replies, newest first).
-- `gobi global list-posts` — List personal posts. `--mine` for your own; `--vault-slug <slug>` to filter by author vault.
+- `gobi global list-posts` — List personal posts. `--mine` for your own.
 - `gobi global get-post <postId>` — Get a personal post with its ancestors and replies.
-- `gobi global create-post` — Create a personal post. `--vault-slug` works the same as on `space create-post`. It is optional: with no flag, the post is created without an `authorVaultSlug` (vault-less personal post).
-- `gobi global edit-post <postId>` — Edit a personal post you authored. `--vault-slug ""` detaches the vault.
+- `gobi global create-post` — Create a personal post. `--artifact <artifactId>` (repeatable) attaches existing artifacts.
+- `gobi global edit-post <postId>` — Edit a personal post you authored.
 - `gobi global delete-post <postId>` — Delete a personal post you authored.
 - `gobi global create-reply <postId>` — Reply to a personal post.
-- `gobi global edit-reply <replyId>` — Edit a reply you authored. Accepts `--vault-slug` for author attribution (mirrors `space edit-reply`).
+- `gobi global edit-reply <replyId>` — Edit a reply you authored.
 - `gobi global delete-reply <replyId>` — Delete a reply you authored.
 
 ### Personal-space posts (private)
 
 `gobi personal` mirrors `gobi global`'s subcommand and write-flag shape, but every row is scoped to a private personal space (`personalSpaceUserId`). Nothing here surfaces on the public global feed — these posts are visible only to you. Use for private notes-as-posts, scratch drafts, or any post you want to author against your vault without making it public.
 
-A couple of read-side flags don't mirror — `personal feed` has no `--following` (there's no follow graph in a private space), and `personal list-posts` has no `--mine` / `--vault-slug` (everything in the personal space is already yours).
+A couple of read-side flags don't mirror — `personal feed` has no `--following` (there's no follow graph in a private space), and `personal list-posts` has no `--mine` (everything in the personal space is already yours).
 
 - `gobi personal feed` — Your personal-space feed (posts and replies, newest first).
 - `gobi personal list-posts` — List your personal-space posts.
 - `gobi personal get-post <postId>` — Get a personal-space post with its ancestors and replies.
-- `gobi personal create-post` — Create a private personal-space post. Same flags as `gobi global create-post` (`--vault-slug`, `--repost-post-id`, `--attach`).
+- `gobi personal create-post` — Create a private personal-space post. Same flags as `gobi global create-post` (`--artifact`, `--repost-post-id`, `--attach`).
 - `gobi personal edit-post <postId>` — Edit a personal-space post you authored.
 - `gobi personal delete-post <postId>` — Delete a personal-space post you authored.
 - `gobi personal create-reply <postId>` — Reply to a personal-space post (inherits the parent's private scope).
@@ -153,7 +152,7 @@ A couple of read-side flags don't mirror — `personal feed` has no `--following
 
 ## Confirm before mutating
 
-Most posts and replies are publicly visible — in a community space (`gobi space …`) or in the global feed (`gobi global …`). `gobi personal …` is the exception: those rows are private to the author. Either way, before running any write, confirm with the user — show the exact command and the resolved title, content (or a short preview), and `authorVaultSlug` if `--vault-slug` is set. This applies even when running autonomously.
+Most posts and replies are publicly visible — in a community space (`gobi space …`) or in the global feed (`gobi global …`). `gobi personal …` is the exception: those rows are private to the author. Either way, before running any write, confirm with the user — show the exact command and the resolved title, content (or a short preview), and any attached artifact ids. This applies even when running autonomously.
 
 - `create-post` / `create-reply` — content goes live on submission.
 - `edit-post` / `edit-reply` — confirm the *new* content; people who already saw the original may re-see it.

package/skills/gobi-space/references/global.md

@@ -43,11 +43,10 @@ Usage: gobi global list-posts [options]
 List posts in the global feed (paginated). Pass --mine to limit to your own posts.
 
 Options:
-  --limit <number>          Items per page (default: "20")
-  --cursor <string>         Pagination cursor from previous response
-  --mine                    Only include posts authored by you
-  --vault-slug <vaultSlug>  Filter by author vault slug
-  -h, --help                display help for command
+  --limit <number>   Items per page (default: "20")
+  --cursor <string>  Pagination cursor from previous response
+  --mine             Only include posts authored by you
+  -h, --help         display help for command
 ```
 
 ## get-post

package/skills/gobi-vault/SKILL.md

@@ -8,12 +8,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.26"
+  version: "2.0.28"
 ---
 
 # gobi-vault
 
-Gobi vault commands for publishing your vault profile and syncing files (v2.0.26).
+Gobi vault commands for publishing your vault profile and syncing files (v2.0.28).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 
@@ -23,7 +23,7 @@ Most `gobi vault …` commands resolve the target vault from the current directo
 
 Exceptions:
 - `vault init`, `vault list`, `vault create <slug>` — no `.gobi` required.
-- `vault delete <slug>`, `vault set-primary <slug>` — slug is a positional, no `.gobi` fallback.
+- `vault delete <slug>` — slug is a positional, no `.gobi` fallback.
 - `vault rename <newName>`, `vault status` — accept an optional `--vault-slug <slug>` to target a vault other than the one in `.gobi`.
 
 ## Gobi Vault
@@ -41,11 +41,10 @@ gobi --json vault publish
 ## Available Commands
 
 - `gobi vault init` — Interactive: select an existing vault or create a new one. Writes `vaultSlug` to `.gobi/settings.yaml` in the current directory and seeds `PUBLISH.md`. Requires the user to be logged in (`gobi auth login`).
-- `gobi vault list` — List vaults you own. The primary vault is marked.
+- `gobi vault list` — List vaults you own.
 - `gobi vault status` — Show the configured vault's publish state (`isPublished`), profile fields (`title`, `description`, `tags`), referenced files (`thumbnailPath`, `homepagePath`, `promptPath`), file count, and the public profile URL. Use this as a diagnostic before authoring a markdown artifact with `--auto-attachments` (see gobi-artifact skill) to confirm the vault is public — files uploaded to a non-public vault are stored on webdrive but are not visible at `gobispace.com/@{vaultSlug}` until you run `gobi vault publish`.
-- `gobi vault create <slug> --name <name>` — Create a new vault with the given slug and display name. Slug must be unique (use `vault list` to see what's taken). Does not change the configured vault — run `vault init` here or `vault set-primary <slug>` afterwards if you want to anchor to it.
+- `gobi vault create <slug> --name <name>` — Create a new vault with the given slug and display name. Slug must be unique (use `vault list` to see what's taken). Does not change the configured vault — run `vault init` here afterwards if you want to anchor to it.
 - `gobi vault rename <newName>` — Rename the configured vault's display name. Pass `--vault-slug <slug>` to target another vault. Local handle only — the public profile title comes from `PUBLISH.md` frontmatter and is unaffected.
-- `gobi vault set-primary <slug>` — Mark a vault as your primary. Unsets primary on the others. Required arg, no `.gobi` fallback (avoids accidental promotion).
 - `gobi vault delete <slug>` — Delete a vault. Irreversible. Required arg, no `.gobi` fallback. The API will reject if the vault still owns content; clean up posts, members, and files first.
 - `gobi vault publish` — Upload `PUBLISH.md` to the vault root on webdrive. Triggers post-processing (vault profile sync, metadata update).
 - `gobi vault unpublish` — Delete `PUBLISH.md` from the vault on webdrive.
@@ -56,11 +55,10 @@ gobi --json vault publish
 Once a vault is published (i.e. `gobi vault status` reports `isPublished: yes`), it is reachable at predictable URLs:
 
 - **Vault profile** — `https://gobispace.com/@{vaultSlug}` (e.g. `https://gobispace.com/@jyk`).
-- **Direct link to a personal post on the vault** — `https://gobispace.com/@{vaultSlug}?postId={postId}` (e.g. `https://gobispace.com/@jyk?postId=144869`). Open in the vault profile with that post focused.
 - **Direct link to a vault file** — `https://gobispace.com/file/{vaultSlug}?path={path}` (e.g. `https://gobispace.com/file/jyk?path=notes/intro.md`). This is the first-class URL for sharing a single file from a vault — use it whenever you want a reader to land on one specific file. The page renders inside the main feed chrome (sidebar + header), so readers stay in `gobispace.com` instead of pivoting to the vault homepage. Paths without an extension are treated as markdown (the same wikilink-stem resolution webdrive uses), so `?path=intro` and `?path=intro.md` both resolve. URL-encode each path segment when assembling.
 - **Custom homepage** — when `homepage` is set in `PUBLISH.md` frontmatter, the vault profile URL renders that HTML file. See **gobi-homepage** skill.
 
-When linking back to your own posts or files, assemble the URL from concrete fields (the post's `authorVaultSlug` + `id`, or the vault's `vaultSlug` + the file's path) rather than guessing.
+When linking to a vault file, assemble the URL from concrete fields (the vault's `vaultSlug` + the file's path) rather than guessing.
 
 ## Confirm before mutating
 
@@ -70,7 +68,6 @@ Every command in this skill writes external state — webdrive files and the pub
 - `vault unpublish` — removes the live profile. Always confirm.
 - `vault sync` — can overwrite remote or local files. Run `--dry-run` first and show the user the plan before re-running without `--dry-run`. With `--conflict server` or `--conflict client`, name which side is going to be overwritten.
 - `vault delete <slug>` — irreversible; cannot undo. Confirm the slug and that the user actually means to delete *that* vault before running.
-- `vault set-primary <slug>` — flips which vault is treated as primary across the user's account. Confirm the target.
 - `vault create` / `vault rename` — creating spends a slug permanently; renaming is reversible but visible. Show the user the resolved slug + name before running.
 
 ## PUBLISH.md Frontmatter Reference

package/skills/gobi-vault/references/vault.md

@@ -11,12 +11,11 @@ Options:
 Commands:
   init                        Select or create the vault for the current directory. Writes .gobi/settings.yaml and seeds PUBLISH.md.
   create [options] <slug>     Create a new vault. <slug> must be unique (use 'gobi vault list' to see existing slugs); --name sets the display name. Does not change the configured vault — run 'gobi
-                              vault init' or 'gobi vault set-primary' afterwards if you want to anchor to it.
+                              vault init' afterwards if you want to anchor to it.
   rename [options] <newName>  Rename a vault. Defaults to the configured vault (.gobi/settings.yaml); pass --vault-slug to target another. Does not affect PUBLISH.md frontmatter (which controls the
                               public profile title) — this is the local display name only.
   delete <slug>               Delete a vault. Irreversible. Slug must be passed explicitly (no .gobi fallback). The API will reject if the vault still owns content; clean up posts, members, and files
                               first.
-  set-primary <slug>          Mark a vault as your primary. Unsets primary on the other vaults you own. Slug must be passed explicitly.
   list                        List vaults you own.
   status [options]            Show the configured vault's publish state and metadata (use before authoring a markdown artifact with --auto-attachments to confirm the vault is public).
   publish                     Upload PUBLISH.md to the vault root on webdrive. Triggers post-processing (vault sync, metadata update).
@@ -41,8 +40,8 @@ Options:
 ```
 Usage: gobi vault create [options] <slug>
 
-Create a new vault. <slug> must be unique (use 'gobi vault list' to see existing slugs); --name sets the display name. Does not change the configured vault — run 'gobi vault init' or 'gobi vault
-set-primary' afterwards if you want to anchor to it.
+Create a new vault. <slug> must be unique (use 'gobi vault list' to see existing slugs); --name sets the display name. Does not change the configured vault — run 'gobi vault init' afterwards if you
+want to anchor to it.
 
 Options:
   --name <name>  Display name for the new vault
@@ -73,17 +72,6 @@ Options:
   -h, --help  display help for command
 ```
 
-## set-primary
-
-```
-Usage: gobi vault set-primary [options] <slug>
-
-Mark a vault as your primary. Unsets primary on the other vaults you own. Slug must be passed explicitly.
-
-Options:
-  -h, --help  display help for command
-```
-
 ## list
 
 ```