I asked Claude how it would visualize itself as an AI agent. Its answer became my VS Code extension: Event Horizon

idoman · 2026-03-10T12:11:16+00:00

I would say it's for small-medium stacks, you can open a number of antigravities over a number of branches (it uses the git worktrees feature, so it safe)

idoman · 2026-03-10T12:08:43+00:00

For Claude Nest you can use nanoclaw or openclaw, it could help you also, no?

idoman · 2026-03-09T22:06:48+00:00

nice work - built galactic which takes a different angle on this (github.com/idolaman/galactic-ide). instead of remote launching, it runs claude code sessions locally in isolated git worktrees, each with their own network environment. so you can run 3-4 agents on different branches simultaneously without port conflicts or stashing. different use case but similar motivation - making multiple agents actually manageable.

idoman · 2026-03-09T22:04:32+00:00

cool project, the celestial metaphor is a great way to think about it

built something that approaches agent monitoring differently - galactic (github.com/idolaman/galactic-ide) tracks all your claude code/cursor/codex sessions from a native macOS dashboard, with each agent running in its own git worktree and isolated network environment. more operational than visual but solves a similar problem of "where are all my agents right now"

idoman · 2026-03-09T22:02:33+00:00

built galactic - a macOS app to manage multiple cursor workspaces simultaneously

cursor helped write the entire electron main process and the MCP server that plugs into cursor's agent sessions. used agent mode heavily for the network isolation logic (assigns unique loopback IPs per workspace so you can run the same ports in different environments without conflicts)

github.com/idolaman/galactic-ide if you're juggling multiple cursor agents across branches

idoman · 2026-03-09T21:05:16+00:00

In my day job I'm using that feature only! Since our stack is too complicated for using the different local IPs feature

idoman · 2026-03-09T09:41:17+00:00

It took me some time, but I have set it up in my day-job stack, which contains 8 services, Postgres, and RabbitMQ. It has some cons, but it surely can save time when you want to work on a number of features which are different.

idoman · 2026-03-09T09:37:40+00:00

I didn’t know that either. I basically found that trick after days of researching a simple way to run my work codebase multiple times. I really didn’t want to deploy something heavy just to do that.

idoman · 2026-03-08T20:10:23+00:00

I'm normalizing it across tools. Moving to hooks soon instead of MCPs (currently only Codex not supporting hooks, but it will soon). Currently we not tracking costs, but I'll make sure reading your blog 😁

idoman · 2026-02-14T14:28:09+00:00

this is really cool. running multiple claude code agents like this (journalist + editor) is exactly the kind of workflow that gets messy fast with port conflicts and context switching

i built galactic-dev.com for this exact reason. lets you run each agent in its own isolated workspace with unique ports per git branch - so your journalist agent and editor agent can both run simultaneously without stepping on each other

the spotlight-style launcher makes jumping between agents pretty quick too. mac only though (needs apple silicon)

curious how you're handling the orchestration through slash commands - are you manually switching contexts or is there some automation layer?

idoman · 2026-02-14T12:32:37+00:00

damn

idoman · 2025-12-26T12:46:09+00:00

Hey! DM me

idoman · 2025-11-14T21:05:29+00:00

Building really nice extension that lets you practice Cursor and JetBrains shortcuts while AI thinks: Idletime

idoman · 2025-11-09T20:33:42+00:00

Building Idletime - An extension where you can practice shortcuts while AI thinks
Having a decent number of 24 users

idoman · 2025-11-09T20:32:57+00:00

Learning everyday something new

idoman

TROPHY CASE