claude-desktop-to-code
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CC_HANDOFF_CLI | No | Path to the Claude Code CLI. Default is 'claude'. | claude |
| CC_HANDOFF_CONFIG | No | Path to the configuration file. Default is ~/.config/cc-handoff/config.toml. | ~/.config/cc-handoff/config.toml |
| CC_HANDOFF_DRY_RUN | No | When set, terminal launches return the argv instead of opening a window. Unset by default. | |
| CC_HANDOFF_TIMEOUT | No | Timeout in seconds for headless Claude Code calls. Default is 600. | 600 |
| CC_HANDOFF_TERMINAL | No | Terminal to use for handoff. Auto-detected by default. | auto-detected |
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 |
|---|---|
| list_profilesA | List the profiles work can be routed to. Each is a directory with its own CLAUDE.md. |
| ask_claude_codeA | Run a prompt through Claude Code headlessly in a profile and return the answer. Set allow_edits only when the user has asked for files to be changed. The returned session_id can be passed to handoff_to_terminal to continue the same session on screen. |
| handoff_to_terminalC | Reopen a headless session from ask_claude_code in a real terminal window. The session keeps its full history, so the user picks up exactly where the headless run left off. |
| open_in_claude_codeA | Write a brief to /.claude/HANDOFF.md and open Claude Code there. Use for work the user should drive themselves. The brief is written verbatim; it is never passed through a shell. If a session is already open in that profile, no second window is opened. Tell the user to switch to it and say "reread HANDOFF.md". Pass new_window to open one anyway. |
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 three Claude Code-invoking tools (ask_claude_code, handoff_to_terminal, open_in_claude_code) share the same underlying target, but their descriptions clearly separate headless execution, continuing a session on screen, and opening a user-driven window. A small amount of overlap remains between handoff_to_terminal and open_in_claude_code since both surface a window, but the intent differences are spelled out.
All names are lowercase snake_case starting with a verb (list_, ask_, handoff_, open_), which is readable and predictable. The pattern varies slightly between verb_noun and verb_preposition_noun forms, but that maps onto meaning rather than being arbitrary.
Four tools is well-scoped for a bridge server that routes and hands off work to Claude Code. Each tool covers a distinct step in the workflow and none feels redundant or superfluous.
The surface covers profile discovery, headless execution, session continuation, and user-driven handoff, which is a coherent lifecycle. Minor gaps exist around session/state management (e.g., listing or managing existing sessions or profiles), but core workflows are reachable.