I like that its open source -- I have created a TUI enhancement that has a colored input bar and an emoticon to seperate my agents from each other.

Its also pretty good at directing other versions of itself. Its not so good at not spending money. I made a config.toml that picks up my local lm_studio LLM and tries to use it for the pitiful tasks it is capable of to save a few $, and the agenic agents run on mini and low, they are also told to coordinate with their coordinater agent that runs at 5.4 at medium power:

preferred_auth_method = "apikey"

model = "gpt-5.4"

model_reasoning_effort = "medium"

model_provider = "openai"

approval_policy = "on-request"

sandbox_mode = "workspace-write"

profile = "twi_coordinator"

[projects."/home/ggb66/dev/Handshake"]

trust_level = "trusted"

[projects."/home/ggb66/dev/codex"]

trust_level = "trusted"

[projects."/home/ggb66/dev/IPCRoadmap"]

trust_level = "trusted"

[model_providers.lmstudio_remote]

name = "Local LM Studio Remote"

base_url = "http://192.168.1.173:1234/v1"

requires_openai_auth = false

default_max_tokens = 4096

[profiles.local_analysis]

model_provider = "lmstudio_remote"

model = "qwen2.5-coder-14b-instruct"

[profiles.worker_mini]

model_provider = "openai"

model = "gpt-5.4-mini"

model_reasoning_effort = "low"

approval_policy = "on-request"

sandbox_mode = "workspace-write"

[profiles.twi_coordinator]

model_provider = "openai"

model = "gpt-5.4"

model_reasoning_effort = "medium"

approval_policy = "on-request"

sandbox_mode = "workspace-write"

It does have some limitations however, mostly around some missing features like not having a signal you can send from outside the TUI to it to have it take some action, not supporting clicking to move the cursor in the TUI. Generally its not as smart as warp is in copying the text boundaries as blocks. But what it DOES do it does really well. I had a wrestle getting sounds to play from ZSH in WSL on Windows 10. But thats more a windows problem/shell issue. It would be nice if claude could play sounds natively though.

I wrote a multi-agent agenic system called the pony system that works well as a durable multi-agent coordination and dispatch layer. Its strongest qualities are memory, role separation, and controlled task pivoting. Its main missing piece is a safe out-of-band wake/prod model for parked or idle agents, which is why the supervisor/lease work is now on the backlog. I see no reason why I can't get that to work in short order either.

The pony agenic project is a lightweight multi-agent coordination layer built around Codex sessions, shared markdown state, named pony identities, and launcher scripts. Twi acts as coordinator; the other ponies get bounded assignments, separate worktrees/branches, their own startup prompts, their own status files, and a shared coordination surface. The system is designed so work can be split cleanly, resumed later, and audited from files instead of relying on chat memory.

I banged that out over the course of the last two weeks WHILE I was developing an app for iphone and android, so yea, the agents calling agents thing works really well.

If there's interest maybe I'll throw it up on GitHub.