Install

Irie’s first release, 0.1.0, has no download yet, so you build it from its source code, the files it’s written in. It takes a few commands in a terminal, the window where you type commands.

What you need

• A Mac or a Linux computer. Windows isn’t planned for version 1.
• Go 1.26 or later, the programming language Irie is written in: go.dev/doc/install.
• git, which keeps the history of code: git-scm.com/install.
• tmux, which keeps programs running in the background: tmux’s install page. Irie is written against tmux 3.7b.
• Claude Code, the coding agent Irie starts by default, signed in to your own account: its setup page.
• Any terminal, Ghostty included.

By default Irie asks Claude Code for Opus 5.5 at max effort in auto mode, so your account must allow them. You can change each one in a profile.

To check what you have, run these. Each should print a version.

go version
git --version
tmux -V
claude --version

Build it

Get the code, then build it. go install puts the irie program in Go’s folder for programs: ~/go/bin, unless you changed it.

git clone https://github.com/irie-people/irie
cd irie
go install ./cmd/irie
irie version

The last command prints a line such as irie 0.1.0-dev+3f2a9c41d07e. The part after the + is different for every build.

If the terminal says it can’t find irie, add Go’s folder to your PATH, the list of folders a terminal looks in for programs. Put this line in your shell’s startup file, such as ~/.zshrc on a Mac or ~/.bashrc on Linux, then open a new terminal:

export PATH="$PATH:$(go env GOPATH)/bin"

Open it

irie

The first time, Irie sets itself up and opens in the same terminal window:

1. It makes its folders: ~/.local/state/irie for its own records, and ~/.local/share/irie for the folders agents work in. Only you can read them.
2. It writes a tmux settings file of its own. Your own tmux settings are never read or changed.
3. It starts a tmux of its own, named irie, apart from any tmux you already use. Inside it runs Irie’s core: the part that starts agents and keeps track of them.
4. The core draws the list on the left and the space for an agent on the right, and your terminal joins in.

Irie doesn’t make a settings file. Until you write one, it uses its defaults, which irie config print shows and Profiles and models lists.

Next time, irie joins the Irie that’s already running, with every agent where you left it. If you set the XDG_CONFIG_HOME, XDG_STATE_HOME or XDG_DATA_HOME folders, Irie uses them instead, on a Mac too.

Your first session shows what you’ll see, and what to type.

Inside tmux already?

Run inside another tmux, irie stops and says so. irie attach --nested opens it there anyway.

Without a window

irie up starts Irie in the background and comes straight back. irie ctl spawn does it for you, so a script can start agents with no window open: see Keys and commands.

Update it

cd irie
git pull
go install ./cmd/irie

The next irie sees the new build and restarts Irie’s own parts with it. Your agents keep running.

Keep irie where it is

Each running agent reports to Irie through irie, by the path it had when the agent started. Don’t move or delete it while agents run: their reports would fail, and Claude Code 2.1.295 and later then block their steps.

Building again in the same place, as above, is fine.

Remove it

To stop Irie and every agent in it, all at once:

tmux -L irie kill-server

Then delete the program and Irie’s folders:

rm "$(go env GOPATH)/bin/irie"
rm -rf ~/.config/irie ~/.local/state/irie ~/.local/share/irie

Look before you delete ~/.local/share/irie: its worktrees folder holds your agents’ work. Each worktree is also listed in its project, so remove them with git first, as Tasks, repos and worktrees shows.