OpenBot WorkBuddy Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKBUDDY_BRIDGE_HOME | No | 会话状态和默认任务目录,可用于隔离多个桥接实例 | %LOCALAPPDATA%\openbot-workbuddy-bridge |
| WORKBUDDY_BRIDGE_PORT | No | 本机调试端口,必须与 WorkBuddy 启动参数一致 | 19389 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workbuddy_statusB | Check the existing WorkBuddy desktop debug endpoint; does not call a model. |
| workbuddy_runA | Run a task in WorkBuddy, reusing the saved bridge conversation. deny requests read-only behavior and rejects interactive permission prompts. It is not a sandbox. allow_once leaves authorization to the WorkBuddy desktop UI; this bridge never automatically grants permissions. Model auto retains the conversation's WorkBuddy model. A timeout never triggers an automatic retry. |
| workbuddy_continueC | Continue a specific existing WorkBuddy conversation without clearing context. |
| workbuddy_cancelB | Request cancellation of a WorkBuddy conversation; does not undo past actions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools map to distinct lifecycle actions: status, run, continue, and cancel. run and continue could be confused because both can reuse a saved conversation, but the descriptions clarify that continue targets a specific existing conversation while run executes a task.
All tools use a consistent snake_case workbuddy_verb pattern. The names are predictable and immediately indicate the action.
Four tools are well-scoped for a narrow desktop bridge: check status, run, continue, and cancel. There is no obvious bloat, and each tool has a clear role.
The surface covers the core lifecycle of checking status, running, continuing, and cancelling a WorkBuddy conversation. A minor gap is the lack of an explicit tool to list or discover existing conversations, which may be needed before continue can be used confidently.