Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COMMANDCODE_API_KEYNoCredential for the commandcode-goat route
DSH_BRIDGE_PROVIDERNoProvider route: 'opencode-go' (default) or 'commandcode-goat'opencode-go
OPENCODE_GO_API_KEYNoCredential for the opencode-go route
DSH_BRIDGE_DATA_ROOTNoPrivate writable location for task state and evidence
DSH_BRIDGE_PROXY_MODENoProxy mode for the child process: 'inherit' (default) or explicit 'direct'inherit
DSH_BRIDGE_RUNTIME_ROOTNoAbsolute directory containing the DSH runtime's node_modules
DSH_BRIDGE_ALLOWED_ROOTSNoExisting workspace roots; separate with ';' on Windows or ':' on POSIX
DSH_BRIDGE_DESKTOP_PROFILE_PATCHNoOptional local desktop profile path; use an absent path when no desktop profile is available

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
dsh_get_capabilitiesA

Read-only. Reports the community-edition DSH paths and versions, the pinned model route and any drift from the live desktop profile, credential presence (never its value), the SDK methods actually present in the pinned runtime, workspace bounds and the honest limit list. Starts no model request.

dsh_submit_taskA

Validates the workspace against the allowed roots, creates an isolated task directory and DSH_HOME, starts a private SDK runtime process, sends the stage prompt and returns immediately with taskId/sessionId/state. It does NOT wait for the work to finish: use dsh_wait_task and dsh_get_result. May create or modify files inside the workspace.

dsh_prepare_recoveryA

Read-only. Loads a persisted task record and checkpoint under DATA_ROOT/tasks with anchored, symlink-refusing reads, checks that the caller workspace matches the recorded workspace, and returns a bounded scrubbed plan with a planToken bound to the exact source record/checkpoint and current workspace state. Starts no runtime and makes no model request; never probes or reuses the recorded PID and never exposes prompts, context, environment, reasoning or the recorded argv. A source still in this bridge process's live map is refused; use dsh_continue_task. A missing or corrupt checkpoint is an explicit refusal. A source recorded accepted/starting/running produces a warning and requires allowUnsettledSource=true at recovery.

dsh_recover_taskA

Starts a NEW task, private SDK runtime and session from a plan produced by dsh_prepare_recovery, using the checked original goal/constraints, a bounded checkpoint summary and the current instructions. The old task tree is never written and its stages are never appended. The recorded PID and recorded verification argv are never reused or executed: fresh caller-supplied verification settings are required when the source configured verification, and original protected pins must still match. A durable atomic claim returns the same new taskId with alreadyRecovered=true on retries, including after a bridge restart. A source recorded accepted/starting/running requires explicit allowUnsettledSource=true; that is a caller acknowledgment, not bridge proof of old-process liveness.

dsh_get_taskB

Returns the eight-state task state, the current stage summary, runtime liveness, cancel/timeout facts and whether the task can accept another stage. Never blocks.

dsh_wait_taskA

Blocks up to timeoutMs (default 30000, hard cap 120000 = limits.waitTimeoutMaxMs in dsh_get_capabilities) waiting for the current stage to end. On timeout it returns the latest status and says you may simply call it again. It never waits indefinitely and never treats a timeout as failure. IMPORTANT for clients: set your own per-request timeout above limits.clientRequestTimeoutFloorMs (125000ms); an MCP client's SDK default is 60s, so a long wait will otherwise be aborted client-side and look like a transport failure.

dsh_get_resultA

Returns the latest or a named stage. Model report and bridge evidence are separate. modelReport.previewTruncated means only the display preview was shortened; upstreamTruncated means the model hit its output limit and the stage is incomplete. Full recorded text stays on disk. bridgeObserved.toolCallsTotal is the TRUE tool-call total (not the retained 60); usageAccounting separates latest, stage sum and task sum (missing counters are null, never 0); verification.status states whether the bridge command ran, its attempts/exit code and any not-run reason; deliverySummary gives a compact deterministic acceptance basis and evidence paths. Model-internal reasoning is excluded.

dsh_get_eventsA

Reads at most limit (default 25, hard cap 100) events from the task event log, starting at an opaque cursor. Logs are scanned in bounded chunks, never loaded whole; a trailing partial JSONL line is not consumed. Cursors are bound to task id and file identity, and invalid/cross-task/stale cursors are refused. Live and persisted-history reads are read-only: no PID is probed or controlled, no runtime is started and no model request is made. Secrets are scrubbed and model reasoning is stripped at output as well as storage.

dsh_list_historyA

Read-only view of tasks recorded under the configured DATA_ROOT/tasks by earlier bridge processes. Returns at most limit (default 20, hard maximum 100) projected summaries. Every response fixes source=persisted-history, runtimeAttached=false, runtimeAlive=null, canContinue=false and canCancel=false. The recorded state, timestamps and PID are evidence only; this tool never probes, resumes, continues, cancels or restarts a recorded runtime, and never recaptures a workspace. One corrupt entry is reported without hiding valid entries.

dsh_get_historyA

Reads one task recorded by an earlier bridge process, optionally one stage. Returns a fixed read-only envelope (source=persisted-history, runtimeAttached=false, runtimeAlive=null, canContinue=false, canCancel=false) plus projected, scrubbed task/stage/checkpoint/delivery evidence. Prompts, context, environment, reasoning, raw argv and record-controlled absolute paths are not returned. A missing or corrupt stage result is reported explicitly and never replaced with an earlier stage. The recorded PID is never probed or used for process control.

dsh_continue_taskA

Continues the SAME live session so the model still has its earlier work in context. Refuses unknown taskIds, a stage already in flight, cancelled tasks, tasks whose runtime died, and any stage after shutdown. Each stage gets its own number and its own result; earlier stage evidence is never overwritten.

dsh_submit_reviewA

Records a caller-reported external acceptance receipt bound to the exact latest settled stage. source=caller-reported: supplied commands and check outputs are DATA ONLY and are never executed. reviewedSource paths must be workspace-relative regular no-link files whose current SHA-256 matches. The receipt is persisted before any prompt. outcome=pass/blocked never starts the model; outcome=fail with actionable findings starts ONE repair stage in the same live session, even if host verification previously passed. Same reviewId with the same body is idempotent and never sends a second prompt; conflicting reuse is refused. Stale/in-flight/cancelled/historical/dead-runtime controls are refused without modifying files.

dsh_cancel_taskA

Stops the SDK process this bridge started for THIS task only, then verifies the pid is gone. It never touches the user's running DSH Desktop. Because the SDK has no per-turn cancel, the turn is interrupted rather than gracefully cancelled, and files may already have been partly modified; the returned diff is what the bridge actually observed.

dsh_export_deliveryA

Copies a recorded delivery index, selected source snapshot and evidence to a new directory inside allowed workspace roots. It exports a settled live task or a validated persisted-history task when no live task exists. Historical export requires task/deliveryStage/index taskId and stageCount alignment and still validates every recorded artifact hash and path; it copies recorded source bytes only, never reruns acceptance, never recaptures the current workspace and starts no model request or runtime.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 14 tools

Disambiguation4/5

Most tools have a clearly distinct purpose (submit/wait/get_result/get_events/continue/cancel map to discrete lifecycle actions), and descriptions explicitly state what each does NOT do. The riskiest overlaps are within the read family — dsh_get_task vs dsh_get_result vs dsh_get_history vs dsh_list_history — where an agent must parse long descriptions to pick correctly.

Naming Consistency4/5

All names use a uniform dsh_ prefix with snake_case verb_noun structure (dsh_submit_task, dsh_get_events, dsh_cancel_task), which is highly predictable. Minor deviation: the prepare_recovery/recover_task pair splits one conceptual operation across two verbs, and some names are verb_noun_noun (dsh_submit_review, dsh_get_capabilities), slightly reducing uniformity.

Tool Count4/5

14 tools sit comfortably in the expected 3-15 band, and each maps to a real lifecycle stage (discovery, execution, observation, review, export, recovery). The set is on the heavier side but no tool looks redundant or trivially trivial.

Completeness4/5

The surface covers a full task lifecycle: capabilities, submit, poll/wait, result, events, continue, cancel, review, delivery export, history, and recovery. Minor gaps: there is no way to enumerate live tasks in the current bridge process (only persisted history is listable), and no explicit cleanup/delete of task directories.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues