flyspace-cli 0.1.65 → 0.1.67
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/{chunk-5ISKGSFF.js → chunk-GT2SOVPK.js} +616 -1001
- package/dist/{chunk-O7OYNQND.js → chunk-JH66T2SW.js} +798 -31
- package/dist/{chunk-GQ2QZ5WF.js → chunk-KP64MCSF.js} +333 -14
- package/dist/cli.js +1149 -626
- package/dist/index.js +2 -2
- package/dist/{threads-AR6D7V3Y.js → threads-B5FBIJLG.js} +31 -2
- package/package.json +1 -1
- package/system.capabilities.md +1 -0
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-
|
|
7
|
-
import "./chunk-
|
|
6
|
+
} from "./chunk-GT2SOVPK.js";
|
|
7
|
+
import "./chunk-JH66T2SW.js";
|
|
8
8
|
export {
|
|
9
9
|
startServer
|
|
10
10
|
};
|
|
@@ -6,6 +6,8 @@ import {
|
|
|
6
6
|
actionInputJsonSchema,
|
|
7
7
|
callAction,
|
|
8
8
|
checkPermissionAction,
|
|
9
|
+
createChannelAction,
|
|
10
|
+
createChannelOnHost,
|
|
9
11
|
createThreadAction,
|
|
10
12
|
listAutoUpdateSharesAction,
|
|
11
13
|
listChannelsAction,
|
|
@@ -13,17 +15,20 @@ import {
|
|
|
13
15
|
openDocAction,
|
|
14
16
|
postReplyAction,
|
|
15
17
|
readThreadAction,
|
|
18
|
+
renameChannelAction,
|
|
16
19
|
requestPermissionAction,
|
|
17
20
|
searchThreadsAction,
|
|
21
|
+
setChannelSlack,
|
|
22
|
+
setChannelSlackAction,
|
|
18
23
|
setUiZoomAction,
|
|
19
24
|
shareDoc,
|
|
20
25
|
shareDocAction
|
|
21
|
-
} from "./chunk-
|
|
26
|
+
} from "./chunk-KP64MCSF.js";
|
|
22
27
|
import {
|
|
23
28
|
SessionStore,
|
|
24
29
|
paths,
|
|
25
30
|
uploadLocalImages
|
|
26
|
-
} from "./chunk-
|
|
31
|
+
} from "./chunk-JH66T2SW.js";
|
|
27
32
|
|
|
28
33
|
// src/mcp/servers/threads.ts
|
|
29
34
|
import { Server } from "@modelcontextprotocol/sdk/server/index.js";
|
|
@@ -196,6 +201,30 @@ async function callTool(name, args, permission) {
|
|
|
196
201
|
str(args["thread_id"])?.trim() ?? "",
|
|
197
202
|
str(args["to_channel_id"])?.trim() ?? ""
|
|
198
203
|
);
|
|
204
|
+
case renameChannelAction.name: {
|
|
205
|
+
const r = await callAction(renameChannelAction, {
|
|
206
|
+
channel_id: str(args["channel_id"])?.trim() ?? "",
|
|
207
|
+
name: str(args["name"]) ?? ""
|
|
208
|
+
});
|
|
209
|
+
return `Renamed channel ${r.id} from ${r.from} to ${r.to}.`;
|
|
210
|
+
}
|
|
211
|
+
case createChannelAction.name: {
|
|
212
|
+
const workspace = str(args["workspace"])?.trim();
|
|
213
|
+
const slack = str(args["slack_channel_id"])?.trim();
|
|
214
|
+
return createChannelOnHost(
|
|
215
|
+
{
|
|
216
|
+
name: str(args["name"])?.trim() ?? "",
|
|
217
|
+
...workspace ? { workspace } : {},
|
|
218
|
+
...slack ? { slack_channel_id: slack } : {}
|
|
219
|
+
},
|
|
220
|
+
requester()
|
|
221
|
+
);
|
|
222
|
+
}
|
|
223
|
+
case setChannelSlackAction.name:
|
|
224
|
+
return setChannelSlack(
|
|
225
|
+
str(args["channel_id"])?.trim() ?? "",
|
|
226
|
+
str(args["slack_channel_id"])?.trim() || void 0
|
|
227
|
+
);
|
|
199
228
|
case shareDocAction.name: {
|
|
200
229
|
const channelId = str(args["channel_id"])?.trim() ?? "";
|
|
201
230
|
const path = str(args["path"])?.trim() ?? "";
|
package/package.json
CHANGED
package/system.capabilities.md
CHANGED
|
@@ -109,6 +109,7 @@ The Flyspace dashboard is your primary surface, and it does NOT require a Slack
|
|
|
109
109
|
- `create_thread` — start a new thread in any channel by id, works with or without a Slack binding
|
|
110
110
|
- `post_reply` — reply to an existing thread by id
|
|
111
111
|
- `move_thread` — move a thread to a different channel
|
|
112
|
+
- `rename_channel` — rename a channel
|
|
112
113
|
|
|
113
114
|
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.
|
|
114
115
|
|