Install

To have your own coding agent install and set it up for you, give it Point your agent here.

Open Conduit ships two commands, kept side by side:

• open-conduit is the daemon and operator client.
• os is the small toolbelt that shell commands call from inside a run. The daemon looks for it beside its own executable.

Homebrew, the release archives and the install script also carry the extension packages beside the binaries, in extensions/: the first-party integrations, executors and providers (GitHub, Slack, Linear, Jira, Claude Code, the Codex executor, the shell executor and the rest), and the setup assistant in extensions/setup/, which runs init --with claude (or --with codex) and the browser setup and gives a fresh install its first configuration. go install doesn’t bring them; see below.

A release build sends anonymous usage telemetry: a daily count of runs and the scopes and first-party extensions in use. Usage telemetry lists exactly what is sent; open-conduit serve --no-telemetry or DO_NOT_TRACK=1 turns it off.

You also need the CLIs of the services you use: a coding agent for agent bindings, either Claude Code or the Codex CLI, installed and signed in, and optionally the GitHub CLI (gh), whose login is the default GitHub credential.

Homebrew

brew install open-conduit/tap/open-conduit

The cask puts only open-conduit on your PATH. os stays beside it in the cask’s own directory, where the daemon finds it, so it can’t clash with another command of that name. A brew upgrade keeps the background service and restarts it on the new version. Run open-conduit service uninstall before brew uninstall, or use brew uninstall --zap, which removes the service with the cask.

Release binaries

Archives for macOS and Linux, on amd64 and arm64, are on the releases page as open-conduit_<version>_<os>_<arch>.tar.gz, with a checksums.txt and its cosign signature, checksums.txt.sigstore.json. SECURITY.md shows how to verify both by hand. Each holds open-conduit, os and the bundled extensions/ directory; keep them together.

The install script downloads the latest release, verifies its checksum (and, if cosign is installed, the signature on the checksums), puts both binaries and extensions/ in ~/.local/lib/open-conduit and links open-conduit into ~/.local/bin:

curl -fsSL https://raw.githubusercontent.com/open-conduit/open-conduit/main/install.sh | sh

Set OPEN_CONDUIT_VERSION=v0.1.0 (or another tag) to install a particular release, and BIN_DIR or INSTALL_DIR to change where the link and the binaries go.

go install

You need Go 1.24.2 or later. Install both commands, which puts them side by side in $(go env GOBIN) (default ~/go/bin):

go install github.com/open-conduit/open-conduit/cmd/open-conduit@latest
go install github.com/open-conduit/open-conduit/cmd/os@latest

os lands on your PATH there under that generic name. Install both into the same directory, or point the daemon elsewhere with serve --toolbelt-dir DIR.

go install doesn’t bring the extension packages: neither the first-party ones, without which the daemon has no integrations or executors, nor the setup assistant, which lives in its own repository, open-conduit/extension-setup. Build them from source as below and install each one you use with open-conduit extension install dist/packages/NAME (setup, github, claude-code and so on). Without the setup assistant, configure with open-conduit init github (or slack, linear, jira) and config set, and serve needs a config file to start.

From source

You need Go 1.24.2 or later, Git and Make:

git clone https://github.com/open-conduit/open-conduit.git
cd open-conduit
make build                 # writes bin/open-conduit and bin/os
make packages              # builds each package into dist/packages/NAME: setup, github, slack, claude-code, codex, shell and the rest
cp bin/open-conduit bin/os /usr/local/bin/   # or anywhere on your PATH, side by side
open-conduit extension install dist/packages/setup
open-conduit extension install dist/packages/github        # and each other package you use,
open-conduit extension install dist/packages/claude-code   # such as codex to run agents on Codex

Upgrading

open-conduit upgrade --check   # say whether a newer release is out
open-conduit upgrade           # install it

upgrade downloads the latest release for this machine, checks it against the release’s checksums.txt and replaces open-conduit, the os beside it and the bundled extensions/ directory, wherever they are installed. Packages you installed yourself, in the config directory, are left alone. If the background service is running, it then restarts it on the new version; pass --no-restart to leave that to you. A daemon you started with open-conduit serve keeps the old version until you restart it. --version 1.9.0 installs a particular release.

A Homebrew install belongs to Homebrew: upgrade tells you to run brew upgrade --cask open-conduit instead.

The web view says when a newer release is out, in the status line along the bottom, and its Update page installs it the same way (see the web view).

Next: run open-conduit init --with claude (or --with codex) and let your agent set it up with you, as the quick start describes. To talk the setup through in the browser instead, start the daemon with no config (open-conduit serve) and open the Setup page of open-conduit web; a session there proposes the config and you approve and apply it (set it up in the browser).