flyspace-cli 0.1.58 → 0.1.60

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -3,8 +3,8 @@ import { createRequire as __flyspaceCreateRequire } from 'node:module';
3
3
  const require = __flyspaceCreateRequire(import.meta.url);
4
4
  import {
5
5
  startServer
6
- } from "./chunk-TAUF3WGB.js";
7
- import "./chunk-XACRG7BO.js";
6
+ } from "./chunk-SIR6PTDT.js";
7
+ import "./chunk-XYS7SVWC.js";
8
8
  export {
9
9
  startServer
10
10
  };
@@ -8,13 +8,14 @@ import {
8
8
  moveThreadFully,
9
9
  parseThreadRef,
10
10
  resolveThreadOwner,
11
+ shareDoc,
11
12
  threadPath
12
- } from "./chunk-44WHW7NK.js";
13
+ } from "./chunk-PXZUNZ4S.js";
13
14
  import {
14
15
  AGENT_AUTHOR,
15
16
  getSupabaseClient,
16
17
  postToDashboardChannel
17
- } from "./chunk-XACRG7BO.js";
18
+ } from "./chunk-XYS7SVWC.js";
18
19
 
19
20
  // src/mcp/servers/threads.ts
20
21
  import { Server } from "@modelcontextprotocol/sdk/server/index.js";
@@ -205,6 +206,19 @@ var TOOLS = [
205
206
  },
206
207
  required: ["thread_id", "to_channel_id"]
207
208
  }
209
+ },
210
+ {
211
+ name: "share_doc",
212
+ description: 'Publish a channel doc (Markdown or HTML) as a public link and return its URL, the same as "Copy public link" in the Docs pane. Re-sharing the same doc keeps the URL and updates the content.',
213
+ inputSchema: {
214
+ type: "object",
215
+ properties: {
216
+ channel_id: { type: "string", description: "The channel the doc belongs to." },
217
+ path: { type: "string", description: "Doc path relative to the channel folder, e.g. docs/plan.md." },
218
+ slug: { type: "string", description: "Optional custom URL: /share/<slug>." }
219
+ },
220
+ required: ["channel_id", "path"]
221
+ }
208
222
  }
209
223
  ];
210
224
  var PERMISSION_TOOL = {
@@ -333,6 +347,13 @@ async function startThreadsServer() {
333
347
  const text = moved === "unchanged" ? `Thread ${threadId} is already in ${toChannelId}.` : `Moved thread ${threadId} to ${moved.to.name} (${moved.to.id}); carried over ${moved.sessions} agent session(s).` + (moved.cwdChanged ? ` The channels have different working directories: files the thread created stay in ${moved.from?.cwd}.` : "");
334
348
  return { content: [{ type: "text", text }] };
335
349
  }
350
+ if (request.params.name === "share_doc") {
351
+ const channelId = typeof args["channel_id"] === "string" ? args["channel_id"].trim() : "";
352
+ const path = typeof args["path"] === "string" ? args["path"].trim() : "";
353
+ if (!channelId || !path) throw new Error("channel_id and path are required");
354
+ const slug = typeof args["slug"] === "string" && args["slug"].trim() ? args["slug"].trim() : void 0;
355
+ return { content: [{ type: "text", text: await shareDoc(channelId, path, slug) }] };
356
+ }
336
357
  if (request.params.name === PERMISSION_TOOL.name && permission) {
337
358
  const toolName = typeof args["tool_name"] === "string" ? args["tool_name"] : "a tool";
338
359
  const input = args["input"] && typeof args["input"] === "object" ? args["input"] : {};
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "flyspace-cli",
3
- "version": "0.1.58",
3
+ "version": "0.1.60",
4
4
  "description": "AI-native headless community OS",
5
5
  "license": "SEE LICENSE IN LICENSE",
6
6
  "private": false,
@@ -111,6 +111,8 @@ The Flyspace dashboard is your primary surface, and it does NOT require a Slack
111
111
 
112
112
  If you only have shell access (a background/automation callback, not the live tool list), use `flyspace chat post --channel <c> [--thread <id>] --text <t> [--title <t>]` instead — same underlying write path. `flyspace chat channels` / `flyspace chat threads <channel>` are the read-side CLI equivalents.
113
113
 
114
+ To publish a doc in the channel folder as a public link (same as the Docs pane's "Copy public link"), run `flyspace docs share <path> --channel <channel-id> [--slug <name>]` (or the threads MCP tool `share_doc`); it prints the URL. Re-sharing a doc keeps its URL and updates the snapshot.
115
+
114
116
  **Do not fall back to `flyspace slack post` to create a Workspace thread.** That only works because a Slack-bound channel mirrors the post back into the dashboard — it silently does nothing useful in a channel with no Slack binding, and duplicates the message in one that has both.
115
117
 
116
118
  ## Automation Management