22 ms·
Show HN: Seshions – Orchestrate multi-agent coding agents from one terminal
I run 3-5 AI coding agents in parallel (Claude Code, Codex, Gemini) and the bottleneck was never the agents, it was managing them. Switching panes, losing track of which agent had which role, re-typing the same setup every time.
Seshions is a terminal UI that gives you one dashboard to launch, route prompts to, and monitor parallel coding agents via tmux. What makes it different from other tmux session managers:
- Blueprints: define a multi-agent team once (planner, builder, reviewer, etc.) and launch the whole group in one action
- Orchestration: dispatch a prompt to a single role, or broadcast to every agent in a group — from one composer
- Works across tools: Claude Code, Codex, Gemini CLI, OpenCode, or any custom shell command
- One command: npx seshions@latest
Demo + repo: https://github.com/danhergir/seshions https://github.com/danhergir/seshions
Built with Bun + TypeScript. I would love to get feedback on the UX and what workflows you'd want supported.
- danhergir 7mo agoHey, I am more than happy to answer questions. Please try Blueprints with Seshions, I used to have to spawn the same 4-agent setup every time manually. Now it's just one keypress.
- jlongo78 7mo ago[flagged]
- danhergir 7mo agocurrently what i do is setting up a group for a set of sessions/agents, once this is done, i'll name the group based on the task/activity which is being completed. by doing this i can move between several tasks, see the current status of each session, and even use Blueprints to send a message to a certain group of sessions/agents
- jlongo78 7mo ago[flagged]
- danhergir 7mo agogrouping groups is not an actual feature since it can get you to have nested tasks eventually overcomplicating your workflow. personally, i am not attracted to having more than 6-7 sessions since i like to take good care of the context. what's your workflow?
- jlongo78 7mo ago[flagged]
- parsak 7mo agoCool concept with the Blueprints system - defining agent teams declaratively is a nice touch. I'm building something adjacent called Pane (https://runpane.com https://runpane.com) that comes at it from the terminal management side rather than orchestration. Each pane is one feature with its own git worktree + N terminals, and worktree creation/cleanup is fully automated. The idea is you shouldn't have to think about the git or tmux layer at all. Main difference from Seshions is Pane is a standalone desktop app rather than sitting on top of tmux, so it owns the terminal emulator directly. Tradeoff is less composability with existing tmux workflows, but the PTY handling and cross-platform support (Windows included) got way simpler. Open source (AGPL-3.0): https://github.com/Dcouple-Inc/Pane https://github.com/Dcouple-Inc/Pane