Connect your agents

npx conciv@latest init

init scans for installed harnesses (claude, codex, opencode, pi) and lists what it found in the plan it prints before doing anything — ● claude for a harness it will teach, ○ codex (not found) for one that is not installed. Pick Adjust at the prompt to choose the harnesses in a multiselect.

Approving the plan writes a marked conciv section into AGENTS.md (and CLAUDE.md if you keep one), whether or not any harness was found; the section names the harnesses you picked in a Set up for: line. Re-running init updates that section in place and reports it as already wired when it is current.

claude is the one harness with a deeper integration: init generates the plugin files under .conciv/claude-connect and installs them through claude's native plugin manager, scoped to the project. If the claude CLI is not selected the step resolves as skipped: not selected, and if the plugin manager fails init prints the two commands to run yourself.

init writes the marketplace, the plugin manifest, and the MCP bridge, but no .mcp.json: the conciv dev server writes that manifest when it connects to a claude session, so the plugin always points at the address that is actually serving.

init prints the whole plan and asks once before it writes anything; --yes approves it up front and --dry-run prints it and exits. It refuses a dirty git tree; commit first or pass --force.

Teach your agents the conciv CLI

Paste this section into AGENTS.md (and CLAUDE.md if you keep one):

<!-- conciv:start -->

## conciv

conciv connects coding agents to the app running in the browser.

Run `conciv tools --help` to discover every command. The CLI finds the running dev server itself: no config, no addresses.

- `conciv tools page` — read and drive the live page: snapshot, click, fill, edit, eval
- `conciv tools react` — inspect and edit live React components
- `conciv tools server` — inspect and nudge the dev server: config, urls, resolve, reload

These commands need the dev server running.

<!-- conciv:end -->

Install the conciv claude plugin

The plugin files are generated, not hand-written, so this one piece goes through init:

npx conciv@latest init

Pick claude at the prompt. init writes .conciv/claude-connect and installs the plugin for you. Run the two commands yourself only if init reports the step as manual:

claude plugin marketplace add .conciv/claude-connect
claude plugin install conciv-connect@conciv --scope local

init writes no .mcp.json under the plugin. The conciv dev server writes that manifest when it connects to a claude session, so the plugin points at the address that is actually serving.