Install

Salidium needs Node 24 or newer. There is nothing else to install first.

On first run it looks for Claude Code and Codex, prints the files it wants to change, and asks once. Answer anything but yes and nothing is written.

What it changes

~/.claude/settings.json

Claude Code hook entries.

~/.codex/hooks.json

Codex hook entries.

~/.salidium/hooks/relay.sh

The relay those hooks call, readable only by you.

Before each change to those settings files, the file is copied to <name>.salidium-backup, so that copy is the state immediately before the most recent change rather than the original. The relay is rewritten rather than backed up, because Salidium is the only thing that writes it. Only entries Salidium owns are added or replaced, and salidium uninstall-hooks takes them out again.

Codex trusts a hook by the hash of its definition, so a changed hook has to be shown to it once. Salidium says so when it happens: open /hooks in Codex and trust it.

What it reads

Salidium imports the last seven days of the session files your agents already write. Anything older is not read. SALIDIUM_HISTORY_DAYS changes that; the daemon reads it every time it starts, so set it and then run salidium restart if one is already running.

Running it again

• Run the same command later and it reopens whatever is already running.
• If the CLI is newer than the running daemon, it stops and restarts it.
• In a terminal that is not interactive it prints the address instead of opening a browser, and without --yes it changes nothing at all.