Models, tools, permissions and multi-surface experience
ENGINE · PROTOCOL · ECOSYSTEM
An open engineering platform for autonomous agents.
ChunkLib brings together the Agentic engine, a standard plugin boundary and developer tooling. The core stays focused; independent extensions enter only when users choose them.
Agentic stable releaseCompatible with the OpenCode ecosystem
agentic — zsh●
❯ npm install --global @chunklib/agentic
resolving @chunklib/agentic
✓ installed agentic
❯ agentic
AGENTICENGINE READY · PLUGINS EXPLICIT
stablepermission-awareplugin-ready
CLI / TUITerminal-first coding-agent experience
DesktopDesktop packages through an independent release channel
Web / ServerUse a browser with local or self-hosted Agentic services
IDE / SDKConnect development environments through VSIX, ACP and SDK interfaces
COMPOSITION OVER COUPLING
The engine is not a fixed feature bundle. It is the boundary through which capability can enter safely.
Agentic provides models, tools, permissions and a consistent multi-surface experience. Flow, Memory and other capabilities can be installed explicitly, used on demand and removed without changing ordinary sessions.
Install and enable independent capabilities through standard configuration
Every capability is optional, removable and independently updated
PROJECT MAP
From a stable engine to composable capability
01ENGINE
Agentic
Terminal-first coding agentA consistent experience across CLI, Web, Desktop and IDE surfaces with clear permission and compatibility boundaries.
Explore engine →02OPTIONAL PLUGIN
Agentic Flow
Explicit engineering orchestrationFor users who want defined stages for complex engineering work. Install and enable it on demand without changing ordinary Agentic sessions.
Plugin boundary →03PLUGIN CAPABILITY
Memory boundary
Independent memory capabilityHelps Agentic retain project facts, confirmed decisions, your preferences and verified outcomes. It remains a product direction, not a default feature.
USER BENEFITS
Predictable upgrades. Unbundled capability. Clear compatibility.
More predictable upgrades
Formal versions arrive through stable channels with corresponding release notes.
Clear capability boundaries
You can see what the engine already provides and what requires a separate install.
Choices stay unbundled
The engine, Desktop and plugins can be selected, updated and removed independently.
Ecosystem compatibility
Providers, tools and plugins continue to rely on real, inspectable interfaces and services.