WhoBuilt

Ten Agents Waiting for Input: AI Coding and Hermes

Oct 12, 2026· 12 min· 554 views·Watch on YouTube

Speaker

Tzvetan Mikov, a React Native community member who works on Hermes, talks with a Callstack host at AgentCon 2026 about AI coding workflows, engine optimization, and the future of software work.

Working across multiple agents

Mikov says slow models have pushed him to work on several tasks in parallel, sometimes five at once. The host describes managing ten agents from a phone and choosing which one to answer based on how easy its question seems. Both find the resulting context switching painful.

AI can handle low-level engine work

Mikov says agents understand JavaScript engines, JITs, assembly languages, and optimization techniques. They do better on focused tasks with some structure, while asking a model to design something huge can send it off course. He values their persistence on boring tasks.

Capability brings mixed feelings

Mikov describes both enjoying quick AI-assisted projects and feeling uneasy when they require little expertise. He thinks job loss is a more immediate concern than AI deliberately harming people. Asked whether a nonexpert could prompt an agent to build a JavaScript engine for inexpensive watches, he says that may already be possible.

Faster Hermes releases, with review

Mikov says a new Hermes release is coming soon and introduces Hermes X, a channel for prereleases that avoids waiting a year for official releases. He says he typically uses one agent per task, writes careful specifications, iterates between Codex and Claude, and checks tests closely.

Humans still choose what matters

Mikov says he is still adding value to agents, though he was more needed the previous year as the tools have improved. He sees humans deciding what is valuable and useful as a continuing role, but wonders how many people will be needed. The conversation closes by returning to the burden of orchestrating agents and switching contexts.

Takeaways

  • Use focused tasks and provide structure when asking agents to work on complex engineering problems.
  • Treat model output as something to review: Mikov iterates between Codex and Claude and checks tests closely.
  • Account for the attention cost of parallel agents, including time spent answering questions and switching contexts.
  • As agents take on more implementation work, clarify who decides which problems are worth solving.
  • Faster prereleases can help teams ship sooner, as Hermes X is intended to do.

Mentioned in this talk

Search inside this talk

What was claimed 4

  • feature
    subagents: Can work on specialized tasks such as low-level engine optimization when given structure; large design tasks may go off track.
    “if I give it a little bit of structure, it does very well with low-level engine optimization”
    YouTube
    Unverified1 source· Talk
  • feature
    Hermes Agent: Hermes X will publish prereleases.
    “there will be something called Hermes X, where I'll publish prereleases”
    YouTube
    Unverified1 source· Talk
  • uses
    “I usually iterate between Codex and Claude, reviewing them.”
    YouTube
    Unverified1 source· Talk
  • uses
    “I usually iterate between Codex and Claude, reviewing them.”
    YouTube
    Unverified1 source· Talk

Related talks

Ten Agents Waiting for Input: AI Coding and Hermes, Tzvetan Mikov · WhoBuilt