{
  "id": "page:docs-user-guide-ecosystem-genty",
  "_kind": "Page",
  "_file": "wiki/docs/user-guide/ecosystem/genty.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/user-guide/ecosystem/genty.md",
    "sourceKind": "repo-docs",
    "title": "genty — the unified agent runtime",
    "displayName": "genty — the unified agent runtime",
    "slug": "docs/user-guide/ecosystem/genty",
    "articlePath": "wiki/docs/user-guide/ecosystem/genty.md",
    "article": "\n[Docs](../index.md) › [Ecosystem](./overview.md) › genty\n\n# genty — the unified agent runtime\n\n**Packages:** `@a5c-ai/genty` + `@a5c-ai/genty-core` / `@a5c-ai/genty-runtime` / `@a5c-ai/genty-platform` · **CLI:** `genty` · **Version:** 6.0.0 · **Maturity:** GA (actively consolidating)\n\n**Genty is the unified agent product that composes every layer of the Babysitter agent stack into a single distributable binary, `genty`. It is how you run processes headlessly, serve MCP, run the internal harness, and drive the daemon/TUI.**\n\n> **Naming:** genty is the renamed `tula` stack. Older material (the April 2026 `v6-announcement.md`) calls the orchestration CLI `agent-platform` / `babysitter-harness` — that naming is **stale**. The README and package metadata are authoritative: use **genty** and `@a5c-ai/genty-platform`.\n\n---\n\n## On this page\n\n- [What it is](#what-it-is)\n- [The layered architecture](#the-layered-architecture)\n- [The command surface](#the-command-surface)\n- [genty as a harness](#genty-as-a-harness)\n- [Surfaces](#surfaces)\n- [Examples](#examples)\n- [Next steps](#next-steps)\n\n---\n\n## What it is\n\nGenty composes the agent stack into one binary. The `@a5c-ai/genty` package (the `cli/` package) re-exports all layers and owns the single `genty` binary. Install the runtime layer when you need headless orchestration, the internal harness, daemon utilities, MCP serving, or the TUI:\n\n```bash\nnpm install -g @a5c-ai/genty-platform\n```\n\n---\n\n## The layered architecture\n\n| Layer | Package | Responsibility |\n|-------|---------|----------------|\n| **L4** | `@a5c-ai/genty-core` | \"Genty core runtime and tool surface\": the agent loop, subagent, context-management strategies, agentic tools (code/exec/fs/web/browser/delegation), synthesis interfaces, and the deferred/extension tool registries. |\n| **L5** | `@a5c-ai/genty-runtime` | Daemon, session, cost, observability, telemetry. |\n| **L6** | `@a5c-ai/genty-platform` | \"Agent Platform layer — harness integration, governance, interaction, storage\" (subpaths `./anycli ./api ./cost ./daemon ./governance ./harness ./interaction …`). |\n| **CLI** | `@a5c-ai/genty` | Re-exports all layers; owns the `genty` binary. |\n\n---\n\n## The command surface\n\nVerified from `packages/genty/cli/src/cli/dispatch.ts`, the `genty` binary dispatches:\n\n`call`, `yolo`, `plan`, `forever`, `resume`, `resume-run`, `create-run`, `retrospect`, `cleanup`, `assimilate`, `doctor`, `contrib`, `observe`, `tui`, `start-server`, `rpc`, `discover`, `list`, `invoke`, `print`, `session-history`, `session-export`, `anycli`, `user-install`, `project-install`, `help`, `version`.\n\nIn an in-session context the same surface is exposed as the babysitter command set (for example `/babysitter:call`, `/babysitter:plan`, `/babysitter:resume`). See [Slash Commands](../reference/slash-commands.md).\n\n---\n\n## genty as a harness\n\nThe README surfaces genty both as the runtime CLI and as a \"harness\" (`genty call --harness internal …`). One thing to be precise about:\n\n> The codecs package does **not** list a standalone `genty` codec. The internal/headless engine is the SDK's built-in **Pi** engine surfaced through `genty call --harness internal`. So the \"genty harness\" in everyday usage is the **genty CLI running on the internal Pi engine** — not a separate codec.\n\nThis is the harness to reach for in CI/CD and headless automation when you want orchestration without a third-party coding harness.\n\n---\n\n## Surfaces\n\nGenty ships UI surfaces under `packages/genty/{ui,webui,tui,desktop-app,mobile-*,tv-*,watch-*,web-app}`, reflecting the v6 ambition of running processes on every surface. The TUI is available via `genty tui`.\n\n---\n\n## Examples\n\n```bash\n# Run a process headlessly on the internal (Pi) engine — good for CI\ngenty call --harness internal \"implement the change described in the issue\"\n\n# Plan a run without executing it\ngenty plan \"refactor the auth module\"\n\n# Serve MCP for a client like Claude Desktop\ngenty start-server\n\n# Watch a live run\ngenty observe\n\n# Resume an interrupted run from its journal\ngenty resume\n```\n\n> Subcommand flags are governed by the repository CLI allowlist; run `genty <command> --help` for the version-matched flag surface.\n\n---\n\n## Next steps\n\n- **See where it sits:** [Architecture & How It Fits Together](../architecture.md)\n- **The internal harness in context:** [Adapters overview](./adapters.md)\n- **Commands:** [Slash Commands](../reference/slash-commands.md) and [CLI Reference](../reference/cli-reference.md)\n- **Ecosystem map:** [Ecosystem Overview](./overview.md)\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-user-guide",
      "to": "page:docs-user-guide-ecosystem-genty",
      "kind": "contains_page"
    }
  ]
}