@gobi-ai/cli 2.0.9 → 2.0.11

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

package/commands/post.md

@@ -0,0 +1,80 @@
+---
+name: post
+description: Draft a post from recent conversation history and publish it to the spaces it best fits. Default mode requires approval; pass `bypass` to post without confirmation.
+argument-hint: "[approval|bypass]"
+disable-model-invocation: true
+---
+
+Always use the globally installed `gobi` binary (not via npx or ts-node).
+
+## Argument: permissionMode
+
+`$ARGUMENTS` is the permission mode. Accept exactly:
+
+- `approval` (default if `$ARGUMENTS` is empty or unrecognized) — draft, present, and require user confirmation before posting.
+- `bypass` — draft and post without a confirmation step.
+
+Treat anything else as `approval`. Do not ask the user which mode to use — the argument is the answer.
+
+## Pre-flight check
+
+```bash
+gobi --json auth status
+```
+
+If unauthenticated, stop and ask the user to run `/gobi:login`.
+
+## 1. List spaces and choose targets
+
+```bash
+gobi --json space list
+```
+
+Each entry has `slug`, `name`, `description`, and (sometimes) `rules`. If the list is empty, stop — there's nowhere to post.
+
+Review the recent conversation history and extract content that is:
+
+- **Reusable** — others could apply it to their own work.
+- **Generalizable** — patterns, decisions, constraints, discoveries; not a one-off task log.
+- **Not sensitive** — exclude code snippets, file paths, PII, credentials, internal URLs, proprietary details.
+
+Then match the content against each space's `name`, `description`, and `rules`. Pick the **space(s) the content genuinely fits** — could be one, could be a few. If nothing fits, stop and tell the user no space matched; do **not** force a post into a tangentially related space.
+
+If a space's `rules` constrain format, topic, or tone, follow them — or skip that space.
+
+## 2. Draft the post
+
+For each target space, prepare:
+
+- **Title** — short, descriptive, no leading `#`, does not duplicate the body's first line.
+- **Content** — markdown body (2–5 bullets is usually right). Do not repeat the title inside the content. Tailor per space if their rules differ; otherwise the same draft can go to multiple spaces.
+
+## 3. Approval mode (default)
+
+Show the user, for each target space:
+
+- The space slug and name.
+- The exact `gobi space create-post` command that will run.
+- The resolved title and a preview of the content.
+
+Wait for the user's confirmation. Accept redirects ("only post to X", "rewrite the title", "skip space Y") and re-present before posting. Do not post until the user confirms.
+
+## 4. Bypass mode
+
+Skip the confirmation step. Proceed straight to posting. Still print the target space(s) and the command(s) to the terminal so the action is visible.
+
+## 5. Post
+
+For each chosen space, run:
+
+```bash
+gobi space create-post --space-slug <slug> --title "<title>" --content "<content>"
+```
+
+(`--space-slug` overrides `.gobi/settings.yaml`, so this works without `gobi space warp` first.)
+
+After each post, echo the result with a shareable URL built from the response:
+
+`https://gobispace.com/spaces/<spaceSlug>?postId=<id>`
+
+If a post fails, report the error and continue with the remaining targets — one failure should not block the others.

package/dist/commands/global.js

@@ -183,6 +183,7 @@ export function registerGlobalCommand(program) {
         .option("--rich-text <richText>", "Rich-text JSON array (mutually exclusive with --content)")
         .option("--vault-slug <vaultSlug>", "Attribute the post to this vault (sets authorVaultSlug). Defaults to your primary vault.")
         .option("--auto-attachments", "Upload wiki-linked [[files]] to webdrive before posting (also sets authorVaultSlug to that vault)")
+        .option("--draft-id <draftId>", "Link this post back to the draft it was created from (records postId on draft.metadata so the client can render an 'Open post' button).")
         .action(async (opts) => {
         if (!opts.content && !opts.richText) {
             throw new Error("Provide either --content or --rich-text.");
@@ -220,6 +221,19 @@ export function registerGlobalCommand(program) {
             body.authorVaultSlug = authorVaultSlug;
         const resp = (await apiPost(`/posts`, body));
         const post = unwrapResp(resp);
+        if (opts.draftId && post.id != null) {
+            try {
+                await apiPatch(`/app/drafts/${opts.draftId}/metadata`, {
+                    postId: typeof post.id === "number" ? post.id : Number(post.id),
+                    spaceSlug: null,
+                });
+            }
+            catch (e) {
+                // Don't fail the create if linking fails — the post is live; just
+                // surface a warning so the agent can mention it.
+                console.error(`Warning: failed to link post to draft ${opts.draftId}: ${e.message}`);
+            }
+        }
         if (isJsonMode(global)) {
             jsonOut(post);
             return;
@@ -227,7 +241,8 @@ export function registerGlobalCommand(program) {
         console.log(`Post created!\n` +
             `  ID: ${post.id}\n` +
             (post.title ? `  Title: ${post.title}\n` : "") +
-            `  Created: ${post.createdAt}`);
+            `  Created: ${post.createdAt}` +
+            (opts.draftId ? `\n  Linked to draft: ${opts.draftId}` : ""));
     });
     // ── Edit post ──
     global

package/dist/commands/space.js

@@ -318,6 +318,7 @@ export function registerSpaceCommand(program) {
         .option("--auto-attachments", "Upload wiki-linked [[files]] to webdrive before posting (also attributes the post to that vault)")
         .option("--vault-slug <vaultSlug>", "Attribute the post to this vault (sets authorVaultId). Also used as upload destination for --auto-attachments.")
         .option("--space-slug <spaceSlug>", "Space slug (overrides .gobi/settings.yaml)")
+        .option("--draft-id <draftId>", "Link this post back to the draft it was created from (records postId/spaceSlug on draft.metadata so the client can render an 'Open post' button).")
         .action(async (opts) => {
         if (!opts.content && !opts.richText) {
             throw new Error("Provide either --content or --rich-text.");
@@ -356,6 +357,19 @@ export function registerSpaceCommand(program) {
         const spaceSlug = resolveSpaceSlug(space, opts);
         const resp = (await apiPost(`/spaces/${spaceSlug}/posts`, body));
         const post = unwrapResp(resp);
+        if (opts.draftId && post.id != null) {
+            try {
+                await apiPatch(`/app/drafts/${opts.draftId}/metadata`, {
+                    postId: typeof post.id === "number" ? post.id : Number(post.id),
+                    spaceSlug,
+                });
+            }
+            catch (e) {
+                // Don't fail the create if linking fails — the post is live; just
+                // surface a warning so the agent can mention it.
+                console.error(`Warning: failed to link post to draft ${opts.draftId}: ${e.message}`);
+            }
+        }
         if (isJsonMode(space)) {
             jsonOut(post);
             return;
@@ -363,7 +377,8 @@ export function registerSpaceCommand(program) {
         console.log(`Post created!\n` +
             `  ID: ${post.id}\n` +
             (post.title ? `  Title: ${post.title}\n` : "") +
-            `  Created: ${post.createdAt}`);
+            `  Created: ${post.createdAt}` +
+            (opts.draftId ? `\n  Linked to draft: ${opts.draftId}` : ""));
     });
     space
         .command("edit-post <postId>")

package/package.json

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

package/skills/gobi-draft/SKILL.md

@@ -10,7 +10,7 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.9"
+  version: "2.0.10"
 ---
 
 # gobi-draft
@@ -74,6 +74,15 @@ The literal `::` separator splits the two. Use `message` whenever the click shou
 
 When the user picks an action via `gobi draft action <id> <index>`, the response includes the picked action's `message` (or `label` as fallback) in `data.actions[index]`, which the client then posts into the originating session.
 
+## Linking a created post back to its draft
+
+When the user picks an action like "Post to Global Feed" / "Post to <space>" and your next turn creates the post, pass `--draft-id <draftId>` to `gobi space create-post` or `gobi global create-post`. The CLI records the resulting `postId` (and `spaceSlug` for space posts) on `draft.metadata`, which the client uses to render an "Open post" button on the actioned draft. Without `--draft-id` the post is still created, but the draft and the post stay disconnected in the UI.
+
+```bash
+gobi --json global create-post --title "..." --content "..." --draft-id <draftId>
+gobi --json space create-post --space-slug <slug> --title "..." --content "..." --draft-id <draftId>
+```
+
 ## Available Commands
 
 - `gobi draft` — Drafts authored by your agent during chat. Each carries up to 3 AI-suggested actions. Top-5 pending feed the system prompt; picking an action posts a synthesized message into the originating session.

package/skills/gobi-space/SKILL.md

@@ -10,7 +10,7 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.9"
+  version: "2.0.10"
 ---
 
 # gobi-space
@@ -30,6 +30,7 @@ Anything you can do to a Space Post (reply, edit, delete, attribute to a vault)
 
 - 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`.
+- When the user wants to draft a post from the current session and route it to whichever space(s) it best fits, invoke `/gobi:post` (default approval mode; pass `bypass` to skip confirmation).
 
 ## Authoring posts: title vs. content
 
@@ -131,6 +132,10 @@ gobi --json space list-posts
 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.
+
+### Linking back to a draft
+
+When a `create-post` is the side-effect of an actioned draft (e.g. the user picked "Post to Global Feed" / "Post to <space>"), pass `--draft-id <draftId>` to `gobi space create-post` or `gobi global create-post`. The CLI records `{ postId, spaceSlug? }` on `draft.metadata`, which the client renders as an "Open post" button on the actioned draft. Without `--draft-id` the post is still created, but the draft and post stay disconnected in the UI.
 - `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.
 

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

@@ -77,6 +77,7 @@ Options:
   --rich-text <richText>    Rich-text JSON array (mutually exclusive with --content)
   --vault-slug <vaultSlug>  Attribute the post to this vault (sets authorVaultSlug). Defaults to your primary vault.
   --auto-attachments        Upload wiki-linked [[files]] to webdrive before posting (also sets authorVaultSlug to that vault)
+  --draft-id <draftId>      Link this post back to the draft it was created from (records postId on draft.metadata so the client can render an 'Open post' button).
   -h, --help                display help for command
 ```
 

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

@@ -123,6 +123,7 @@ Options:
   --auto-attachments        Upload wiki-linked [[files]] to webdrive before posting (also attributes the post to that vault)
   --vault-slug <vaultSlug>  Attribute the post to this vault (sets authorVaultId). Also used as upload destination for --auto-attachments.
   --space-slug <spaceSlug>  Space slug (overrides .gobi/settings.yaml)
+  --draft-id <draftId>      Link this post back to the draft it was created from (records postId/spaceSlug on draft.metadata so the client can render an 'Open post' button).
   -h, --help                display help for command
 ```