A few weeks in, we’ve already shipped eight beta releases for @Xirp, so here’s a quick update on what’s changed.
One of the problems we talked about at launch was coordination: engineers running multiple coding agents across different projects, branches, and repos, each with its own setup and context.
Since then, we’ve been hearing from engineers and technical leads using Xirp in their own workflows, and we’ve been closing some of those gaps they’ve flagged.
We’ve recently added Cursor alongside Claude Code, Codex, and Gemini. Sessions can be grouped by worktree, so it’s easier to see which project and branch each one belongs to. And when a session spans multiple projects, each agent now looks for the correct instruction files for its own project.
Agent setup and context are more consistent now, too. Codex gets the same launch context as Claude sessions, and Codex sessions launched from Portal now receive the workspace tools and project context they were previously missing.
Claude Code and Codex now use their vendors’ official installers, and the new Doctor page checks your coding agents, tmux, and agent hooks, then shows you what failed and how to fix it.
We’ve also fixed issues around sessions starting in the wrong directory, Codex sending false waiting notifications, startup failures, and other reliability gaps that get in the way when you’re running multiple agents in parallel.
All of these changes are focused on the same problem: When you’re running more agents across more projects and tools, Xirp should make it easier to know where each session is running, what context it has, and when it actually needs your attention.
That’s what we’re continuing to work on with every change we ship for Xirp. Keep the feedback coming.
See all the changes here: https://lnkd.in/dcCQysAh