Clients

Clients points local coding tools at a running loopback server. Every write is previewed, backed up and reversible.

Supported clients

Write targets are a fixed allowlist of these paths. Symbolic links at the config, backup or restore path are refused.

Add clients and check setup

Add clients / Setup doctor… checks supported config files, running Workbench endpoints and saved model-host connections. Progress names the current check; results show the check time, missing configs, unreadable or linked files, and endpoint mismatches. Checks never install applications, write configs, start servers or generate output.

Choose a running endpoint, then Review config… beside one client. OpenCode, Zed and Aider can create a config even when its folder does not exist. The wiring preview lists only that client; Confirm client wiring performs the existing server and file checks before writing. Rollback restores a backup or moves an unchanged newly created config to Trash. Unreadable and linked configs require manual review. Continue’s adapter supports existing legacy JSON files; its guide covers current YAML setup, and the doctor does not create a legacy file for a new installation.

Install / setup guide opens the application’s official instructions. Creating a config does not establish that the application is installed or that it used the endpoint.

The doctor offers the same Add connection… flow for Ollama, LM Studio, ComfyUI, llama.cpp and OpenAI-compatible hosts, including when no application folder was detected. Presets fill the local URL; review it and use Test connection before Save host. Saved hosts offer Edit / test…, dated inventory results and connection errors. Tests read inventory only; failed checks retain earlier snapshots. Canceling an editor saves nothing. See Hosted models for host capabilities.

The wiring board

The board reads each writable client's config and draws what it points at against the servers running now. It reads only the URL parts and model names, never writes, and refreshes when you open the screen, refresh clients and servers, or finish a confirm or rollback. Refresh also detects clients configured or removed while the screen is open. When no clients are detected, the board lists the supported writable clients.

Wire a client

1. Refresh clients and servers, then choose a running server.
2. Preview client wiring shows the exact change to each config file. The preview binds the server's identity.
3. Confirm client wiring reads fresh serving status first and refuses a server that stopped, was replaced or is ambiguous. It then rechecks each file for changes since the preview, backs it up and writes it atomically.

The result reports zero, partial or full outcomes per client. The opencode adapter adds opencode's $schema when it is missing or empty, since opencode rewrites a loaded config without one.

Manual wiring

For a model by Hugging Face repository id, enter the repo id, a config file path and a target runtime, then Preview Wire. The review lists all three; Confirm manual wiring applies the engine's wire transaction.

Roll back

Roll back last wiring restores each file from its backup only while its contents still match what wiring wrote. A config file the wiring created moves to the Trash under the same check. Files you have since edited are kept. Older backup records without a recorded content digest require manual review and recovery from their backup.

A partial rollback keeps the action available for retry. Clients already restored are skipped, including after restarting the app.

Handoffs

Wire into clients in Compare's model guidance opens Clients with that model and port preselected, when a matching endpoint is running. After a successful wiring, Review report in Compare… opens Compare's workflow-evidence import with the endpoint and wired clients prefilled. Wiring records configuration context only; it never proves a task used the endpoint. See Compare.