Agents

Cline

VS Code extension; CLI and hosted agents are separate products.

Setting up with an AI assistant? Copy the setup prompt or open this guide as Markdown.

Setup prompt

Read https://zrelay.net/docs/ai.md and https://zrelay.net/docs/md/agents/coding-agents/cline.md first.

Set up the Cline VS Code extension for Zrelay. Detect my OS and installed Cline version; consult https://docs.cline.bot/provider-config/openai-compatible and https://keys.zrelay.net/api/catalog. Preserve existing providers, settings, Plan/Act selections and GitHub Copilot. Use the supported settings UI: OpenAI Compatible, base URL https://api.zrelay.net/v1, enabled Chat Completions model deepseek-v4.1-flash, context 128000, maximum output 4096, matching my key's provider/pool. Confirm these values against the current catalog. Keep Azure Identity and image support off for this text setup. Have me enter the key locally in Cline; never request, read, print or copy it into chat, commands or repository files. Do not guess globalState, SecretStorage or private configuration paths. If UI automation is unavailable, provide exact manual fields. Validate configuration without inference. Ask before installing software, replacing an occupied connection or making any paid test/Verify request. Report what was inspected and leave streaming/tool-loop compatibility explicitly untested. Treat Cline CLI and hosted agents as separate products.

Manual setup

1. Open Cline Settings > OpenAI Compatible. Preserve other connections and Plan/Act selections. If the slot is occupied, choose a separate configuration supported by the installed version or explicitly decide to change it.

2. Base URL: https://api.zrelay.net/v1. Enter the key locally. Model ID: deepseek-v4.1-flash (Custom Model ID if absent). Under Model Configuration set Context Window Size: 128000 and Max Output Tokens: 4096. Use the matching DeepSeek Flex/Prime key.

3. Leave Azure Identity and Supports Images off for this text recipe; do not add custom headers. Review Plan and Act independently. Inspect fields without pressing Verify or starting a task.

4. The inspected adapter appends /chat/completions and uses Bearer; this is not Responses. Do not edit globalState or secret files. cline --version and cline auth --help identify the separate CLI, whose limits need independent confirmation; do not copy extension secrets into it.

Configuration and commands

Use the exact fields in the manual above in the client’s supported settings UI. This client has no file-based recipe here; preserve existing connections and enter the key locally.

Alternative: ask an AI assistant

Copy this complete prompt into your coding assistant. It describes configuration work; installation and paid tests need your authorization.

Setup prompt

Set up the Cline VS Code extension for Zrelay. Detect my OS and installed Cline version; consult https://docs.cline.bot/provider-config/openai-compatible and https://keys.zrelay.net/api/catalog. Preserve existing providers, settings, Plan/Act selections and GitHub Copilot. Use the supported settings UI: OpenAI Compatible, base URL https://api.zrelay.net/v1, enabled Chat Completions model deepseek-v4.1-flash, context 128000, maximum output 4096, matching my key's provider/pool. Confirm these values against the current catalog. Keep Azure Identity and image support off for this text setup. Have me enter the key locally in Cline; never request, read, print or copy it into chat, commands or repository files. Do not guess globalState, SecretStorage or private configuration paths. If UI automation is unavailable, provide exact manual fields. Validate configuration without inference. Ask before installing software, replacing an occupied connection or making any paid test/Verify request. Report what was inspected and leave streaming/tool-loop compatibility explicitly untested. Treat Cline CLI and hosted agents as separate products.

Limits and verification

The current CLI documents providers.json storage; do not assume universal VS Code SecretStorage. Documented streaming/tools are not a tested Zrelay loop. Do not promise Computer Use or add a control absent from the inspected UI.

These recipes were reviewed against documentation and public catalog data. No client installation, authenticated request, paid inference, streaming or tool loop was executed. Validate configuration first; a later short text test does not establish complete agent compatibility.

Recheck the live catalog and your key’s provider/pool. The reviewed examples have 128000 input and 4096 output maxima unless a client limitation above prevents controlling the request. Never print, log or commit credentials.