Coding-tool setup

Every tool is unvalidated at launch. A tool is listed where compatibility can be established, and only with a dated validation record. Each tool needs its own supported configuration and tested behavior.

We also want developers to use HIPS with coding tools, including Claude Code where compatibility can be established. An intended setup helper will guide configuration for supported tools. Tool-specific instructions will explain what changes, how credentials are handled, and how to restore the previous setup.

A tool is listed as supported only after every column is tested on a stated version; one untested column keeps the row at unvalidated. HIPS Code is the first row and is tested first, since the company controls both ends.

HIPS Code is the company's own coding agent for the terminal and the desktop, a fork of an open-source project, rebranded and themed by HIPS, which will run on HIPS inference. It is the first row of the matrix and is tested first. It needs no API key: it signs in as you with OAuth device authorization, showing a code XXXX-XXXX, a QR code and a link in the terminal, which you approve in the Console while signed in, choosing the workspace its usage is attributed to; it keeps the tokens in the operating system's keystore (how sign-in works). HIPS_API_KEY remains the path for CI and scripted use. Its page here is published once its HIPS provider is built against the gateway, with its validation record Not decided yet.

A coding tool's own gateway or proxy documentation describes that tool's expectations, not HIPS's compatibility with them. OpenAI compatibility alone does not establish another vendor's interface or a coding tool's protocol expectations: serving POST /v1/chat/completions says nothing about a Messages-style interface, a Responses-shaped tool loop, a tool's system-prompt conventions, its streaming event names or its retry behavior. Each is tested or it is unvalidated. Until a row says supported, no page says HIPS works with the tool.

Every tool that takes an OpenAI-style base URL is configured with the same three names: HIPS_API_KEY, HIPS_BASE_URL (https://ai.hips.com/v1) and HIPS_MODEL. No credential, and no command that implies a working integration, appears here until a row is validated.

A future product, described as intended and never a download. It should discover the tool and version, prefer temporary session configuration first, preview persistent changes, back up existing settings, configure the published base URL, authentication and model mapping, avoid printing secrets, test only with permission to incur usage, and provide selective undo. It must not quietly change unrelated providers or global defaults.