Stop babysitting the agents you already use
PEX is a local Windows companion that supervises existing coding-agent workflows. It connects to supported worker surfaces, keeps a durable goal and acceptance criteria, observes real evidence, asks a bounded Strands supervisor for a structured decision, applies local policy, and either stays quiet or sends one evidence-specific correction back to the same worker session.
The problem
Running multiple coding agents creates another job: remembering the original goal, checking every “done,” catching drift, rerunning verification, and typing “continue.” That repetitive, judgment-heavy supervision interrupts focused work.
How PEX helps
Attaches to OpenCode HTTP and isolated Codex App Server sessions without replacing the worker. Uses Strands Agents over six request-scoped, read-only evidence tools. Requires validated structured decisions such as NOOP or SEND_NUDGE. Keeps deterministic verification and local policy authoritative. Sends a correction to the same worker session only when cited evidence justifies it. Stays quiet when acceptance criteria are already satisfied. Supports Zen BYOK with a write-only key field and OS-vault storage. Ships exactly two desktop companions: Pex and Von. Provides an Inspector timeline for goals, evidence, decisions, delivery, and outcomes. Implements a locally tested AgentCore Runtime-compatible protocol; no AWS deployment is claimed.
Working proof
On exact RC4 product source, the OpenCode recovery case observed a missing required artifact, produced one evidence-grounded Strands correction, delivered it to the unchanged worker session, observed the exact repaired artifact, recorded helped:true, and finished with NOOP. A ten-case already-correct control produced ten model-backed NOOP decisions and zero follow-ups.
A separate exact-current Codex App Server pair showed the same behavior: one same-thread correction produced the exact requested result and was followed by NOOP; the already-correct control produced only NOOP and zero follow-ups. These are retained, source-bound behavioral proofs—not a comparative productivity claim.
Both paths used Zen BYOK with muse-spark-1.3-contributor-free through Strands and a bounded review limit. No paid fallback is bundled or silently selected. The public RC4 installer and evidence assets are available at https://github.com/josepha-mayo/pex/releases/tag/v0.1.0-rc4.
Safety and honest boundaries
Strands proposes actions; deterministic evidence and the local policy guard retain authority. Missing evidence, malformed output, timeouts, and rejected actions fail safely. Cursor is observe-only in this focused MVP. AgentCore is locally implemented and tested, not deployed. PexBench remains unfrozen, so we claim no productivity uplift or leaderboard rank.
Who it is for
PEX is for professionals who already use coding agents and want the leverage without becoming full-time dispatchers.
You keep the goal and dangerous approvals. PEX keeps the mechanical supervision quiet.
Log in or sign up for Devpost to join the conversation.