Install

Installing has two steps: put the besydr program on your machine, then connect each coding agent you want it to work with.

Install the program

Linux and macOS:

curl -fsSL https://cdn.besydr.com/install.sh | sh

Windows (PowerShell 5.1 or later):

irm https://cdn.besydr.com/install.ps1 | iex

Both scripts do the same steps:

  1. Detect the platform. Builds exist for Linux (x86_64, aarch64), macOS (x86_64, aarch64) and Windows (x64, ARM64).
  2. Download the release manifest, then the archive for this platform.
  3. Compare the archive's SHA-256 checksum with the manifest. On a mismatch they install nothing.
  4. Copy the program into the install folder. No administrator rights or sudo are needed.
Linux and macOS Windows
Program besydr besydr.exe
Default folder $HOME/.local/bin %LOCALAPPDATA%\besydr\bin
PATH Prints the line to add if the folder is not on it Adds the folder to your user PATH
Needs curl, tar, and sha256sum or shasum PowerShell

Environment variables for both scripts:

Variable Meaning Default
BESYDR_VERSION Version to install, for example 0.1.0 latest
BESYDR_INSTALL_DIR Install folder see the table above
BESYDR_DOWNLOAD_URL Download host https://cdn.besydr.com

Check the result with besydr --version.

Windows supports octomind only. The commands hook, install and uninstall exist on Linux and macOS only, and the shared socket server is not available on Windows.

Connect a client

Besydr runs as one shared server per user. Each client talks to that server; the first client that needs it starts it in the background. When no server can be reached, the client carries on as if Besydr were not installed.

Octomind

Octomind lists Besydr as a plugin in its default configuration and downloads it on first use. The plugin entry runs besydr connect, which joins the shared server over standard input and output and starts it if it is not running. You run no install command.

Claude Code

besydr install claude            # add Besydr's hooks to ~/.claude/settings.json
besydr install claude --print    # show the file that would be written, write nothing
besydr uninstall claude          # remove the hooks again

A hook is a command that Claude Code runs at a fixed point of its work. install adds ten hooks that run besydr hook --client claude <hook name>. Open a new Claude Code session afterwards, because Claude Code reads the file at session start.

Codex

besydr install codex             # add Besydr's hooks to ~/.codex/hooks.json
besydr install codex --print
besydr uninstall codex

install adds nine hooks. Codex ignores a hook until you have reviewed and trusted it: start Codex after installing and open /hooks to review the new entries. Until you do, Codex runs as if Besydr were not installed. Installing again from another path changes the entries and needs a new review.

OpenCode

besydr install opencode          # write ~/.config/opencode/plugins/besydr.js
besydr install opencode --print  # show the path and the file, write nothing
besydr uninstall opencode        # delete that file

The file is a plugin without dependencies that runs besydr hook --client opencode at eight events. Restart OpenCode after installing or removing it. The plugin targets the OpenCode 1.x plugin interface (@opencode-ai/plugin 1.19.5). It has not been checked against OpenCode 2.

pi

besydr install pi                # write ~/.pi/agent/extensions/besydr.js
besydr install pi --print
besydr uninstall pi

The file is an extension without dependencies that runs besydr hook --client pi at eight events. Start pi again, or run /reload. Like every pi extension, it runs inside the pi process with your permissions.

What install changes

Client Files touched Backup
Claude Code, Codex The settings file listed above. Other settings and hooks stay; the file's keys come back in alphabetical order. Before the first change, the file is copied to <file>.besydr-backup. An existing backup is never overwritten. uninstall leaves it in place.
OpenCode, pi One file, besydr.js. Its first line is // besydr adapter and its second line holds the absolute path of the besydr program. None. A file of that name without the first line is not Besydr's: install and uninstall stop and leave it alone.

Running install twice changes nothing. The hooks and files hold the absolute path of the besydr program that ran install, so run it again after moving the program. A settings file that is not a JSON object is reported and left alone.

When a hook fails

A hook never blocks the client. If Besydr cannot be reached, does not answer in time, or gets input it does not expect, the hook prints nothing and exits with code 0. The reason is appended to hook.log in the data directory (see Configuration). The file is cut to its newest half when it passes 1 MiB.