I built speedmux to make parallel agent workflows manageable from one terminal interface.
At a high level, the architecture is:
1. one terminal multiplexer process managing multiple concurrent sessions
2. per-session isolation so each agent/task can run independently
3. a persistent sidebar that tracks session state/activity without switching context
4. rendering/performance path powered by libghostty, which keeps interaction latency low even with multiple active sessions
It’s written in Go, and a lot of it was vibe-coded with Codex.
Good concept and congrats on the launch. My feedback is I don't see why I would move my conversations( and convincing all my friends) from existing apps like iMessage, Discord, Slack etc to new app just coz of a calendar feature. Who is the target customer for this service?
Discord, Slack and iMessage have many apps that can be used to schedule events. I think it would make more sense if this a SaaS offering where I could use this in other platforms as an app or a bot.
At a high level, the architecture is:
1. one terminal multiplexer process managing multiple concurrent sessions 2. per-session isolation so each agent/task can run independently 3. a persistent sidebar that tracks session state/activity without switching context 4. rendering/performance path powered by libghostty, which keeps interaction latency low even with multiple active sessions
It’s written in Go, and a lot of it was vibe-coded with Codex.