You built an AI — a CLI agent, a local model, something entirely your own. The tool that built it can also connect it to Conduck: one brief tells your AI coding tool how to build the adapter, verify it against Conduck's own checks, and hand a working setup back to you.
Paste this into the AI coding tool that knows your engine — Claude Code, Codex, or whatever you build with — and fill in the one placeholder:
Read https://conduck.com/setup/adapter/build.md and follow it. The AI engine to connect: <describe it - e.g. "the agent in this repo" or "the Claude Code CLI on this machine">.The brief carries the whole workflow — here's the flight plan it walks your AI through, so you know what's happening while it works:
Fetches the adapter spec and records the exact revision it builds against.
How a turn runs, whether it can see images, what can run in parallel — then agrees the details with you: port, token, optional file folder.
A small HTTP server in front of your engine, reachable only from the machine itself — plus a harmless echo mode used purely for testing.
Runs Conduck’s conformance checks against echo first, then against your real engine — fixing and re-running until ordinary and deep runs both exit green.
Its own tests for timeouts, process cleanup, file confinement, and that nothing sensitive ever reaches a log.
Under a supervisor (launchd, systemd), so the adapter survives restarts — a terminal window left open is not a deployment.
A README and self-test write-up, the values you’ll need for pairing — and the pairing step itself, which is deliberately yours.
The full, exact instructions are the adapter contract plus the brief itself — this is just the map.
The finish line is not your AI's opinion — it's Conduck's automated conformance check.
The conduck-connect script's
--doctor mode (and its deeper --deep run) sends the adapter
the same requests Conduck sends and verifies the replies, exiting 0 only
when everything conforms. The brief instructs your AI to loop on that check and to
report the doctor's results, not its own summary.
SELF-TEST.md with the doctor transcript, and a SPEC-FEEDBACK.md noting anything unclear in the contract.When the doctor is green, run Conduck's setup command on the adapter's machine. It helps put HTTPS in front (Tailscale, cloudflared, or a front you already run), verifies with real requests, and prints a QR pairing code to scan in Conduck:
curl -fsSLO https://github.com/gigaduckai/conduck-connect/releases/latest/download/conduck-connect.sh && bash conduck-connect.sh --generic The wizard needs a real, interactive terminal and asks a few questions — the port, the token, the working folder. Your AI will hand you those values; you type them and scan the code. That's deliberate: pairing is the moment a person confirms what goes live.