LOCAL AGENT EXECUTION BOUNDARY

Delegate.Withoutletting go.

An execution boundary between your AI client and its tools. Fix what can be called. Isolate execution. Keep results and evidence. All through a local, controlled entry.

Follow progress on XAsk about Waypost

PRIVATE VERIFICATION & DOGFOOD / NOT RELEASED

01 / THE EXECUTION BOUNDARY
ROUTE DOCTORInspect before launch
WaypostTools admitted at startup
AI clientThe caller
MCP backendOne execution destination
Admitted calls
Results & evidence return
Isolated generation
01 / CLIENTAI clientThe caller
02 / WAYPOSTTools admitted at startupRoute Doctor · Inspect before launch
03 / BACKENDMCP backend × 1Isolated generation

↑ Results & evidence returnResult → Receipt → AI client

FIG. 01A diagram of the current execution route. Not a product interface.
LINUX / WSL2LOCAL STDIOONE MCP BACKENDWhere we are

01 / WHY A BOUNDARY

Connected doesn’tmean controlled.

A visible tool is not a guarantee of safe execution. Where an agent’s intent becomes an effect in the world, there needs to be a boundary.

01

Can a new tool quietly gain access?

One startup inventory defines admission.

02

Where does execution cleanup stop?

Handle only the runtime you own.

03

What happened, and what remains?

One route from the call to its evidence.

02 / ONE CONNECTED ROUTE

Before the call.Through the return.

Waypost doesn’t manage how an AI thinks. It manages the route through which tools execute. Four connected contracts make up the working core.

  1. 01

    Decision

    Check the execution boundary

    Admit calls against an immutable inventory captured at startup.

  2. 02

    Invocation

    Dispatch the admitted tool

    Route to one MCP backend in its own isolated generation.

  3. 03

    Result

    Receive the outcome

    Bound cancellation and deadlines. Handle public-safe results.

  4. 04

    Receipt

    Keep execution evidence

    Connect decision, invocation, and result. Not a guarantee of parent-task completion.

The working core’s route. Not a human approval interface or a guarantee of parent-task completion.

03 / IMPLEMENTED, NOT RELEASED

A small, explicit execution surface.

Linux / WSL2 · local stdio · one MCP backend. This is the scope of the working core today.

01

Inspect before launch

Route Doctor checks route configuration and required artifacts before the backend starts. Know the route before execution begins.

02

What is listed is what can run

The startup tool inventory is immutable. Tools added mid-session do not automatically gain permission to execute.

03

Isolate execution. Keep evidence.

Separate runtime resources by generation. Clean up by identity, with public-facing results designed to exclude sensitive data.

Explore the technical scope
MCP entry
Newline-delimited JSON-RPC over local stdio: initialize, notifications/initialized, ping, tools/list, tools/call. Protocols: 2024-11-05 / 2025-03-26 / 2025-06-18.
Artifact admission
Check path, owner, mode, inode, size, and hash. Validated artifacts and executables enter the route; later source-file changes cannot enter the running route.
Runtime & results
Separate home, data, socket, PID, and event DB. Identity-based cleanup; bounded cancellation and deadlines. Public-safe results are designed to exclude prompts, credentials, raw payloads, and private paths.
Connector diagnostics
Initialize and tools/list record success, failure, stage, and failure category in the current process. Not persistent, system-wide health monitoring.

04 / FIELD NOTES

The boundary works.The product comes next.

PUBLIC STATUS

Based on the supplied public progress dated 2026-09-05. Private-main gate results are developer-reported, not independently rerun for this landing page.

Follow progress on X
REPORTED

Private main passed its gates

Session gate, PR CI, and main CI reported passed. Latest-main validation is distinct from promotion into daily use.

OBSERVED

Different clients. Different evidence.

Official TypeScript MCP SDK passed connect / list / call / ping. Claude Code and Gemini CLI only observed Connected. Hatch is in daily dogfood.

PENDING

The global promotion gap

The active global launcher is older than validated main and route config. Codex is configured, but its actual runtime remains UNKNOWN.

05 / THE ROAD AHEAD

The next stretch of the route.

NEXT TO VERIFY

Latest main, into daily use.

Promote the global launcher and connect the evidence chain. Verify the actual Codex runtime.

FUTURE DIRECTION / NOT IMPLEMENTED

From execution to work completed.

Define parent-task lifecycle and Assurance Profiles. Then build the human-facing UI and distribution layer.

AUTONOMY WITH BOUNDARIES.

Building autonomy.With boundaries.

What works. What remains unknown. Follow the development route as it takes shape.

Follow progress on XAsk about Waypost