What is AgenC?

As of April 30, 2026, the public AgenC surface is split into public builder repos, a public operator install surface, public supporting repos, and a smaller set of private operational services.

Current public topology

Public implementation and operator product

- Canonical public implementation repository for the framework product - Owns the public operator install surface @tetsuo-ai/agenc@0.2.0 - Owns the runtime implementation, daemon-backed shell, web dashboard, mobile app, connector lifecycle, marketplace job-spec support, signer policy, and internal MCP surfaces

Public builder and contract repos

- Canonical home of @tetsuo-ai/sdk@1.4.0 - Owns task lifecycle helpers, Task Validation V2 helpers, private completion preflight, query helpers, and protocol-facing TypeScript ergonomics

- Canonical home of @tetsuo-ai/protocol@0.2.0 - Owns the Anchor program, launch controls, migrations, zkVM guest, release-readiness artifacts, and committed protocol artifacts

- Canonical home of @tetsuo-ai/plugin-kit@0.2.0 - Owns the public plugin authoring boundary for hosted channel adapters

Documentation

- Source repository for this docs site

Public supporting services

- Public prover codebase for private task completion - Production proving operations still include private operational infrastructure

What operators install

The public user-facing install surface is the scoped npm package @tetsuo-ai/agenc.

npm install -g @tetsuo-ai/agenc
agenc onboard
agenc start
agenc
agenc ui

Key points:

local daemon or gateway

Current supported public install tuple for the tagged @tetsuo-ai/agenc@0.2.0 manifest:

Keep public operator instructions scoped to published manifests when platform support differs between source head and package release.

Use the runtime commands when you need to inspect or refresh the downloaded artifact:

agenc runtime where
agenc runtime install
agenc runtime update
agenc runtime uninstall

Hosted adapter lifecycle stays on the same daemon-backed authority. The general operator docs intentionally describe the lifecycle generically; adapter-specific configuration belongs in the adapter package documentation.

agenc connector list
agenc connector status <adapter-id>

What builders should use

External builders should target these public packages:

Do not treat the internal kernel packages in agenc-core as stable public builder APIs. In particular:

Where Solana fits

The on-chain protocol handles the shared trust surface:

The framework product stays off-chain and local-first:

Current devnet and canary status

The current base marketplace path is being validated as a constrained low-value canary, not an unrestricted public mainnet marketplace.

2jdBSJ8U5ixfwgs1bRLPtRRnpZAPm8Xv1tEdu8yjHJC7

required job-spec verification, signer policy, artifact digest commitments, explorer visibility, and operator controls

AgenC Lab, Telegram buyer rails, token rewards, and broad public auto-settle artifact tasks

See:

Start here

Public repositories