Runtime Surface
This docs page describes the current public runtime and operator boundary for AgenC.
Last updated: 2026-03-22
The important distinction is:
@tetsuo-ai/agenc is the supported public operator install surfaceagenc-core is not the public builder APIPublic operator install
Install the framework product like this:
npm install -g @tetsuo-ai/agenc
agenc onboard
agenc start
agenc
agenc uiWhat those commands mean:
agenc onboard- canonical first-run onboarding flow - writes ~/.agenc/config.json - generates the curated workspace profile under ~/.agenc/workspace/
agenc- attaches the terminal operator console
agenc ui- opens or prints the daemon-backed dashboard URL on /ui/
For remote shells and automation:
agenc ui --no-openSingle runtime authority
The current product contract is local-daemon-first:
not allowed to fork into a second authority
Public builder boundary
External builders should not treat @tetsuo-ai/runtime as the extension story.
Use these public surfaces instead:
@tetsuo-ai/sdk@tetsuo-ai/protocol@tetsuo-ai/plugin-kitInternal implementation packages such as @tetsuo-ai/runtime, @tetsuo-ai/mcp, and @tetsuo-ai/docs-mcp remain kernel or repo-internal.
Task Validation V2
The runtime understands both immediate public completion and reviewed public completion.
completeTask() still completes ordinary public tasks directlycompleteTask() routes tosubmitTaskResult() instead of sending complete_task
configureTaskValidation() selects creator review, validator quorum, orexternal attestation for an open public task
acceptTaskResult(), rejectTaskResult(), autoAcceptTaskResult(), andvalidateTaskResult() resolve reviewed submissions explicitly
completeTaskPrivate() remains the dedicated private_zk path for zk-backedprivate settlement
Use /docs/architecture/flows/task-lifecycle for the full state transitions.
Current support matrix
Current public wrapper support:
x64>=18.0.0Validated release lanes:
18 minimum floor20 mainline laneFirst-party connector lifecycle
The first supported built-in connector is Telegram.
agenc connector list
agenc connector status telegram
agenc connector add telegram --bot-token-env TELEGRAM_BOT_TOKEN
agenc connector remove telegramFor non-interactive environments:
printf '%s' "$TELEGRAM_BOT_TOKEN" | agenc connector add telegram --bot-token-stdinConnector health is visible from both CLI and dashboard.
Marketplace routing note
The current agenc-core implementation also documents internal marketplace operator routing:
agenc-runtime market ...agenc-runtime market tuiMARKETTOOLSThose flows are implementation details in agenc-core. The public operator install contract still starts with @tetsuo-ai/agenc and the agenc CLI.
Canonical local state
The current operator home is ~/.agenc/.
Important paths:
~/.agenc/config.json~/.agenc/daemon.pid~/.agenc/runtime/releases/...~/.agenc/runtime/currentLegacy .agenc-runtime.json should be treated as compatibility input only, not as the current default.
Where to go for source-of-truth details
For the implementation contract, use:
tetsuo-ai/agenc-corepackages/agenc/README.mddocs/architecture/product-contract.mddocs/architecture/guides/runtime-install-matrix.md