cohix

Sign in Subscribe

Latest — 12 Jun 2026

A penny for your context?

Welcome back to the PrettySmart show after a week on Vancouver Island exploring what may be the most laid back part of Canada I've witnessed yet: Tofino, British Columbia. This week on the show we have several very different but long-awaited new pieces in awman: Experimental support

More issues

Workflows from issue to merged PR: awman v0.9 is out

In the last post, I announced that amux was becoming awman — the Agentic Workflow Manager. The rename reflected a shift in focus: the tool has grown from a terminal multiplexer for agents into something closer to a software development lifecycle pipeline tool, orchestrating the entire process from spec to merged

amux is becoming awman: an Agentic Workflow Manager for the entire software development lifecycle

When I started building amux earlier this year, the name stood for "agent multiplexer." The idea was simply "tmux, but for agents running in containers", which was immediately useful for me in my daily work. As my "agentic engineering" proficiency grew, the tool grew

Behold the miraculous self-improving codebase! ane v0.2 is out.

Since one of the core goals of ane is to allow code agents to explore, read, and edit source code with one-shot commands using chords and a simple CLI, this week I experimented with a self-improving codebase to work on ane from a code agent's point

Introducing ane: A language server-aware chord-based terminal code editor (for humans and agents)

TL;DR ane is a terminal code editor that combines a new chord grammar with language servers to allow both human developers and code agents to efficiently explore and edit source code - ane exec lets agents and scripts make precise reads and edits, while ane’s TUI editor lets developers

That refactor sucked, but amux v0.8 is out now

The past few weeks has been spent rebuilding amux's internals from scratch. The previous architecture was mostly “designed” by Claude and Codex across sixty-plus work items, and by the end it had become clear that the three frontends (CLI, TUI, headless) were each implementing business logic in

Code agents are bad at Software Architecture - for now

Hello from paternity leave, week three. There wasn’t an amux release last week because I've gotten so fed up with the patchwork design of the amux codebase I've decided to burn it all to the ground, more or less. Even top-end foundation models like

Manage your fleet of agent machines with amux v0.7

Hello and welcome to my first paternity leave blog post! I'm off work hanging with the family for 2 months, but I still plan to continue moving amux forwards while I'm off. With that, one of the reasons I can make so much progress each week

Multi-agent workflows, config commands, and true background yolo mode: amux v0.6

I've been using amux daily for all my personal dev projects the past few months, and though it is working incredibly well for my workflows, there were some codebase architecture issues I was ignoring in order to add all the feature ideas I had bouncing around in my

Code agents that actually get things done while you're asleep: amux v0.5

A few days ago was the first time I was actually able to kick off a complicated agent-based workflow before bed and have it completely finished when I got up the next morning. It's really quite impressive what these tools can accomplish these days. Using amux workflows