Waygent

Waygent is a local agent runtime for running, inspecting, recovering, and applying multi-agent implementation work. It owns scheduling, worktrees, provider adapters, verification, recovery, apply readiness, and durable event emission.

Lens is the TypeScript observability and inspection path inside Waygent. agentlens.event.v3 remains the event contract label, but the legacy Python components/agentlens/ tree has been removed from the product runtime. KWS executor skills remain in this repository as local executor contracts, but they are not the Waygent product runtime.

Project Map

apps/                  CLI, API, and console surfaces
packages/              TypeScript runtime packages
native/kernel/         Rust execution kernel boundary
skills/                Waygent and KWS executor skill definitions
docs/                  Architecture, operations, contracts, and migration notes

Quick Start

Install dependencies and run the default local checks:

bun install
bun run check
bun run platform:demo

Useful Waygent commands:

waygent run --latest
waygent status --last
waygent inspect --run <run_id> --json
waygent explain --last
waygent resume --last
waygent apply --run <run_id>

Live Codex and Claude provider checks are opt-in because they require installed and authenticated local CLIs:

WAYGENT_LIVE_PROVIDER=codex bun run waygent:live-smoke
WAYGENT_LIVE_PROVIDER=claude bun run waygent:live-smoke

Architecture

Waygent uses a Bun/TypeScript control plane, a Rust execution kernel, and filesystem event journals as replayable evidence. Runtime decisions come from durable state and TypeScript projections, not from chat context.

• Runtime overview: docs/architecture/waygent.md
• Documentation index: docs/README.md
• Getting started: docs/getting-started.md
• Event contracts: docs/contracts/events.md
• Operations: docs/operations/waygent.md
• Waygent skill: skills/waygent/README.md

Graphify Repository Map

Graphify is an approved development and documentation-audit tool for this repository. Use it to build a queryable repo map, find cross-file relationships, and check whether documentation still matches the current Waygent and Lens structure.

Refresh the local graph after meaningful code or documentation structure changes:

graphify update .

Query the graph when exploring cross-cutting architecture:

graphify query "how does Waygent decide apply readiness?"
graphify path "ProviderResult" "Lens"
graphify explain "safe wave"

Committed Graphify outputs may include graphify-out/graph.json, graphify-out/GRAPH_REPORT.md, and, for smaller graphs, graphify-out/graph.html. Large graphs may skip the HTML view; in that case use GRAPH_REPORT.md, graph.json, and graphify query. Local-only Graphify files such as manifest.json, cost.json, cache/, and machine-path metadata stay ignored. Graphify is not a product runtime dependency and must not replace the canonical contracts under docs/, packages/, native/, and skills/.

Working Rules

Read AGENTS.md before changing this checkout. For complex plans, use PLANS.md. For reviews, use code_review.md.

Keep runtime state out of git, including .agentlens/, .claude/, .codex-orchestrator/, .orchestrator/, .superpowers/, .waygent/, node_modules/, build outputs, caches, and local virtualenvs.