@gobi-ai/cli 2.0.2 → 2.0.4

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.2",
+  "version": "2.0.4",
   "plugins": [
     {
       "name": "gobi",
       "description": "Manage the Gobi collaborative knowledge platform from the command line. Publish vault profiles, create posts and replies, manage saved notes and posts, manage sessions, generate images and videos.",
-      "version": "2.0.2",
+      "version": "2.0.4",
       "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.2",
+  "version": "2.0.4",
   "author": {
     "name": "gobi-ai"
   },

package/dist/commands/init.js

@@ -96,9 +96,13 @@ export async function selectSpace() {
     return { slug: selected.slug, name: selected.name };
 }
 async function selectExistingVault() {
-    const resp = (await apiGet("/vault"));
-    const vaults = (Array.isArray(resp) ? resp : resp.data || resp);
-    if (!vaults || vaults.length === 0) {
+    const resp = (await apiGet("/vaults"));
+    const vaults = (Array.isArray(resp)
+        ? resp
+        : Array.isArray(resp?.data)
+            ? resp.data
+            : []);
+    if (vaults.length === 0) {
         console.log("You don't have any vaults yet. Let's create one.");
         return createNewVault();
     }

package/package.json

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

package/skills/gobi-core/SKILL.md

@@ -117,6 +117,14 @@ JSON responses have the shape `{ "success": true, "data": ... }` on success or `
 
 > File sync (`gobi vault sync`) lives in the **gobi-vault** skill.
 
+## Confirm before mutating
+
+`gobi session reply` posts a human-attributed message into a chat session — the message becomes part of the user's permanent chat history and triggers the agent to respond. Before running it, confirm with the user — show the exact session id and the message text. This applies even when running autonomously.
+
+`auth login` / `auth logout` and `init` are explicit user-driven commands; they prompt the user themselves and don't need an extra confirmation layer. `update` upgrades the CLI binary — fine to run without extra confirmation.
+
+Read-only commands (`auth status`, `session list`, `session get`, `space list`) run without confirmation.
+
 ## Reference Documentation
 
 - [gobi auth](references/auth.md)

package/skills/gobi-draft/SKILL.md

@@ -85,6 +85,15 @@ When the user picks an action via `gobi draft action <id> <index>`, the response
   - `gobi draft action` — Take one of the draft's suggested actions by 0-based index. Posts the synthesized message into the originating session.
   - `gobi draft revise` — Bump the draft to a new revision with a comment, optionally replacing title / content / actions.
 
+## Confirm before mutating
+
+Drafts are agent-authored proposals — `add` and `revise` are the agent's normal authoring path and run without extra confirmation. Two commands flip that:
+
+- `draft action <id> <index>` — picking an action is **a user decision**. Marks the draft `actioned` (terminal — the agent can't take it back) and posts the action's `message` into the originating session. Don't pick on the user's behalf; only run this when the user has explicitly told you which action to take.
+- `draft delete <id>` — irreversible. Confirm the target id with the user before running.
+
+`draft prioritize` is low-stakes (just reorders the prompt feed) — fine to run when the user asks.
+
 ## Reference Documentation
 
 - [gobi draft](references/draft.md)

package/skills/gobi-media/SKILL.md

@@ -171,6 +171,17 @@ Do NOT use markdown image/link syntax `![](...)` or `gobi://` URLs. Always use `
 - `gobi media image-download` — Download a generated image.
 - `gobi media image-status` — Check image generation job status.
 
+## Confirm before mutating
+
+Media generation jobs consume credits (real-world billable cost) and produce assets attached to the user's account. Videos and avatar work can take minutes per job. Before running any generation/upload command, confirm with the user — show the exact command and the prompt / script / source files / aspect ratio / duration. This applies even when running autonomously.
+
+- `image-generate`, `image-edit`, `image-inpaint` — quick but billable per job.
+- `video-create`, `cinematic-create` — slower and more expensive; confirm script, avatar/voice ids, and aspect ratio before submitting.
+- `avatar-design`, `avatar-confirm`, `avatar-from-selfie` — produce assets the user will see in their avatar list. Confirm the photo/prompt and that the user wants the variant locked in (`avatar-confirm` is the commit step).
+- `upload` — adds to the user's media. Low-stakes but still a write; mention the file before uploading.
+
+Read-only commands (`avatars`, `voices`, `image-status`, `video-status`, `video-list`, `video-get`, `avatar-job-status`) and downloads (`image-download`, `video-download`) run without confirmation.
+
 ## Reference Documentation
 
 - [gobi media](references/media.md)

package/skills/gobi-saved/SKILL.md

@@ -54,6 +54,16 @@ gobi --json saved note list --date 2026-04-27
 - `gobi saved post create --source <id>` — Save a post or reply by id. Records a snapshot in your saved-posts collection.
 - `gobi saved post delete <postId>` — Remove a post from your saved-posts collection.
 
+## Confirm before mutating
+
+Saved items are the user's private collection but they still persist server-side and deletes are irreversible. Before running any write, confirm with the user — show the command and the note content / target id. This applies even when running autonomously.
+
+- `note create`, `note edit` — confirm the content (or content delta on edit).
+- `post create` (snapshotting a feed post) — confirm the source id you're about to bookmark.
+- `note delete`, `post delete` — irreversible. Flag that explicitly and confirm the target id before running.
+
+Read-only commands (`note list`, `note get`, `post list`, `post get`) run without confirmation.
+
 ## Reference Documentation
 
 - [gobi saved](references/saved.md)

package/skills/gobi-space/SKILL.md

@@ -94,6 +94,16 @@ gobi --json space list-posts
 - `gobi global edit-reply <replyId>` — Edit a reply you authored.
 - `gobi global delete-reply <replyId>` — Delete a reply you authored.
 
+## Confirm before mutating
+
+Posts and replies are publicly visible — in a community space (`gobi space …`) or in the global feed (`gobi global …`). 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` / `--auto-attachments` is set. 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.
+- `delete-post` / `delete-reply` — irreversible. Flag that explicitly and confirm the target id before running.
+
+Read-only commands (`list-posts`, `get-post`, `feed`, `list-topics`, `list-topic-posts`, `get`) run without confirmation.
+
 ## Reference Documentation
 
 - [gobi space](references/space.md)

package/skills/gobi-vault/SKILL.md

@@ -34,6 +34,14 @@ gobi --json vault publish
 - `gobi vault unpublish` — Delete `PUBLISH.md` from the vault on webdrive.
 - `gobi vault sync` — Sync local vault files with Gobi Webdrive. Supports `--upload-only`, `--download-only`, `--conflict <ask|server|client|skip>`, `--dry-run`, `--full`, `--path <p>`, `--plan-file`, `--execute`.
 
+## Confirm before mutating
+
+Every command in this skill writes external state — webdrive files, the public vault profile, and a Discord notification on `publish`. Before running any of them, confirm with the user — show the exact command and the key changes (which `PUBLISH.md` fields, which paths will sync, which conflict policy). This applies even when running autonomously.
+
+- `vault publish` — public profile change + Discord ping. Always confirm.
+- `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.
+
 ## PUBLISH.md Frontmatter Reference
 
 `PUBLISH.md` is the metadata file at the root of every vault. Its YAML frontmatter controls the vault's public profile, homepage, and AI agent behavior. Example: