Making this multi-player + creating the right representation to collaborate with agents is in my opinion the next bottlenecks. I wrote a small article about my thoughts there https://x.com/mmabrouk_/status/2010803911486292154
[1] https://steve-yegge.medium.com/the-future-of-coding-agents-e...
I've been really enjoying how OpenCode is so extensible, how you can make great plugins that can for example read the session.idle event & then go do whatever they want. That does require dropping in some config asking for the plugin, which takes some effort & requires a restart (but your session will be right there & you can continue). It's technically elegant imo, and nice that there is the extensibility.
But hard to beat using screen as a framebuffer & just reading it out, for doing absolutely whatever it is you could possibly want to do! For example you can also detect permissions prompts, which I don't believe there is an event for!
And what's really fascinating isn't that multiple people have built the same thing is just how convergent all the ideas are. This makes a heap of sense given that they are all vibe-coded and using similar libraries. It's just very real when you see it right in front of your face like this.
I think there's a heap of really interesting stuff when you start linking into hooks which can also create tmux splits and really make the agent the center of an ide which seems like this is on the way to.
I wonder if it would be more ergonomic to connect to the aoe window on my phone for when I have more then one claude code session to keep track of. I'm not against switching the zellij part to tmux.
Steps to reproduce the bug that broke my tmux:
1. `aoe add .`
2. `aoe`
3. Attach to the session that was added
4. Close that pane with `<Prefix> x` then `y`
5. Tmux closes down
6. Attempt to reattach to any session within tmux: `open terminal failed: not a terminal`
7. `tmux kill-server` is the only viable option, losing all my sessions
If only we could have a clean API to programmatically control agents... The best UI is no UI
I am seeing a lot of development working around the shitty experience that is being stuck in a terribly slow cli program, nothing against this particular project
The best (for me) of these that I’ve tried so far is conductor.build
They have a different UI orientation, and it’s more locked into Claude code, but it might be good inspiration for your future plans. They get the git worktree setup and teardown and managing dev servers part of it right IMO.
Regarding feedback on whether sandboxing would be useful, yes, please! Including something like Docker sandboxes would make isolating the agent env’s much less of a hassle.
As an aside, I’m curious how others are handling this now… Mostly just creating dedicated user accounts?
>relies on tmux for security how is it more secure than not using it?