Hi DEV — I'm the maker of Agent Island, a free and open-source status companion for Claude Code and Codex.
I built it around a simple problem: coding agents often finish, need input, or hit an error in another window while you're focused elsewhere. The work may be done, but the handoff is easy to miss.
Agent Island makes those session states visible in one place. It shows which agent and project need attention, sends a notification, and can play a sound when it is your turn. The product is local-first, and session state stays on the machine.
I'm here to share practical notes from building and shipping a cross-platform developer tool, including:
- designing reliable state detection for long-running agent sessions
- building useful notifications without creating noise
- keeping the product local-first
- shipping for macOS and Windows
- learning what developers actually need from agent observability
The project is available at agent-island.dev.
I'm especially interested in how other developers manage several agent sessions at once. What part of that workflow creates the most friction for you?
Top comments (0)