Roadmap

Irie’s eleven milestones as stones over two waves: 5 of 11 are done, and 2 are in progress. Stones 1, 2, 3, 6 and 10 are filled with a tick: done. Stones 4 and 7 are suns: in progress. Stones 5, 8, 9 and 11 are empty: planned. A flag marked v1 stands after stone 11. 5 of 11 milestones done 12346710 58911 v1
A tick is done, a sun is in progress, and an empty stone is planned. Done means added to main, the project’s main line of code.

Irie is built one milestone at a time, and version 1 is all eleven. The full plan is in the design document.

Version 1

  1. Launch and look Done

    Open Irie and type a task, and Claude Code starts on it. Press Enter on its row to watch it work, and close the window without stopping it.

  2. Live states Done

    Rows show who is working, who needs you, who is done and which task couldn’t start. Most of it comes from Claude Code’s hooks, small commands it runs as it works.

  3. Repos, worktrees, any task size, profiles Done

    Name a project, or repo, with @, and its agent gets a worktree of its own: a second working copy, so agents keep out of each other’s way.

    Pick the agent and the AI model for each task with + and a profile, a recipe you name. Any agent that runs in a terminal, the window where you type commands, can be started.

    Tasks of any size can be pasted in.

  4. Manage the list In progress

    Rename a session, close it and reopen it later, and drag the rows into the order you want.

    Parking rows out of the way, jumping to one by typing, and undo and redo are still to come.

  5. Pause at the next tool call Planned

    Pause an agent at its next tool call, a step such as running a command or editing a file. Let it go when you’re ready, and it’s told how long it waited.

  6. Freeze Done

    Stop an agent and everything it started at once, or every agent. Thaw it and it carries on; if it was busy, it’s told it was frozen.

  7. Priority and notes In progress

    Promote a task: it moves to the top, and its agent gets the computer first.

    Notes to an agent, which it reads at its next step, are still to come.

  8. Subagent panes Planned

    Some agents start helpers, called subagents, for parts of a task. Each gets a live view, or pane, of its own, and you can pause one alone.

  9. The Irie window in Ghostty, and Irie.app Planned

    On a Mac, find Irie in Spotlight, the Mac’s search, and open it like any app. It opens in a window of Ghostty, a free terminal app, and opening it again brings that window forward.

  10. Local models, cost and routing Done

    Run an agent on a model on your own computer, through a model server Irie runs for you. Irie won’t start an agent on a model without room for its work, and says how to fix it.

    Every session shows what it costs. A task with no profile goes to the cheapest one that does such tasks well, and hard work stays on the strongest model.

  11. Control-mode events and real-Claude smoke tests Planned

    tmux, which keeps the agents running, tells Irie about changes at once instead of being asked every second. A set of tests runs against the real Claude Code.

Built beside the milestones

Four colour themes are on their way too: see Themes.

After version 1

  1. Fuller support for more agents: Codex CLI first, then opencode, Gemini CLI and pi, then goose, hermes-agent, Amp and crush.
  2. Agents working together more, such as a second opinion from another company’s model before anything reaches you.
  3. Popping an agent out into its own Ghostty tab.
  4. Seeing which agents work on the same project and how near each is to the most its model can hold in mind, and a focus mode that pauses the rest.
  5. Costs for agents other than Claude Code, clearing out old worktrees, and a desktop alert when an agent needs you.