Skip to main content

Packages

One page per workspace package, generated from its entry point. @svatah/yam is the command line; every other package is @svatah/yam-<name>.

PackageExportsWhat it is
@svatah/yam67The yam CLI and MCP server
@svatah/yam-adapter-appium43Appium adapter: Android Chrome and native
@svatah/yam-adapter-atspi28Linux AT-SPI accessibility adapter
@svatah/yam-adapter-ax54macOS Accessibility adapter: the Yam agent surface over AXUIElement
@svatah/yam-adapter-bidi40WebDriver BiDi adapter (independence proof)
@svatah/yam-adapter-http14HTTP/API adapter
@svatah/yam-adapter-playwright41Default web adapter: AgentSurface on Playwright
@svatah/yam-adapter-process12Process and pseudo-terminal adapter
@svatah/yam-adapter-uia40Windows UI Automation adapter: the Yam agent surface over UIAutomationClient
@svatah/yam-bindings53Bindings store, context hash, resolver, synthesis, fingerprint, relocalization
@svatah/yam-bindings-cli28The yam-bindings command line: bindings, heal, surface conform and the healing eval for module (a)
@svatah/yam-compiler51Compiler tiers, validation, lint and plan writer
@svatah/yam-conformance17Surface and runtime conformance suites
@svatah/yam-contract43The surface operation catalogue and the contract fingerprint every client agrees on
@svatah/yam-gateway44Model gateway: local and frontier backends, caching, redaction, provenance
@svatah/yam-healer44Failure selection, model-free repair, verification and diff
@svatah/yam-host-playwright22Playwright Test host for Yam flows: the yam fixture, generated specs and the results reporter
@svatah/yam-mcp10The Yam MCP server: surface and operation tools over stdio or Streamable HTTP
@svatah/yam-migrate34v1/v2 to v3 migration and prototype database import
@svatah/yam-playwright-test23The bind() fixture for an existing Playwright Test project
@svatah/yam-recorder51Grounding, record session and report
@svatah/yam-runtime50Runner-agnostic executor core: scope, guards, checkpoints, policies, results, audit
@svatah/yam-schema185Zod definitions and generated JSON Schemas for the Yam artifact contracts
@svatah/yam-screens125The headless screen model: one set of screens, actions and keys behind the app, yam ui, the SDK and the CLI
@svatah/yam-sdk17The typed TypeScript client for the Yam local service, generated from its OpenAPI description (REQ-SDK-1)
@svatah/yam-service17Local HTTP and event-stream service (yam serve)
@svatah/yam-spec54Flow reader, grammar, target dictionary, signatures
@svatah/yam-steps30defineStep API and the Tier 0 matcher
@svatah/yam-surface103The published AgentSurface interface, adapter registry and wire schemas
@svatah/yam-surface-control139Shared surface operation dispatcher, session lifecycle and operation catalogue
@svatah/yam-tool17MCP tool server exposing stories as deterministic tools
@svatah/yam-trajectory19Trajectory capture and compile to proposals
@svatah/yam-tui78yam ui — the terminal cockpit, a second renderer of the screen model (REQ-TUI-1)
@svatah/yam-ui44The Yam design system: React components on Radix primitives, every one of them named and id'd (REQ-ADE-12)
@svatah/yam-ui-tokens28The Yam design tokens: two themes, one type ramp, one status set (REQ-ADE-12)
@svatah/yam-workflow8Story-as-function runner and resume