Back to work
Technical project · 2026 · In progress

Hermesday

An agent team I built in Hermes, cast from the characters of Wednesday. Wednesday runs the show as the orchestrator, while Thing, Enid, and Eugene do the work.

Duotone still in ultramarine: Eugene in glasses on the left, Wednesday with braids at center, Enid smiling on the right, and Thing the disembodied hand resting on Wednesday's shoulder.
Pictured: Eugene, Wednesday, Enid, and Thing.

WThe cast

  • Orchestrator

    Wednesday

    Nevermore’s sharpest mind, who trusts nothing she hasn’t checked herself.

    Reads the codebase, decides the design, and writes each worker a precise brief. When a worker says it’s done, Wednesday re-runs the checks herself before anything is merged.

  • Worker

    Thing

    The family’s ever-helpful disembodied hand.

    Making the outro text of each audio readback configurable from the admin screen.

  • Worker

    Enid

    Wednesday’s roommate and sunny opposite.

    Storing the pilot’s start date properly instead of reading it from a hard-coded call.

  • Worker

    Eugene

    Founder of the Nevermore beekeeping club.

    A retry queue, so audio that fails to generate gets tried again later.

Their first assignments are on a Drupal module that turns NJIT news articles into audio.

HHow the team works

One orchestrator, three workers

Wednesday plans and verifies. Thing, Enid, and Eugene are identical workers; each one owns a single workstream at a time.

Separate workspaces

Every worker edits its own git worktree, so their changes can never collide. Wednesday merges them one by one.

Runs locally

The workers run Qwen on a Mac Studio on our own network, so university content never leaves it.

What’s next

Hermesday is just getting started. Next I want to give the team more of the work, and see how much Wednesday can trust them with.

Stack
HermesQwen (MLX)Mac StudioGit worktreesDrupal / PHP