CHUNKLIB PLATFORM

Keep the core focused and extensions independent.

ChunkLib does not pack every capability into one engine. The core experience stays stable while plugins and external services remain optional and independently updated.

ARCHITECTURE

Platform architecture

01

Product surfaces

Use the same Agentic capability through CLI, TUI, Web, Server, Desktop and IDE surfaces.

02

Core toolbox

Connect models, tools, permissions, MCP and project rules to complete real development work.

03

Optional extensions

Install the plugins you need through standard configuration and remove them when you do not.

04

Independent services

Long-term capabilities such as memory stay independent so data ownership, permissions and transfer remain clear.

WHAT YOU CAN EXPECT

Four principles you can rely on

Explicit choice

Capabilities are installed and enabled deliberately, never silently added to ordinary sessions.

Removable

Agentic's core experience keeps working after an extension is removed.

Clear compatibility

Each component explains its platform, install channel and compatibility scope.

Permission-aware

Plugins and external services remain subject to project rules, sandboxing and user approval.

ENGINEstable+PLUGINoptional+SERVICEindependent

INDEPENDENT UPDATES

One platform. Every capability can evolve independently.

The engine, plugins and external services can update separately. Choose only what you need today, then combine it through clear compatibility ranges.