Frontend and accessibility engineer

Tony Martinez

I run a fleet of AI agents that build and ship my projects, end to end.

Nine years of frontend and accessibility work, now pointed at pi-durable-local, a small software factory where durable agent sessions take work from idea to merged PR under budgets and merge gates.

How a change ships
  1. GoalA loop wakes with a budget and a brief
  2. PRThe agent opens it from a template
  3. ReviewChecks run, then an independent review
  4. MergeGated: low and medium risk only

Selected work

Projects I am building. Each card opens the live version; some also link to source code.

How I build

The projects above come out of pi-durable-local. One daemon owns the state; everything else goes through it. This is the path a change takes.

  1. Goal

    Generals set it

    Tony and Claude Code sessions set goals and answer escalations. Cheap Sonnet and Haiku sessions are the workforce.

  2. Session

    Durable sessions

    Long-running agent conversations in a bubblewrap sandbox with no credentials. They survive restarts and resume from the last committed step.

  3. Loop

    Loops under budget

    A session wakes on an interval within a dollar budget and an iteration cap. A gate decides in code whether a tick is worth running.

  4. Gates

    PR template and CI

    The daemon opens PRs from a template. A deterministic state machine, pr_tick, picks the one next action.

  5. Review

    Independent review

    A separate model reads the diff for the exact head commit. Risky or one-way changes park for a human.

  6. Merge

    Pinned squash merge

    Low and medium risk PRs that pass every gate merge, pinned to the checked commit.

Agents never hold GitHub credentials, and an audit log records every decision.Read the case study.

Approach

Contact

Want to talk about frontend, accessibility or agent tooling? Email is best.