Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Emanuele-web04/dpcode/llms.txt

Use this file to discover all available pages before exploring further.

DP Code is a GUI layer that wraps AI coding agents. Each agent you connect is called a provider. The server launches a provider’s CLI binary as a subprocess and communicates with it over the Codex app-server protocol (JSON-RPC over stdio), then streams structured events to the browser through a WebSocket push channel. You configure which providers are active and where their binaries live in Settings → Providers.

​
Supported providers

Codex

OpenAI’s Codex CLI agent. The default provider. Communicates via the Codex app-server JSON-RPC protocol. Requires the codex binary on your PATH.

Claude Code

Anthropic’s Claude Code CLI agent (claude binary). Supports extended thinking via maxThinkingTokens and custom launch arguments.

Gemini

Google’s Gemini CLI agent (gemini binary). Connects via the same JSON-RPC subprocess protocol.

Grok

xAI’s Grok CLI agent (grok binary). Connects via the standard subprocess protocol.

Kilo Code

Kilo Code agent (kilo binary). Supports an optional remote server URL and server password for connecting to a shared Kilo Code server.

OpenCode

OpenCode CLI agent (opencode binary). Supports an optional remote server URL and password, useful for running OpenCode server-side.

Cursor

Cursor’s agent binary (cursor-agent). Supports a custom API endpoint for enterprise or self-hosted Cursor configurations.

Pi

Pi agent (pi binary). Supports a custom agent directory path for loading agent configuration from a non-default location.

​
How providers connect

Every provider runs as a child process spawned by the DP Code server. The server communicates with the process using the Codex app-server protocol: structured JSON-RPC messages exchanged over the process’s stdin and stdout. When a turn starts, the server sends the user message and streams back provider events (text deltas, tool calls, approval requests, session status changes) in real time. 
Browser  ──WebSocket──  DP Code Server  ──stdio/JSON-RPC──  Provider CLI
The server maintains one session per active thread. When you resume a thread, the server restarts the provider process and re-attaches to its state.

​
Provider settings

Each provider exposes a shared set of settings plus its own provider-specific options.

​
Common settings (all providers)

SettingDescription
EnabledToggle the provider on or off. Disabled providers cannot be selected for new threads.
Binary pathPath to the provider’s CLI binary. Leave blank to use the system PATH default.
Custom modelsA list of additional model names to make available in the model picker, beyond the ones the provider reports at runtime.

​
Provider-specific settings

SettingDefaultDescription
Binary pathcodexPath to the Codex CLI binary.
Home path(empty)Override the Codex home directory used for auth and state storage.
SettingDefaultDescription
Binary pathclaudePath to the Claude Code CLI binary.
Launch args(empty)Extra command-line arguments passed when starting the Claude process.
SettingDefaultDescription
Binary pathcursor-agentPath to the Cursor agent binary.
API endpoint(empty)Custom API endpoint URL for enterprise or self-hosted Cursor.
SettingDefaultDescription
Binary pathgeminiPath to the Gemini CLI binary.
SettingDefaultDescription
Binary pathgrokPath to the Grok CLI binary.
SettingDefaultDescription
Binary pathkiloPath to the Kilo Code CLI binary.
Server URL(empty)URL of a remote Kilo Code server to connect to instead of spawning a local process.
Server password(empty)Authentication password for the remote server.
SettingDefaultDescription
Binary pathopencodePath to the OpenCode CLI binary.
Server URL(empty)URL of a remote OpenCode server.
Server password(empty)Authentication password for the remote server.
SettingDefaultDescription
Binary pathpiPath to the Pi agent binary.
Agent directory(empty)Directory from which the Pi agent loads its configuration.

​
Model selection

When you create a thread or start a turn, you select a model from the provider’s model list. DP Code populates the picker in two ways:
  • Runtime model list: if the provider supports it, DP Code queries the running binary for available models.
  • Custom models: any names you add under a provider’s Custom models setting appear in the picker alongside the runtime list.
You can set a default model at the project level in the project settings. Individual threads can override this default on creation or per-turn.

​
Provider health status

DP Code checks the install and auth status of each enabled provider at startup and on demand. A status badge next to each provider in Settings → Providers shows whether the binary is found, authenticated, and ready to accept sessions.
If a provider shows an error status, run the provider’s own CLI tool (for example codex auth or claude doctor) to diagnose the issue before starting a new thread in DP Code.

Build docs developers (and LLMs) love

Get started for freeTalk to us