What is AgenC?

As of March 22, 2026, the public AgenC surface is no longer one monolithic repository. The project 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 - Owns the runtime implementation, web dashboard, mobile app, and internal MCP surfaces

Public builder and contract repos

- Canonical home of @tetsuo-ai/sdk

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

- Canonical home of @tetsuo-ai/plugin-kit - Owns the public plugin authoring boundary

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:

daemon or gateway

Current supported public install tuple:

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 telegram

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 status

The public devnet contract was revalidated on March 22, 2026.

6UcJzbTEemBz3aY5wK5qKHGMD7bdRsmR4smND29gB2ab

until the 24-hour voting window closes

See:

Start here

Public repositories