# Install Zesia Zesia adds independent professional consultation to your existing agent. Installation does not send task context or call a model. Consultation materials are sent to `https://api.zesia.dev` only after you review and confirm them. ## One installation prompt Read https://zesia.dev/install.md and install Zesia for this agent. ## Supported hosts Read https://zesia.dev/releases/latest.json before installing. This public distribution currently supports **Claude Code**. Do not install the Claude Code package into Codex, DSH or another host; explain in English that this installer does not yet support that host. Do not infer the active agent solely from a `claude` executable being present. If the current host is unclear, ask which agent the user wants to configure. For prompt-driven installation, Claude Code must already be able to run its own model; Zesia installation does not configure or repair the host model connection. The native installation commands themselves do not call a model. The Claude Code adapter requires Claude Code >= 2.1.299 and Node.js >= 20 on PATH. Public installation is verified on Claude Code 2.1.319. Run `claude --version` and `node --version` first. Do not install or upgrade system dependencies, use sudo, or ask for administrator access. If a prerequisite is missing, explain it and stop before modifying configuration. ## Claude Code installation Use the host's native user-scoped plugin installer. The public marketplace pins a versioned HTTPS archive and its SHA-256; Claude Code verifies the archive before installation. No GitHub account, repository clone, npm installation or global package is required. ```sh claude plugin marketplace add https://zesia.dev/marketplace.json --scope user claude plugin install zesia-consult@zesia --scope user claude plugin list --json ``` Preserve existing settings and marketplace entries. If a marketplace named `zesia` is already registered to a different source, do not remove or overwrite it silently; explain the conflict and ask before replacing that specific entry. If the official marketplace is already registered, reuse it. For an installed Zesia plugin, use the update instructions below. Read the installed `zesia-consult@zesia` entry from `claude plugin list --json`. Its `installPath` is the plugin directory. Use that actual path for the configuration script; do not guess a cache version or search unrelated files. Quote paths correctly. ```sh node "/scripts/configure.mjs" --show ``` This prints only the endpoint, project, confirmation mode and whether a token is configured. Never read or display the token file itself. ## Trial access A separately issued Zesia trial token is required to send a consultation. The download contains no trial token and does not create an account. If you do not have a token, ask the person who shared the Zesia beta with you for access. Installation can finish without a token; state clearly that consultation is not configured yet. If a token is missing, ask the user to run the following command in their own terminal, with the actual plugin path substituted: ```sh node "/scripts/configure.mjs" ``` The prompt hides input and stores the token locally with mode 0600. Ctrl+C cancels. Non-interactive agent tools must not wait for a secret: they should show the user the command and explain where to run it. Never ask the user to paste a token into chat or put it in a shell argument, public file or environment file. Do not overwrite an existing token. ## Finish and verify locally - Confirm `zesia-consult@zesia` is enabled at user scope and its version matches the current release. - Use `claude plugin details zesia-consult@zesia` to confirm the four consultation Skills, the Zesia commands and the local tool bridge are present. - Re-run the configuration script with `--show`; distinguish **installed** from **token configured**. - Report what was installed, the version, and whether trial access still needs configuration. - Restart Claude Code or reload plugins when the host requires it. In a new interactive session, look for **zesia** above the prompt, or invoke `/zesia-consult:zesia` to prepare consultation materials. - If Mods are disabled by host policy or safe mode, report that the button and review pane are unavailable. Do not weaken host policy. The command/Skill route still requires explicit review and confirmation. - Do not run a handshake consultation, send a sample task, call preflight, or spend model credits to verify installation. A live consultation is a separate user action. ## Update ```sh claude plugin marketplace update zesia claude plugin update zesia-consult@zesia --scope user ``` Restart or reload when requested. Keep the existing Zesia configuration and user preferences. Do not uninstall first or replace user settings with a template. ## Manual download Versioned download URLs, sizes and SHA-256 values are listed at https://zesia.dev/releases/latest.json. The human-readable page is https://zesia.dev/install. If using a ZIP manually, verify its SHA-256 before extracting or running it. Do not treat an HTML error page as a successful download. ## Behavior and limits Preparation is local. You review the question, evidence, destination and full materials before each send, including follow-up rounds. The consultant returns advice to the original agent; it does not execute code or authorize further actions. No expert knowledge database or independent project execution is promised. Cloud consultation uses A2A. The current Claude Code adapter exposes local tools through a bundled MCP bridge; that bridge does not replace the cloud A2A protocol. Installation and consultation can be subject to the host's ordinary permission prompts. User-scoped installation avoids administrator privileges; it does not bypass host trust policies. Do not automatically retry a consultation whose delivery outcome is unknown.