<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Codeg on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/codeg/</link><description>Recent content in Codeg on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/codeg/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing AI agents in the terminal: I ended up keeping herdr — a head-to-head review of four managers</title><link>https://blog.lynxflow.co/en/posts/terminal-agent-manager-comparison-2026/</link><pubDate>Tue, 11 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/terminal-agent-manager-comparison-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/terminal-agent-manager-comparison-2026.png" alt="Featured image of post Managing AI agents in the terminal: I ended up keeping herdr — a head-to-head review of four managers" /&gt;Prologue: First, Getting Tangled Up by My Own Pile of AI Agents My recent workflow has turned into this: several AI agents running in the terminal at the same time—Claude Code modifying one project, Codex doing research in another, and yet another one generating content. Multiple projects in parallel, with the terminal as the main arena.
Then came the problem: I had no idea which agent was stuck, what it was waiting for, or whether it had finished. I tried tmux, used it for a while, then dropped</description></item></channel></rss>