@gobi-ai/cli 0.9.13 → 1.1.0

package/dist/main.js

@@ -5,7 +5,8 @@ import { ApiError, GobiError } from "./errors.js";
 import { registerAuthCommand } from "./commands/auth.js";
 import { registerInitCommand, printContext } from "./commands/init.js";
 import { registerSpaceCommand } from "./commands/space.js";
-import { registerBrainCommand } from "./commands/brain.js";
+import { registerGlobalCommand } from "./commands/global.js";
+import { registerVaultCommand } from "./commands/vault.js";
 import { registerSessionsCommand } from "./commands/sessions.js";
 import { registerSenseCommand } from "./commands/sense.js";
 import { registerSyncCommand } from "./commands/sync.js";
@@ -32,7 +33,8 @@ export async function cli() {
     registerAuthCommand(program);
     registerInitCommand(program);
     registerSpaceCommand(program);
-    registerBrainCommand(program);
+    registerGlobalCommand(program);
+    registerVaultCommand(program);
     registerSessionsCommand(program);
     registerSenseCommand(program);
     registerSyncCommand(program);

package/package.json

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

package/skills/gobi-core/SKILL.md

@@ -38,9 +38,8 @@ brew tap gobi-ai/tap && brew install gobi
 
 ## Key Concepts
 
-- **Space**: A shared space for a group or community. A logged-in user can be a member of one or more spaces. A space contains threads, sessions, brain updates, and connected vaults.
-- **Vault**: A filetree storage of information and knowledge. A local directory becomes a vault when it contains `.gobi/settings.yaml` with a vault slug and a space slug. Each vault is identified by a slug (e.g. `brave-path-zr962w`).
-- **Brain**: Another name for a vault when referring to its AI-searchable knowledge. You can search brains, ask them questions, and publish a `BRAIN.md` document to configure your vault's brain.
+- **Space**: A shared space for a group or community. A logged-in user can be a member of one or more spaces. A space contains threads, sessions, and connected vaults.
+- **Vault**: A personal knowledge container — a filetree storage of information and knowledge that can also be searched and asked questions like a knowledge base. A local directory becomes a vault when it contains `.gobi/settings.yaml` with a vault slug and a space slug. Each vault is identified by a slug (e.g. `brave-path-zr962w`). Publish a `PUBLISH.md` document at the vault root to configure the vault's public profile and AI agent.
 
 ## First-Time Setup
 
@@ -56,7 +55,7 @@ This is an **interactive** command that:
 1. Logs in automatically if not already authenticated (opens a browser URL for Google OAuth)
 2. Prompts the user to select an existing vault or create a new one
 3. Writes `.gobi/settings.yaml` in the current directory with the chosen vault slug
-4. Creates a `BRAIN.md` file if one doesn't exist
+4. Creates a `PUBLISH.md` file if one doesn't exist
 
 ### Step 2: Select a Space
 
@@ -128,7 +127,7 @@ JSON responses have the shape `{ "success": true, "data": ... }` on success or `
 |------|-------------|
 | `~/.gobi/credentials.json` | Stored authentication tokens (auto-managed) |
 | `.gobi/settings.yaml` | Per-project vault and space configuration |
-| `BRAIN.md` | Brain document with YAML frontmatter, published via `gobi brain publish` |
+| `PUBLISH.md` | Vault profile document with YAML frontmatter, published via `gobi vault publish` |
 
 ## Environment Variables
 

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

@@ -3,7 +3,7 @@
 ```
 Usage: gobi space [options] [command]
 
-Space commands (threads, replies).
+Space commands. A Space is a shared room of members where they post threads and replies, organized by topics.
 
 Options:
   --space-slug <slug>                       Space slug (overrides .gobi/settings.yaml)
@@ -11,9 +11,12 @@ Options:
 
 Commands:
   list                                      List spaces you are a member of.
+  get [spaceSlug]                           Get details for a space. Pass a slug or omit to use the current space (from .gobi/settings.yaml or --space-slug).
   warp [spaceSlug]                          Select the active space. Pass a slug to warp directly, or omit for interactive selection.
   list-topics [options]                     List topics in a space, ordered by most recent content linkage.
   list-topic-threads [options] <topicSlug>  List threads tagged with a topic in a space (cursor-paginated).
+  messages [options]                        List the unified message feed (threads and replies, newest first) in a space.
+  ancestors <threadId>                      Show the ancestor lineage of a thread or reply (root → immediate parent).
   get-thread [options] <threadId>           Get a thread and its replies (paginated).
   list-threads [options]                    List threads in a space (paginated).
   create-thread [options]                   Create a thread in a space.

package/skills/gobi-homepage/SKILL.md

@@ -8,7 +8,7 @@ description: >-
 
 # Gobi Homepage Developer Guide
 
-A **Gobi Homepage** is a custom HTML page hosted on a vault's webdrive and served as its public homepage at `https://gobispace.com/@{vaultSlug}`. Gobi injects a `window.gobi` bridge before any scripts run, giving the homepage access to vault data, files, brain updates, and chat.
+A **Gobi Homepage** is a custom HTML page hosted on a vault's webdrive and served as its public homepage at `https://gobispace.com/@{vaultSlug}`. Gobi injects a `window.gobi` bridge before any scripts run, giving the homepage access to vault data, files, and chat.
 
 > **Sandbox:** The homepage runs in a sandboxed iframe with `origin: null`. Direct `fetch()` / `XMLHttpRequest` calls are blocked by CORS. All data access must go through `window.gobi.*`.
 
@@ -20,7 +20,7 @@ A **Gobi Homepage** is a custom HTML page hosted on a vault's webdrive and serve
    ```bash
    gobi sync
    ```
-2. Set `homepage` in BRAIN.md (homepage property):
+2. Set `homepage` in PUBLISH.md (homepage property):
    - `homepage: "[[app/home.html]]"` — Gobi sidebars visible alongside the homepage
    - `homepage: "[[app/home.html?nav=false]]"` — full-screen, no Gobi chrome
 
@@ -67,31 +67,6 @@ function getFileUrl(path) {
 }
 ```
 
-### Brain Updates
-
-```js
-const { data: updates, pagination } = await gobi.listBrainUpdates({ limit: 10, cursor: null });
-// updates[i] → {
-//   id: 42,
-//   title: 'New insights',
-//   content: '## ...',   // markdown — MAY contain ![[file|width]] wiki image embeds
-//   topics: [{ id: 3, name: 'AI', slug: 'ai' }],
-//   createdAt: '2025-03-01T12:00:00Z'
-// }
-// pagination → { hasMore: true, nextCursor: 'abc...' }
-
-// ⚠️ Always call resolveWikiImages() on content before rendering — see Rendering Markdown below.
-for (const u of updates) {
-  el.innerHTML += marked.parse(resolveWikiImages(u.content));
-}
-
-// Pagination — load the next page using the cursor
-if (pagination.hasMore) {
-  const { data: moreUpdates, pagination: nextPage } =
-    await gobi.listBrainUpdates({ limit: 10, cursor: pagination.nextCursor });
-}
-```
-
 ### Chat (login required)
 
 `getSessions`, `loadMessages`, and `sendMessage` require the visitor to be logged in. `getSessions` returns an empty array when not logged in — **but also when logged in with no prior sessions**. Don't use it as a definitive auth check.
@@ -119,7 +94,7 @@ const { messages, hasMore, nextCursor } = await gobi.loadMessages('sess_abc', {
 //   sendMessage(sessionId, text, options, onDelta)  → Promise<{ content }>
 //
 // options.context tells the AI what the user is looking at:
-//   { brainUpdateId?: number, brainUpdateTitle?: string, filePath?: string }
+//   { filePath?: string }
 
 let reply = '';
 await gobi.sendMessage(sessionId, 'Hello', (delta) => {
@@ -128,10 +103,6 @@ await gobi.sendMessage(sessionId, 'Hello', (delta) => {
 });
 
 // With context
-await gobi.sendMessage(sessionId, 'Tell me more', {
-  context: { brainUpdateId: 42, brainUpdateTitle: 'New insights' }
-}, (delta) => { reply += delta; renderReply(reply); });
-
 await gobi.sendMessage(sessionId, 'Explain this', {
   context: { filePath: 'notes/research.md' }
 }, (delta) => { reply += delta; renderReply(reply); });
@@ -144,7 +115,7 @@ sessionId = crypto.randomUUID();
 
 ## Rendering Markdown
 
-Brain update `content` and any markdown read via `readFile` may contain Obsidian-style wiki embeds (`![[path|width]]`). Resolve them before passing to a renderer.
+Markdown read via `readFile` may contain Obsidian-style wiki embeds (`![[path|width]]`). Resolve them before passing to a renderer.
 
 The examples below use [marked](https://cdn.jsdelivr.net/npm/marked/marked.min.js) — include it in your `<head>`:
 
@@ -162,7 +133,7 @@ function resolveWikiImages(md) {
   });
 }
 
-const html = marked.parse(resolveWikiImages(update.content));
+const html = marked.parse(resolveWikiImages(text));
 ```
 
 **Open links in a new tab.** The homepage runs in a sandboxed iframe — clicking a rendered link replaces the iframe with the external page. Override the renderer so every `<a>` opens in a new tab:
@@ -175,7 +146,7 @@ renderer.link = (href, title, text) =>
 marked.setOptions({ renderer });
 ```
 
-**Plain-text previews.** For BU list cards, render a truncated preview with `escapeHtml(content.substring(0, 200))` — don't run markdown on a random substring, it produces broken HTML. Use `marked.parse(resolveWikiImages(content))` only for the full expanded view. Same for chat: `marked.parse(content)` for assistant messages, `escapeHtml(content)` for human messages.
+**Plain-text previews.** For preview cards, render a truncated preview with `escapeHtml(content.substring(0, 200))` — don't run markdown on a random substring, it produces broken HTML. Use `marked.parse(resolveWikiImages(content))` only for the full expanded view. Same for chat: `marked.parse(content)` for assistant messages, `escapeHtml(content)` for human messages.
 
 ---
 
@@ -202,58 +173,9 @@ Centralize colors and spacing in CSS custom properties so restyling is a one-lin
 
 Pair with Google Fonts (e.g. Space Grotesk for headings, IBM Plex Mono for meta, Inter for body) via CDN `<link>`.
 
-### Knowledge Graph from BU topics
-
-Brain updates carry a `topics` array. Treat each topic as a node and any two topics co-occurring in the same BU as an edge — you get a force-directed graph of the vault's themes for free. Use [d3](https://cdn.jsdelivr.net/npm/d3@7/dist/d3.min.js).
-
-```js
-// Separate data-building from rendering so the same graph can be drawn at multiple sizes.
-function buildGraphData(updates) {
-  const counts = new Map();     // name → frequency
-  const edges  = new Map();     // "a|b" → weight
-  for (const u of updates) {
-    const names = (u.topics || []).map(t => t.name);
-    for (const n of names) counts.set(n, (counts.get(n) || 0) + 1);
-    for (let i = 0; i < names.length; i++)
-      for (let j = i + 1; j < names.length; j++) {
-        const key = [names[i], names[j]].sort().join('|');
-        edges.set(key, (edges.get(key) || 0) + 1);
-      }
-  }
-  // Top 20 by frequency, then drop orphans (nodes with no surviving edges).
-  const top = [...counts.entries()].sort((a, b) => b[1] - a[1]).slice(0, 20).map(([n]) => n);
-  const keep = new Set(top);
-  const links = [...edges].flatMap(([k, w]) => {
-    const [a, b] = k.split('|');
-    return keep.has(a) && keep.has(b) ? [{ source: a, target: b, weight: w }] : [];
-  });
-  const connected = new Set(links.flatMap(l => [l.source, l.target]));
-  const nodes = top.filter(n => connected.has(n)).map(n => ({ id: n, count: counts.get(n) }));
-  return { nodes, links };
-}
-
-function drawGraph(containerId, w, h, data, opts = {}) {
-  const { nodeRange = [4, 16], fontSize = '9px', distance = 60, charge = -80 } = opts;
-  const max = Math.max(...data.nodes.map(n => n.count), 1);
-  const r = d3.scaleSqrt().domain([1, max]).range(nodeRange);
-  const svg = d3.select('#' + containerId).append('svg').attr('width', w).attr('height', h);
-  // ... standard d3.forceSimulation with link/charge/center, then clamp in tick:
-  //   node.attr('cx', d => d.x = Math.max(20, Math.min(w - 20, d.x)))
-  //   node.attr('cy', d => d.y = Math.max(20, Math.min(h - 20, d.y)))
-  // Node fill: accent with opacity 0.3 + 0.7 * (count/max).
-  // Call d3.drag() on nodes so visitors can rearrange the graph.
-}
-```
-
-Tips:
-- **Enrich the data.** One page of 8 BUs makes a sparse graph. Paginate 3–4 times (cap at ~32 BUs) before building.
-- **Cache the built data** in a module-level variable so the full-screen overlay can reuse it without refetching.
-- **Mini vs full presets.** Pass different `opts` — e.g. mini `{nodeRange:[4,16], fontSize:'9px', distance:60, charge:-80}`, full `{nodeRange:[8,32], fontSize:'12px', distance:120, charge:-200}`.
-- Run a **separate simulation** for the full-scale instance — copy the nodes/links rather than sharing references, otherwise both graphs fight over the same positions.
-
 ### Full-screen overlay
 
-Useful for expanding the K-Graph (or any small component) into a focused view:
+Useful for expanding any small component into a focused view:
 
 ```js
 function openOverlay(renderInto) {
@@ -272,27 +194,12 @@ function openOverlay(renderInto) {
 
 Always restore `body.overflow` on close, and always remove the `keydown` listener.
 
-### Brain update card — preview/full toggle
-
-Show a truncated card that expands in place on click:
-
-```js
-card.onclick = (event) => {
-  // Link click guard — don't toggle when the user clicked a link inside the card.
-  if (event.target.closest('a')) return;
-  card.classList.toggle('expanded');
-  card.querySelector('.body').innerHTML = card.classList.contains('expanded')
-    ? marked.parse(resolveWikiImages(update.content))
-    : escapeHtml(update.content.substring(0, 200));
-};
-```
-
 ### Chat suggestion chips
 
 Empty chat looks dead. Show clickable prompt chips until the first message is sent:
 
 ```js
-const prompts = ['What is this brain about?', 'Summarize the latest update', 'What topics come up most?'];
+const prompts = ['What is this vault about?', 'Summarize the latest notes', 'What topics come up most?'];
 chips.innerHTML = prompts.map(p => `<button class="chip">${escapeHtml(p)}</button>`).join('');
 chips.querySelectorAll('.chip').forEach((btn, i) => {
   btn.onclick = () => { input.value = prompts[i]; chips.remove(); input.focus(); };
@@ -317,7 +224,7 @@ Single breakpoint at `768px` is enough for most homepages:
 
 ```css
 @media (max-width: 768px) {
-  .hero-grid, .updates-grid { grid-template-columns: 1fr; }
+  .hero-grid { grid-template-columns: 1fr; }
   .hero-content { flex-direction: column; }
   .btn { width: 100%; }
 }
@@ -336,9 +243,9 @@ Single breakpoint at `768px` is enough for most homepages:
   <style>
     * { box-sizing: border-box; margin: 0; padding: 0; }
     body { font-family: system-ui, sans-serif; max-width: 720px; margin: 0 auto; padding: 24px; }
-    .update { margin-bottom: 32px; }
-    .update h2 { margin-bottom: 8px; }
-    .update img { border-radius: 8px; }
+    .hero { margin-bottom: 32px; }
+    .hero h1 { margin-bottom: 8px; }
+    .hero p { color: #555; }
     #chat { margin-top: 40px; border-top: 1px solid #ddd; padding-top: 24px; }
     .message { margin-bottom: 12px; padding: 8px 12px; border-radius: 8px; }
     .message[data-role="human"] { background: #e8f0fe; }
@@ -351,7 +258,10 @@ Single breakpoint at `768px` is enough for most homepages:
   </style>
 </head>
 <body>
-  <div id="updates"></div>
+  <div class="hero">
+    <h1 id="title"></h1>
+    <p id="description"></p>
+  </div>
   <div id="chat">
     <div id="messages"></div>
     <div id="chat-input">
@@ -361,7 +271,9 @@ Single breakpoint at `768px` is enough for most homepages:
   </div>
 
   <script>
-    document.title = gobi.vault.title || 'Brain';
+    document.title = gobi.vault.title || 'Vault';
+    document.getElementById('title').textContent = gobi.vault.title || '';
+    document.getElementById('description').textContent = gobi.vault.description || '';
 
     // ── Helpers ──────────────────────────────────────
 
@@ -389,23 +301,6 @@ Single breakpoint at `768px` is enough for most homepages:
         `https://gobispace.com/login?redirect_uri=${encodeURIComponent(window.location.href)}`;
     }
 
-    // ── Brain updates ────────────────────────────────
-
-    async function loadUpdates() {
-      try {
-        const { data: updates } = await gobi.listBrainUpdates({ limit: 5 });
-        const el = document.getElementById('updates');
-        for (const u of updates) {
-          const div = document.createElement('div');
-          div.className = 'update';
-          div.innerHTML = `<h2>${escapeHtml(u.title)}</h2>${marked.parse(resolveWikiImages(u.content))}`;
-          el.appendChild(div);
-        }
-      } catch (err) {
-        console.error('Failed to load brain updates:', err);
-      }
-    }
-
     // ── Chat ─────────────────────────────────────────
 
     let sessionId = null;
@@ -466,7 +361,6 @@ Single breakpoint at `768px` is enough for most homepages:
 
     // ─────────────────────────────────────────────────
 
-    loadUpdates();
     initChat();
   </script>
 </body>

package/skills/gobi-space/SKILL.md

@@ -1,19 +1,20 @@
 ---
 name: gobi-space
 description: >-
-  Gobi space commands for community interaction: list/create/edit/delete
-  threads and replies, browse topics and topic threads, explore what's
-  happening in a space. Use when the user wants to read, write, or manage
-  threads and replies in their Gobi community spaces.
+  Gobi space commands for community interaction: post threads and
+  replies, browse the unified message feed and topic feeds, walk reply
+  lineage, and post to the global (slugless) space. Use when the user
+  wants to read or write threads and replies in their Gobi community
+  spaces. Space and member administration is web-UI only.
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "0.8.0"
+  version: "0.9.13"
 ---
 
 # gobi-space
 
-Gobi space commands for community interaction (v0.8.0).
+Gobi space commands for community interaction (v0.9.13).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 
@@ -40,19 +41,43 @@ For programmatic/agent usage, always pass `--json` as a **global** option (befor
 gobi --json space list-threads
 ```
 
+> Space and member administration (creating spaces, inviting/approving members, joining/leaving) is web-UI only and not available in the CLI.
+
 ## Available Commands
 
+### Space details
+- `gobi space get` — Get details for a space.
+
+### Topics
 - `gobi space list-topics` — List topics in a space, ordered by most recent content linkage.
 - `gobi space list-topic-threads` — List threads tagged with a topic in a space (cursor-paginated).
+
+### Feed & lineage
+- `gobi space messages` — List the unified message feed (threads and replies, newest first).
+- `gobi space ancestors` — Show the ancestor lineage of a thread or reply (root → immediate parent).
+
+### Threads
 - `gobi space get-thread` — Get a thread and its replies (paginated).
 - `gobi space list-threads` — List threads in a space (paginated).
 - `gobi space create-thread` — Create a thread in a space.
 - `gobi space edit-thread` — Edit a thread. You must be the author.
 - `gobi space delete-thread` — Delete a thread. You must be the author.
+
+### Replies
 - `gobi space create-reply` — Create a reply to a thread in a space.
 - `gobi space edit-reply` — Edit a reply. You must be the author.
 - `gobi space delete-reply` — Delete a reply. You must be the author.
 
+### Global thread space
+The global thread space has no slug and is visible across all spaces.
+
+- `gobi global messages` — List the global unified message feed (newest first).
+- `gobi global get-thread` — Get a global thread and its direct replies.
+- `gobi global ancestors` — Show the ancestor lineage of a global thread or reply.
+- `gobi global create-thread` — Create a thread in the global space.
+- `gobi global reply` — Reply to a thread in the global space.
+
 ## Reference Documentation
 
 - [gobi space](references/space.md)
+- [gobi global](references/global.md)

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

@@ -0,0 +1,82 @@
+# gobi global
+
+```
+Usage: gobi global [options] [command]
+
+Global thread commands. Global is the platform-wide thread feed visible to everyone on Gobi.
+
+Options:
+  -h, --help                       display help for command
+
+Commands:
+  messages [options]               List the global unified message feed (threads and replies, newest first).
+  get-thread [options] <threadId>  Get a global thread and its direct replies (paginated).
+  ancestors <threadId>             Show the ancestor lineage of a global thread or reply (root → immediate parent).
+  create-thread [options]          Create a global thread (visible platform-wide).
+  reply [options] <threadId>       Reply to a global thread.
+  help [command]                   display help for command
+```
+
+## messages
+
+```
+Usage: gobi global messages [options]
+
+List the global unified message feed (threads and replies, newest first).
+
+Options:
+  --limit <number>   Items per page (default: "20")
+  --cursor <string>  Pagination cursor from previous response
+  -h, --help         display help for command
+```
+
+## get-thread
+
+```
+Usage: gobi global get-thread [options] <threadId>
+
+Get a global thread and its direct replies (paginated).
+
+Options:
+  --limit <number>   Replies per page (default: "20")
+  --cursor <string>  Pagination cursor from previous response
+  -h, --help         display help for command
+```
+
+## ancestors
+
+```
+Usage: gobi global ancestors [options] <threadId>
+
+Show the ancestor lineage of a global thread or reply (root → immediate parent).
+
+Options:
+  -h, --help  display help for command
+```
+
+## create-thread
+
+```
+Usage: gobi global create-thread [options]
+
+Create a global thread (visible platform-wide).
+
+Options:
+  --title <title>         Title of the thread
+  --content <content>     Thread content (markdown supported, use "-" for stdin)
+  --rich-text <richText>  Rich-text JSON array (mutually exclusive with --content)
+  -h, --help              display help for command
+```
+
+## reply
+
+```
+Usage: gobi global reply [options] <threadId>
+
+Reply to a global thread.
+
+Options:
+  --content <content>     Reply content (markdown supported, use "-" for stdin)
+  --rich-text <richText>  Rich-text JSON array (mutually exclusive with --content)
+  -h, --help              display help for command
+```

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

@@ -3,7 +3,7 @@
 ```
 Usage: gobi space [options] [command]
 
-Space commands (threads, replies).
+Space commands. A Space is a shared room of members where they post threads and replies, organized by topics.
 
 Options:
   --space-slug <slug>                       Space slug (overrides .gobi/settings.yaml)
@@ -11,9 +11,12 @@ Options:
 
 Commands:
   list                                      List spaces you are a member of.
+  get [spaceSlug]                           Get details for a space. Pass a slug or omit to use the current space (from .gobi/settings.yaml or --space-slug).
   warp [spaceSlug]                          Select the active space. Pass a slug to warp directly, or omit for interactive selection.
   list-topics [options]                     List topics in a space, ordered by most recent content linkage.
   list-topic-threads [options] <topicSlug>  List threads tagged with a topic in a space (cursor-paginated).
+  messages [options]                        List the unified message feed (threads and replies, newest first) in a space.
+  ancestors <threadId>                      Show the ancestor lineage of a thread or reply (root → immediate parent).
   get-thread [options] <threadId>           Get a thread and its replies (paginated).
   list-threads [options]                    List threads in a space (paginated).
   create-thread [options]                   Create a thread in a space.
@@ -25,6 +28,17 @@ Commands:
   help [command]                            display help for command
 ```
 
+## get
+
+```
+Usage: gobi space get [options] [spaceSlug]
+
+Get details for a space. Pass a slug or omit to use the current space (from .gobi/settings.yaml or --space-slug).
+
+Options:
+  -h, --help  display help for command
+```
+
 ## list-topics
 
 ```
@@ -50,6 +64,30 @@ Options:
   -h, --help         display help for command
 ```
 
+## messages
+
+```
+Usage: gobi space messages [options]
+
+List the unified message feed (threads and replies, newest first) in a space.
+
+Options:
+  --limit <number>   Items per page (default: "20")
+  --cursor <string>  Pagination cursor from previous response
+  -h, --help         display help for command
+```
+
+## ancestors
+
+```
+Usage: gobi space ancestors [options] <threadId>
+
+Show the ancestor lineage of a thread or reply (root → immediate parent).
+
+Options:
+  -h, --help  display help for command
+```
+
 ## get-thread
 
 ```

package/skills/gobi-vault/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: gobi-vault
+description: >-
+  Gobi vault commands for knowledge management: search public vaults by text
+  and semantic similarity, ask vaults questions, and publish/unpublish
+  PUBLISH.md. Use when the user wants to search knowledge, ask a vault, or
+  publish their vault document.
+allowed-tools: Bash(gobi:*)
+metadata:
+  author: gobi-ai
+  version: "1.1.0"
+---
+
+# gobi-vault
+
+Gobi vault commands for knowledge management (v1.1.0).
+
+Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
+
+## Gobi Vault — Knowledge Management
+
+`gobi vault` commands manage your vault: search public vaults, ask them questions, and publish/unpublish your `PUBLISH.md`. Public vaults are accessible at `https://gobispace.com/@{vaultSlug}`.
+
+> **Vault updates have moved to threads.** To post user-level content, use `gobi global create-thread` (platform-wide global) or `gobi space create-thread` (a specific space). See the **gobi-space** skill.
+
+## Important: JSON Mode
+
+For programmatic/agent usage, always pass `--json` as a **global** option (before the subcommand):
+
+```bash
+gobi --json vault search --query "machine learning"
+```
+
+## Available Commands
+
+- `gobi vault search` — Search public vaults by text and semantic similarity.
+- `gobi vault ask` — Ask a vault a question. Creates a targeted session (1:1 conversation).
+- `gobi vault publish` — Upload PUBLISH.md to the vault root on webdrive. Triggers post-processing (vault sync, metadata update, Discord notification).
+- `gobi vault unpublish` — Delete PUBLISH.md from the vault on webdrive.
+
+## 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:
+
+```yaml
+---
+title: My Vault
+tags:
+  - topic1
+  - topic2
+description: A short description of what this vault is about.
+thumbnail: "[[VAULT.png]]"
+homepage: "[[app/home.html?nav=false]]"
+prompt: "[[system-prompt.md]]"
+---
+```
+
+### Fields
+
+- **`title`** (required) — Display name of the vault.
+- **`description`** (required for public listing) — Short description shown on the vault card and public profile. Without both `title` and `description`, the vault won't appear in the public catalog.
+- **`tags`** — Tags for categorization and discovery. Supports YAML block list or inline array format:
+  ```yaml
+  # Block list
+  tags:
+    - ambient ai
+    - wearables
+
+  # Inline array
+  tags: [ambient ai, wearables]
+  ```
+- **`thumbnail`** — Profile image for the vault card. Uses wiki-link syntax pointing to an image file in the vault (e.g. `"[[VAULT.png]]"`).
+- **`homepage`** — Custom HTML page to serve as the vault's public homepage at `gobispace.com/@{vaultSlug}`. Uses wiki-link syntax pointing to an HTML file in the vault. Supports a `nav` query parameter to control Gobi's sidebar navigation:
+  - `"[[app/home.html]]"` — Shows the Gobi sidebar alongside the homepage (default)
+  - `"[[app/home.html?nav=false]]"` — Full-screen, no Gobi sidebar/chrome
+- **`prompt`** — Wiki-link to a custom system prompt file for the vault's AI agent (e.g. `"[[system-prompt.md]]"`).
+
+> For details on building custom HTML homepages and using the `window.gobi` API, see the **gobi-homepage** skill.
+
+## Publishing Workflow
+
+After editing `PUBLISH.md` frontmatter, follow these steps to make your changes live:
+
+1. **Edit `PUBLISH.md`** in the vault root with the desired frontmatter fields.
+2. **Sync referenced files** — if the homepage HTML, thumbnail image, or prompt file is new or updated, upload them first:
+   ```bash
+   gobi sync
+   ```
+3. **Publish the vault**:
+   ```bash
+   gobi vault publish
+   ```
+   This uploads `PUBLISH.md` to webdrive, triggers post-processing that extracts metadata (title, description, tags, thumbnail, homepage path), updates the vault's public profile, and sends a Discord notification.
+4. The vault is now live at `https://gobispace.com/@{vaultSlug}`.
+
+> **Important:** Any time you change `PUBLISH.md` frontmatter (e.g. adding or updating `homepage`), you must re-run `gobi vault publish` for the changes to take effect.
+
+## Reference Documentation
+
+- [gobi vault](references/vault.md)