Hacker News: yoanwaidev

New comment by yoanwaidev in "Claude Fable 5.1 and Claude Mythos 5.1"

yoanwaidev — Tue, 01 Sep 2026 21:14:42 +0000

as an anthropic employee, do you trust the benchmarks?

New comment by yoanwaidev in "Claude Fable 5.1 and Claude Mythos 5.1"

yoanwaidev — Tue, 01 Sep 2026 21:13:54 +0000

Almost finished my weekly limit today! I am more excited from the usage reset!

New comment by yoanwaidev in "Launch HN: Hoplite (YC S26) – Effortlessly deploy cloud coding agents"

yoanwaidev — Mon, 03 Aug 2026 22:18:07 +0000

Same instinct locally with git worktrees: one agent per worktree so they do not thrash the same checkout. Cloud VMs buy isolation and scale; worktrees buy cheap isolation when you already have a machine. I end up using both patterns depending on whether the bottleneck is compute or just not stepping on each other.

Reading agent status out of Claude Code's hooks

yoanwaidev — Mon, 03 Aug 2026 14:42:53 +0000

Article URL: https://agent-manager.dev/writing/claude-code-hooks/

Comments URL: https://news.ycombinator.com/item?id=49156473

Points: 1

# Comments: 0

New comment by yoanwaidev in "Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode"

yoanwaidev — Sat, 01 Aug 2026 02:31:44 +0000

You're not, and this won't convert you. The reason I stay in a terminal is that the agents already live in one, so a TUI is a view over what's running rather than a second place things live. If your agent already runs in a GUI, that argument doesn't apply to you.

New comment by yoanwaidev in "Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode"

yoanwaidev — Sat, 01 Aug 2026 02:31:35 +0000

Different scope, as far as I can tell from their site: they describe a multiplexer for all work, spanning remote hosts, sandboxes, CI, production systems and shared terminals. This is a Go binary that drives tmux on the machine you're already on, and every session it creates is an ordinary tmux session you can attach to without it. Much smaller bet, and it stops where tmux stops.

New comment by yoanwaidev in "Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode"

yoanwaidev — Thu, 30 Jul 2026 21:13:01 +0000

To be clear on the GUI point, since my last reply here answered a different question: this is a terminal tool and it won't convert you. The reason I stay in one is that the agents already live in terminals, so the manager is a view over what's running rather than a second place things live.

New comment by yoanwaidev in "Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode"

yoanwaidev — Thu, 30 Jul 2026 15:29:36 +0000

herdr's a whole runtime, own multiplexer, plugins, socket api. mine sits on tmux and doesn't try to replace it, sessions stay normal tmux sessions.

overlap on the status sidebar is real. two things I lean on that I couldn't find a key for over there: space on a blocked agent types the answer into its pane without attaching, and ctrl+r opens its repo as full-file diffs where a comment on a line goes back to that agent as a prompt. herdr's socket api can push text into a pane, so the first one is scriptable at least. correct me if I missed something.

mouse and windows, herdr's ahead.

New comment by yoanwaidev in "Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode"

yoanwaidev — Thu, 30 Jul 2026 15:29:28 +0000

agent-deck was the first one I actually tried to adopt, landed a couple of commits in it. wanted it to be the one.

what I kept missing was answering an agent without attaching to it. so space on a blocked one, type, enter, and it lands in that pane. on a project row it spawns a new agent already working on what you typed. the other half is review, ctrl+r opens what it changed as whole files with the diff tinted, c comments a line, C sends the notes into the pane.

deck does plenty I don't, worktrees, cost, forking. different bets.

New comment by yoanwaidev in "Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode"

yoanwaidev — Thu, 30 Jul 2026 09:34:40 +0000

I run three or four coding agents at once and the part that eats my time isn't the coding, it's that I can't tell what state any of them is in without tabbing through every terminal. One of them is usually sitting on a permission prompt I never saw.

agent-manager is a Go binary on top of tmux. No config file, no daemon, no server. Every agent shows up in one list with a live status, grouped by the project it's running in. Status comes from reading the pane, so adding a CLI is a few lines of regex in a toml file rather than an integration.

The keystroke I use constantly is space: press it on an agent, type, enter, and the prompt lands in that agent's pane without attaching. Press it on a project row and you get a new agent already working on what you typed. ctrl+r opens what an agent changed as whole files with the diff highlighted, and a comment left on a line is sent back to that agent as a prompt.

Sessions are plain tmux sessions, so quitting the manager leaves everything running and v reattaches a session with its conversation intact.

I built it for four agents and most days I use it with one. Still rough in places, and I'd like to hear what breaks for you.

Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

yoanwaidev — Thu, 30 Jul 2026 09:34:27 +0000

Article URL: https://github.com/YoanWai/agent-manager

Comments URL: https://news.ycombinator.com/item?id=49107749

Points: 98

# Comments: 80