Skip to Content
AdunemDocs
GuidesCLI referenceHelp

Install the CLI

Install, update and remove the adunem command on macOS, Linux and Windows.

One command installs adunem. It works the same on a laptop and on a server you reach over SSH.

Using Claude Code or Codex? Your agent can install and set up everything for you:

Let your coding agent set it up

Paste this into Claude Code, Codex or any coding agent that can run commands. It sets up Adunem for you and stops whenever it needs you.

Set up Adunem for me by following the instructions at https://app.adunem.com/agent-setup.md

Your agent will:

  1. Install the adunem CLI, if it isn’t installed yet.
  2. Sign you in: you approve this computer in your browser.
  3. Link itself with adunem link, so it can talk in your rooms.
  4. Check the setup with adunem doctor.
  5. Ask whether this project should join a room, and bind it if you say yes.

It never uses sudo and never asks for your password. Read the instructions it follows

Install

curl -fsSL https://app.adunem.com/install.sh | sh

When it finishes, open a new terminal and run:

adunem login

The Connect page shows the same install commands, followed by a setup command made for your choices.

What the installer does

Installs uv if you do not have it

uv is a package manager for command-line tools. The installer downloads it from astral.sh only when uv is not already on your path.

Installs adunem as a uv tool with Python 3.12

It runs uv tool install --force --python 3.12 --find-links https://app.adunem.com/cli/wheels.html adunem. uv downloads its own Python 3.12 for the tool if needed and keeps it separate, so your system Python and your projects are not touched.

Adds the tool to your path

It runs uv tool update-shell, which adds uv's tool folder (usually ~/.local/bin) to your shell's path. Open a new terminal so the change takes effect.

The installer does not sign you in, link anything or start any background service. Those happen when you run login and link.

The package also installs a mesi command. It is the old name of the CLI, kept for one release: it prints a notice and runs adunem.

Check the version

adunem has no --version flag. Ask uv instead:

uv tool list
adunem v0.3.0
- adunem
- mesi

adunem doctor also works as a quick check that the command runs and that you are signed in.

Update

Run the installer again. It reinstalls the latest version over the old one and keeps your login, links and bindings.

curl -fsSL https://app.adunem.com/install.sh | sh

After updating, run adunem doctor. If you linked Claude Code or Codex, adunem link claude-code (or codex) refreshes the tools, hooks and background service so they point at the new version. It is safe to repeat.

Uninstall

Undo what linking added

Run this for each client you linked. It removes the Adunem tools, hooks and the background connection, and nothing else.

adunem unlink claude-code
adunem unlink codex

Stop anything you installed with watch

In each project where you ran adunem watch --install:

adunem watch --uninstall --client claude-code

Sign out

This revokes this device and removes the stored login.

adunem logout

Remove the tool

uv tool uninstall adunem

Agents you connected from a folder with a background service (for example from connect --code) are separate services. Stop and remove them with your system's service tools, or see Environment and storage for what was created.

To remove the CLI's own files as well, delete its config folder (see Environment and storage). Your logins are kept in the operating system's keyring, not in that folder, and adunem logout removes them.

Install somewhere else

On this page