@gobi-ai/cli 2.0.24 → 2.0.25

package/dist/commands/draft.js

@@ -1,230 +0,0 @@
-import { apiDelete, apiGet, apiPatch, apiPost } from "../client.js";
-import { isJsonMode, jsonOut, readStdin, unwrapResp } from "./utils.js";
-function readContent(value) {
-    if (value === "-")
-        return readStdin();
-    return value;
-}
-function snippet(content, max = 80) {
-    const single = content.replace(/\s+/g, " ");
-    return single.length > max ? `${single.slice(0, max)}…` : single;
-}
-function parseActionFlags(values) {
-    if (!values)
-        return [];
-    return values
-        .map((v) => v.trim())
-        .filter(Boolean)
-        .slice(0, 3)
-        .map((entry) => {
-        const sep = entry.indexOf("::");
-        if (sep === -1)
-            return { label: entry };
-        const label = entry.slice(0, sep).trim();
-        const message = entry.slice(sep + 2).trim();
-        return message ? { label, message } : { label };
-    })
-        .filter((a) => a.label.length > 0);
-}
-function formatDraftLine(d) {
-    const status = d.status === "pending" ? "·" : "✓";
-    const actionCount = d.actions.length;
-    return `- [${status}] p${d.priority} rev${d.revision} ${d.draftId.slice(0, 8)}  ${snippet(d.title)} (${actionCount} action${actionCount === 1 ? "" : "s"})`;
-}
-export function registerDraftCommand(program) {
-    // The draft command surface is designed for agent use: every subcommand
-    // accepts `--json` (set globally) and returns the same envelope shape, and
-    // the agent-authoring flow funnels through `add` + `revise` while user-
-    // facing decisions go through `action` and `revise` (with --comment).
-    const draft = program
-        .command("draft")
-        .description("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.");
-    // ── List ──
-    draft
-        .command("list")
-        .description("List drafts (priority ASC, then newest first).")
-        .option("--limit <number>", "Items per page", "20")
-        .action(async (opts) => {
-        const params = { limit: parseInt(opts.limit, 10) };
-        const resp = (await apiGet("/app/drafts", params));
-        const items = (resp.data || []);
-        if (isJsonMode(draft)) {
-            jsonOut(items);
-            return;
-        }
-        if (!items.length) {
-            console.log("No drafts.");
-            return;
-        }
-        console.log(`Drafts (${items.length}):`);
-        for (const d of items)
-            console.log(formatDraftLine(d));
-    });
-    // ── Get ──
-    draft
-        .command("get <draftId>")
-        .description("Get one draft with its history and suggested actions.")
-        .action(async (draftId) => {
-        const resp = (await apiGet(`/app/drafts/${draftId}`));
-        const d = unwrapResp(resp);
-        if (isJsonMode(draft)) {
-            jsonOut(d);
-            return;
-        }
-        console.log(`Draft ${d.draftId}`);
-        console.log(`  title:    ${d.title}`);
-        console.log(`  status:   ${d.status}`);
-        console.log(`  priority: ${d.priority}`);
-        console.log(`  revision: ${d.revision}`);
-        console.log(`  session:  ${d.sessionId}`);
-        if (d.vaultSlug)
-            console.log(`  vault:    ${d.vaultSlug}`);
-        console.log(`  created:  ${d.createdAt}`);
-        console.log("");
-        console.log("Content:");
-        console.log(d.content);
-        if (d.actions.length) {
-            console.log("");
-            console.log("Suggested actions:");
-            d.actions.forEach((a, i) => {
-                console.log(`  [${i}] ${a.label}`);
-                if (a.message)
-                    console.log(`      → ${a.message}`);
-            });
-        }
-        if (d.history.length) {
-            console.log("");
-            console.log("History:");
-            for (const h of d.history) {
-                console.log(`  ${h.createdAt}  rev${h.revision}  ${h.type}`);
-                if (h.type === "created" || h.type === "revised") {
-                    if (h.title !== undefined)
-                        console.log(`    title:   ${h.title}`);
-                    if (h.content !== undefined) {
-                        console.log(`    content: ${snippet(h.content, 200)}`);
-                    }
-                    if (h.actions !== undefined && h.actions.length) {
-                        console.log(`    actions: ${h.actions
-                            .map((a) => (a.message ? `${a.label} :: ${a.message}` : a.label))
-                            .join(" | ")}`);
-                    }
-                    if (h.comment !== undefined)
-                        console.log(`    comment: ${h.comment}`);
-                }
-                else if (h.type === "prioritized" && h.priority !== undefined) {
-                    console.log(`    priority=${h.priority}`);
-                }
-                else if (h.type === "actioned") {
-                    console.log(`    action[${h.actionIndex}]=${h.actionLabel}`);
-                }
-            }
-        }
-    });
-    // ── Add ──
-    draft
-        .command("add <title> <content>")
-        .description("Add a draft. Pass '-' for content to read from stdin. Pass --action up to 3 times to attach AI-suggested actions. Session id is optional: the Gobi agent runtime exports GOBI_SESSION_ID automatically and `--session` takes precedence; if neither is set, the server mints a new chat session anchored to your primary vault and seeds it with the draft so clicking an action later has somewhere to land.")
-        .option("--session <sessionId>", "Originating chat session UUID. Falls back to $GOBI_SESSION_ID; if unset, the server creates a new session.")
-        .option("--priority <number>", "Priority (lower = higher), default 100")
-        .option("--action <label[::message]>", "Suggested action (repeatable, max 3). `label` is the button text; an optional `::message` suffix is what the user is taken to be saying to the agent on click. Without the suffix, the message falls back to the label.", (value, prev = []) => [...prev, value], [])
-        .option("--vault-slug <vaultSlug>", "Anchor vault for this draft. When set, clients render the draft against this vault, and a sessionId-less create bootstraps the new chat session here instead of your primary vault.")
-        .action(async (title, content, opts) => {
-        const sessionId = opts.session || process.env.GOBI_SESSION_ID;
-        const body = {
-            title,
-            content: readContent(content),
-        };
-        if (sessionId)
-            body.sessionId = sessionId;
-        if (opts.priority)
-            body.priority = parseInt(opts.priority, 10);
-        const actions = parseActionFlags(opts.action);
-        if (actions.length)
-            body.actions = actions;
-        if (opts.vaultSlug)
-            body.vaultSlug = opts.vaultSlug;
-        const resp = (await apiPost("/app/drafts", body));
-        const d = unwrapResp(resp);
-        if (isJsonMode(draft)) {
-            jsonOut(d);
-            return;
-        }
-        console.log(`Created ${d.draftId} (priority ${d.priority}, ${d.actions.length} action${d.actions.length === 1 ? "" : "s"}).`);
-    });
-    // ── Delete ──
-    draft
-        .command("delete <draftId>")
-        .description("Delete a draft.")
-        .action(async (draftId) => {
-        await apiDelete(`/app/drafts/${draftId}`);
-        if (isJsonMode(draft)) {
-            jsonOut({ id: draftId });
-            return;
-        }
-        console.log(`Deleted ${draftId}.`);
-    });
-    // ── Prioritize ──
-    draft
-        .command("prioritize <draftId> <priority>")
-        .description("Set priority (lower = higher). Top 5 feed the system prompt.")
-        .action(async (draftId, priority) => {
-        const resp = (await apiPatch(`/app/drafts/${draftId}/priority`, {
-            priority: parseInt(priority, 10),
-        }));
-        const d = unwrapResp(resp);
-        if (isJsonMode(draft)) {
-            jsonOut(d);
-            return;
-        }
-        console.log(`Set ${d.draftId} priority to ${d.priority}.`);
-    });
-    // ── Action ──
-    draft
-        .command("action <draftId> <actionIndex>")
-        .description("Take one of the draft's suggested actions by 0-based index. Marks the draft 'actioned' and the client posts the synthesized message into the originating session.")
-        .action(async (draftId, actionIndex) => {
-        const idx = parseInt(actionIndex, 10);
-        if (Number.isNaN(idx) || idx < 0 || idx > 2) {
-            throw new Error("actionIndex must be 0, 1, or 2.");
-        }
-        const resp = (await apiPost(`/app/drafts/${draftId}/action`, {
-            actionIndex: idx,
-        }));
-        const d = unwrapResp(resp);
-        if (isJsonMode(draft)) {
-            jsonOut(d);
-            return;
-        }
-        const label = d.actions[idx]?.label ?? `action ${idx}`;
-        console.log(`Took action "${label}" on ${d.draftId}.`);
-    });
-    // ── Revise ──
-    draft
-        .command("revise <draftId> <comment>")
-        .description("Bump the draft to a new revision. Comment is required. Pass --title, --content, and/or --action to update the draft in the same call (--action repeatable, max 3, replaces all). Pass '-' for any of comment/title/content to read from stdin.")
-        .option("--title <title>", "Replacement title")
-        .option("--content <content>", "Replacement content; pass '-' to read from stdin")
-        .option("--action <label[::message]>", "Replacement suggested action (repeatable, max 3). Same `label[::message]` syntax as `draft add`. When passed, replaces the entire actions array.", (value, prev = []) => [...prev, value], [])
-        .option("--vault-slug <vaultSlug>", "Replacement anchor vault. When set, switches the draft's anchor vault. Carries forward when omitted.")
-        .action(async (draftId, comment, opts) => {
-        const body = {
-            comment: readContent(comment),
-        };
-        if (opts.title !== undefined)
-            body.title = opts.title;
-        if (opts.content !== undefined)
-            body.content = readContent(opts.content);
-        if (opts.action && opts.action.length > 0) {
-            body.actions = parseActionFlags(opts.action);
-        }
-        if (opts.vaultSlug !== undefined)
-            body.vaultSlug = opts.vaultSlug;
-        const resp = (await apiPost(`/app/drafts/${draftId}/revise`, body));
-        const d = unwrapResp(resp);
-        if (isJsonMode(draft)) {
-            jsonOut(d);
-            return;
-        }
-        console.log(`Revised ${d.draftId} → rev${d.revision}.`);
-    });
-}

package/skills/gobi-draft/SKILL.md

@@ -1,113 +0,0 @@
----
-name: gobi-draft
-description: >-
-  Gobi draft commands for managing agent-authored drafts: list, get, add,
-  delete, prioritize, action, revise. Each draft carries 0–3 AI-suggested
-  actions; the user picks one with `draft action`. The top-priority pending
-  drafts feed into the agent's system prompt every turn. Use when the user
-  wants to review, organize, or respond to drafts — or when an agent (using
-  gobi-cli as its tool layer) wants to record a draft it just composed.
-allowed-tools: Bash(gobi:*)
-metadata:
-  author: gobi-ai
-  version: "2.0.24"
----
-
-# gobi-draft
-
-Gobi draft commands for managing agent-authored drafts (v2.0.24).
-
-Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
-
-## What is a draft?
-
-A draft is a unit of standing guidance authored by an agent (in-process during chat, or via `gobi draft add` when the agent uses gobi-cli as its tool layer). Each draft has:
-
-- **title** — short headline (1–200 chars)
-- **content** — the draft text (markdown, 1–8000 chars)
-- **actions** — 0–3 AI-suggested actions. Each action is `{ label, message? }`:
-  - `label` — short button text (1–80 chars) the user sees, e.g. `"Apply"`, `"Skip"`.
-  - `message` — optional (≤2000 chars). What the user is taken to be saying to the agent when they click that button. Falls back to `label` when omitted. Use this whenever the click should send something more specific than the button text — e.g. label `"Punch it up"`, message `"Tighten the opening paragraph and shorten the CTA"`.
-- **sessionId** — the chat session the draft is anchored to. Optional on create: when omitted, the server mints a fresh session anchored to the draft's vault (or the user's primary if `vaultSlug` is unset) and seeds it with a tool-call entry representing the draft, so clicking an action later has somewhere to land.
-- **vaultSlug** — optional anchor vault slug. When set, clients render the draft against this vault's identity and the bootstrap session (created when no `sessionId` is passed) is anchored here instead of the user's primary. Pass `--vault-slug <slug>` on `add` or `revise`. Caller must own the vault.
-- **priority** — lower number = higher priority; default `100`
-- **status** — `pending` until the user picks an action, then `actioned`
-- **revision** — bumped each time the draft is revised
-- **history** — append-only log of `created`, `revised`, `prioritized`, and `actioned` events
-
-The top 5 pending drafts (lowest priority first) are injected into the agent's system prompt every turn — that's how drafts turn into standing instructions.
-
-When invoked from inside the Gobi agent runtime, `GOBI_SESSION_ID` is exported and `gobi draft add` picks it up automatically. Outside that runtime (e.g. local Claude Code, ad-hoc shells), you can either pass `--session <uuid>` to anchor to an existing chat session, or omit it entirely — the server will mint a new session and seed it with the draft so the action click lands somewhere coherent.
-
-## Lifecycle
-
-A draft is **authored** by an agent (`gobi draft add` with up to three `--action` flags). The user can then:
-
-- **Take an action**: `gobi draft action <id> <index>` — flips status to `actioned`, the client posts the synthesized message ("Take action 'X' on draft Y") into the originating chat session.
-- **Ask to revise**: `gobi draft revise <id> <comment>` — bumps revision and records the comment. The agent's next turn should produce a fresh `gobi draft revise --title --content --action ...` (or a new `add`) addressing the comment.
-- **Re-prioritize / delete** as bookkeeping.
-
-Only pending drafts can be revised. Picking an action is terminal; the agent can author a fresh draft if the user later changes their mind.
-
-## Important: JSON Mode
-
-For programmatic/agent usage, always pass `--json` as a **global** option (before the subcommand):
-
-```bash
-gobi --json draft list --limit 20
-gobi --json draft add "Concise titles" "Prefer concise titles for personal posts." \
-  --action "Apply::Yes, rewrite my last three posts with concise titles." \
-  --action "Skip" \
-  --priority 50
-gobi --json draft action <draftId> 0
-```
-
-JSON mode wraps the response as `{"success": true, "data": <draft>}` (or `{"success": false, "error": "..."}`).
-
-## Action `label::message` syntax
-
-The `--action` flag (on both `add` and `revise`) accepts either form:
-
-- `--action "Apply"` — label only; message falls back to `"Apply"` on click.
-- `--action "Apply::Yes, rewrite my last three posts with concise titles."` — label is `Apply`, the click sends the full sentence as the user's next turn into the originating chat session.
-
-The literal `::` separator splits the two. Use `message` whenever the click should send something more specific than the button text — that's the whole point of the field. Keep `label` punchy (a few words); put the actual instruction in `message`.
-
-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>" / "Save to Personal Space" and your next turn creates the post, pass `--draft-id <draftId>` to the relevant create command. `--draft-id` is the **sole** source of `title` and `content` — the CLI fetches the draft and uses its title and content directly, so `--title` / `--content` / `--rich-text` are not allowed alongside it on `create-post`. If you want to change the wording, `gobi draft revise` first, then create.
-
-- `gobi space create-post --draft-id` / `gobi global create-post --draft-id` / `gobi personal create-post --draft-id` — uses draft's title and content as the post's `title` and `content`. The draft's `vaultSlug` (when set) seeds `--vault-slug` if not given explicitly. `--auto-attachments`, `--space-slug`, and an explicit `--vault-slug` override remain allowed. Records `{ postId, spaceSlug? }` on `draft.metadata` for an "Open post" button.
-
-```bash
-gobi --json global create-post --draft-id <draftId>
-gobi --json space create-post --space-slug <slug> --draft-id <draftId>
-gobi --json personal create-post --draft-id <draftId>
-gobi --json global create-post --draft-id <draftId> --auto-attachments
-```
-
-## 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.
-  - `gobi draft list` — List drafts (priority ASC, then newest first).
-  - `gobi draft get` — Show one draft with its history and suggested actions.
-  - `gobi draft add` — Add a draft. Pass `--action <label[::message]>` up to 3 times to attach AI-suggested actions. Pass `--vault-slug <slug>` to anchor the draft to a specific vault.
-  - `gobi draft delete` — Delete a draft.
-  - `gobi draft prioritize` — Set priority (lower = higher). Top 5 feed the system prompt.
-  - `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 / vault-slug.
-
-## 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-draft/references/draft.md

@@ -1,114 +0,0 @@
-# gobi draft
-
-```
-Usage: gobi draft [options] [command]
-
-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.
-
-Options:
-  -h, --help                            display help for command
-
-Commands:
-  list [options]                        List drafts (priority ASC, then newest first).
-  get <draftId>                         Get one draft with its history and suggested actions.
-  add [options] <title> <content>       Add a draft. Pass '-' for content to read from stdin. Pass --action up to 3 times to attach AI-suggested actions. Session id is optional: the Gobi agent
-                                        runtime exports GOBI_SESSION_ID automatically and `--session` takes precedence; if neither is set, the server mints a new chat session anchored to your primary
-                                        vault and seeds it with the draft so clicking an action later has somewhere to land.
-  delete <draftId>                      Delete a draft.
-  prioritize <draftId> <priority>       Set priority (lower = higher). Top 5 feed the system prompt.
-  action <draftId> <actionIndex>        Take one of the draft's suggested actions by 0-based index. Marks the draft 'actioned' and the client posts the synthesized message into the originating
-                                        session.
-  revise [options] <draftId> <comment>  Bump the draft to a new revision. Comment is required. Pass --title, --content, and/or --action to update the draft in the same call (--action repeatable, max
-                                        3, replaces all). Pass '-' for any of comment/title/content to read from stdin.
-  help [command]                        display help for command
-```
-
-## list
-
-```
-Usage: gobi draft list [options]
-
-List drafts (priority ASC, then newest first).
-
-Options:
-  --limit <number>  Items per page (default: "20")
-  -h, --help        display help for command
-```
-
-## get
-
-```
-Usage: gobi draft get [options] <draftId>
-
-Get one draft with its history and suggested actions.
-
-Options:
-  -h, --help  display help for command
-```
-
-## add
-
-```
-Usage: gobi draft add [options] <title> <content>
-
-Add a draft. Pass '-' for content to read from stdin. Pass --action up to 3 times to attach AI-suggested actions. Session id is optional: the Gobi agent runtime exports GOBI_SESSION_ID automatically
-and `--session` takes precedence; if neither is set, the server mints a new chat session anchored to your primary vault and seeds it with the draft so clicking an action later has somewhere to land.
-
-Options:
-  --session <sessionId>        Originating chat session UUID. Falls back to $GOBI_SESSION_ID; if unset, the server creates a new session.
-  --priority <number>          Priority (lower = higher), default 100
-  --action <label[::message]>  Suggested action (repeatable, max 3). `label` is the button text; an optional `::message` suffix is what the user is taken to be saying to the agent on click. Without
-                               the suffix, the message falls back to the label. (default: [])
-  --vault-slug <vaultSlug>     Anchor vault for this draft. When set, clients render the draft against this vault, and a sessionId-less create bootstraps the new chat session here instead of your
-                               primary vault.
-  -h, --help                   display help for command
-```
-
-## delete
-
-```
-Usage: gobi draft delete [options] <draftId>
-
-Delete a draft.
-
-Options:
-  -h, --help  display help for command
-```
-
-## prioritize
-
-```
-Usage: gobi draft prioritize [options] <draftId> <priority>
-
-Set priority (lower = higher). Top 5 feed the system prompt.
-
-Options:
-  -h, --help  display help for command
-```
-
-## action
-
-```
-Usage: gobi draft action [options] <draftId> <actionIndex>
-
-Take one of the draft's suggested actions by 0-based index. Marks the draft 'actioned' and the client posts the synthesized message into the originating session.
-
-Options:
-  -h, --help  display help for command
-```
-
-## revise
-
-```
-Usage: gobi draft revise [options] <draftId> <comment>
-
-Bump the draft to a new revision. Comment is required. Pass --title, --content, and/or --action to update the draft in the same call (--action repeatable, max 3, replaces all). Pass '-' for any of
-comment/title/content to read from stdin.
-
-Options:
-  --title <title>              Replacement title
-  --content <content>          Replacement content; pass '-' to read from stdin
-  --action <label[::message]>  Replacement suggested action (repeatable, max 3). Same `label[::message]` syntax as `draft add`. When passed, replaces the entire actions array. (default: [])
-  --vault-slug <vaultSlug>     Replacement anchor vault. When set, switches the draft's anchor vault. Carries forward when omitted.
-  -h, --help                   display help for command
-```