Setup Run the command

Run the setup command

You picked OpenClaw or Hermes in the Conduck app - a self-hosted agent harness, what this site calls an agent gateway. Copy the command below and run it in a terminal on the server where that agent lives. --setup skips the welcome menu and goes straight to gateway selection.

on your server

curl -fsSLO https://github.com/gigaduckai/conduck-connect/releases/latest/download/conduck-connect.sh && bash conduck-connect.sh --setup

Downloads conduck-connect.sh from GitHub Releases, then runs it. View the script on GitHub

Are you an AI coding tool?

If somebody pointed you at this page and asked you to run the command above, read this first. On this page, “agent” means the AI being paired — OpenClaw or Hermes — not you.

You cannot finish --setup. It is interactive, it has no answer flags to pass, and it ends in a QR code a person scans with the Conduck app on a phone. Hand the command to your operator and stop. With no terminal attached it exits 4; if the operator stops partway it exits 3, which means no setup code was printed — never report that as a completed pairing.
The checks are yours to run. bash conduck-connect.sh --check-server <url> and bash conduck-connect.sh --check-adapter <url> take the address as an argument, read the token from CONDUCK_TOKEN so it never reaches argv, change no configuration, and end in one machine-readable summary line. Set CI=1: without it, a check that passes then asks whether to continue into setup and waits there — after it has already printed its result.
To read what is already set up, run bash conduck-connect.sh --list --json. One JSON object: every saved setup’s id, address, transport, model and shared folder, plus whether its file server is running. It asks nothing, changes nothing, and prints no token, password, or setup code.
Building an adapter for an AI engine of your own? That is a different job with its own brief — Build it with your AI.

What the script will ask

It reports every OpenClaw or Hermes install it finds.
You explicitly choose a detected gateway or a different OpenAI-compatible server. Detection never decides for you.
You pick how to expose it over HTTPS — a private Tailscale link, a free public link, Cloudflare, or your own HTTPS.
It offers file transfer, the step that changes the most on your machine. Saying yes sets up a shared folder for attachments, which on OpenClaw and Hermes is the agent’s own working directory, puts a small file server in front of it as a background service that starts again on its own, and adds a block of Conduck instructions to your agent’s own guidance file. Each change is shown before it happens, and you can skip the whole step.
It verifies everything with real requests before printing the code.
At any question, i explains it in plain language and q stops the run; where stepping back makes sense, b returns to the previous question.

Stopped before the code? Read what it printed

Setup is approved one step at a time, not as one transaction. It stops at the step that failed and names what it found. No setup code means nothing is paired — but any change you already approved stays in place, and q does not undo it. The run says so as it goes.

Fix what it named, then run the command again. Re-running is safe: a file lane an earlier run set up is reused rather than rebuilt, and if that run was cut off with an HTTPS route still open, the next one reports it and offers to close it.

Common failures and their fixes Troubleshoot conduck-connect on GitHub

Then pick up your phone

conduck-connect ends with a QR code and a setup code. Back in the Conduck app, scan the QR code — or paste the setup code (on a Mac, paste).

That code carries your gateway token, so treat it like a password: anyone who scans or photographs it reaches your gateway too, until you rotate the token.

The code is an open format - a gateway may mint it natively instead of running the script; the minting rules live with conduck-connect on GitHub.

Full setup guide