SideDesk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| data_dir | No | Path to the plugin data directory, passed as --data_dir=${PLUGIN_DATA} in the MCP server arguments. Used to store session state, shadow copies, and user-provided API keys. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sidedesk_openA | 打开或刷新右侧 SideDesk · 副席面板,查看双引擎人物卡、运行中任务与待验收的影子副本 Diff。支持空参数调用。 |
| sidedesk_list_personasA | 列出 SideDesk 中配置的所有人物卡(含驱动引擎类型、模型与权限),绝不返回任何密钥。 |
| sidedesk_dispatchA | 将后端分析、审计或编码任务派发给 SideDesk 副席中的指定人物卡(自动按人物卡驱动路由至本机 Codex CLI 或 OpenAI 兼容 API)。默认必须在隔离影子副本中执行(read-only / workspace-write),原工程目录零修改;仅当用户明确要求 Turbo / 直接改原目录,或目标人物卡默认权限为 turbo-direct 时,才允许使用 turbo-direct(跳过影子副本与容量熔断,直接在原目录无沙箱执行)。 |
| sidedesk_job_statusA | 查询指定 jobId 的运行状态、实时进度、影子副本改动摘要、源目录完整性校验与最终回复。可配合 waitSeconds 优雅等待。 |
| sidedesk_abort_jobA | 立即中止运行中的 Codex 进程树或 OpenAI API 流式请求,并将任务标记为 aborted(绝不自动重发)。 |
| app_get_stateB | UI 专用:拉取脱敏后的人物卡、会话、实时任务流、待验收影子副本与可撤销备份。 |
| app_refresh_quotaB | UI 专用:零网络开销重新扫描本机 ~/.codex/sessions 最新 token_count 快照,并同步当前话题上下文水位。 |
| app_get_diffB | UI 专用:按需计算并拉取指定影子副本的完整文件变更与红绿 Unified Diff。 |
| app_save_personaB | UI 专用:新增或编辑人物卡(支持 Codex CLI 与 OpenAI 兼容 API,返回脱敏结构)。 |
| app_delete_personaB | UI 专用:删除指定人物卡。 |
| app_test_providerB | UI 专用:provider=codex-cli 时异步重新探测本机 codex.exe;provider=openai-compatible 时向 Base URL 发最小化探测请求返回延迟或错误。 |
| app_boss_sendC | UI 专用:用户在副席直接给当前人物卡发消息(<50ms 瞬时异步启动,支持三组权限胶囊与图片附件)。 |
| app_save_draftB | UI 专用:实时把输入框草稿与目标路径持久化到后端,防收起面板丢失。 |
| app_abort_jobB | UI 专用:强杀运行中的 Codex 进程树或中断 API 流式请求。 |
| app_emergency_tripA | UI 专用:一次性强杀所有会话运行中的 Codex 进程树与在途 API 请求(绝不重发),并将在途全局 Turbo 直通安全降级回影子隔离。 |
| app_apply_shadowB | UI 专用:冲突预检 → 自动快照备份原文件 → 应用改动到原工程目录。 |
| app_undo_last_applyB | UI 专用:按备份快照精确还原修改/删除的原文件,并清理该轮新增文件。 |
| app_discard_shadowB | UI 专用:删除影子副本及其未应用的改动,不触碰原目录。 |
| app_new_sessionB | UI 专用:为指定人物卡与工程目录开启全新话题(旧话题保留归档),可选继承压缩上下文摘要(已有新鲜摘要时零额度复用)。 |
| app_save_user_profileA | UI 专用:保存用户的称呼、头像与外观主题偏好到插件持久化目录;自定义称呼将自动注入双引擎指令。 |
| app_set_themeA | UI 专用:轻量持久化外观主题模式(auto 跟随宿主 / light 浅色羊皮纸 / dark 深色暖炭),防关面板丢失。 |
| app_save_default_permissionsB | UI 专用:保存三组全局默认权限胶囊(fileScope / commandPolicy / networkPolicy)。 |
| app_clear_inherited_summaryA | UI 专用:移除当前话题的 inheritedSummary,后续轮次不再注入前序摘要。 |
| app_update_inherited_summaryC | UI 专用:允许用户直接微调当前话题顶部的继承摘要内容。 |
| app_compress_sessionB | UI 专用:将指定话题压缩为摘要、重置底层长线程并将摘要挂载到当前话题顶部继续。 |
| app_rename_sessionB | UI 专用:修改指定话题的标题。 |
| app_export_sessionA | UI 专用:导出指定话题完整记录为 .md 文件并返回内容与保存路径。 |
| app_clear_sessionB | UI 专用:清空指定话题的对话记录并重置线程。 |
| app_delete_sessionA | UI 专用:永久删除指定归档或当前话题记录。 |
| app_paste_clipboard_imageA | UI 专用:读取系统剪贴板中的位图截图或复制的图片文件,供头像裁剪或聊天附图使用。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SideDesk · 副席界面 | SideDesk 副席单文件交互面板(多引擎人物卡、实时进度、红绿 Diff 验收与撤销) |
TDQS
Scored across 30 tools
The tool set is split into an agent-facing sidedesk_* group and a UI-facing app_* group, and the descriptions do a reasonable job explaining that separation. But several pairs overlap in practice: sidedesk_abort_job vs app_abort_job, sidedesk_dispatch vs app_boss_send, sidedesk_job_status vs app_get_state, and app_undo_last_apply vs app_discard_shadow. An agent must read the descriptions carefully to avoid picking the UI-only twin of an operation it needs.
Names are snake_case and carry clear sidedesk_/app_ prefixes, but they mix verb_noun forms (app_get_diff, app_save_persona) with noun_verb and imperative outliers (app_boss_send, app_emergency_trip, app_apply_shadow, sidedesk_dispatch). It's readable, but there's no single predictable pattern to infer a tool's name.
30 tools is too heavy for this surface, and about 25 of them are single-purpose UI micro-operations (theme, draft, inherited summary edits). Many could be folded into coarser actions without losing capability.
Coverage of the domain is strong: persona CRUD and test, session lifecycle (new/rename/compress/clear/delete/export), shadow diff/apply/discard/undo with backups, permission defaults, quota, drafts, and profile. Gaps are minor, such as no single-persona-get or job-history listing, but nothing blocks core workflows.