Explicit activation
Installing a plugin does not silently change every ordinary Agentic session.
PLUGIN ECOSYSTEM
Plugin capability is an engine boundary—not a default feature list.
You install each extension deliberately. It can update and be removed independently, with clear guidance for configuration, data and permissions.
EXTENSION CHOICES
The plugin boundary users can rely on
Core keeps working
If a plugin fails or is removed, the basic Agentic experience remains available.
Independent updates
Each plugin uses its own release channel and explains compatibility.
Clear data ownership
Stateful plugins explain what they store and how to delete or move it.
Predictable uninstall
You can understand what happens to configuration and data before removal.
No permission amplification
Extensions remain subject to permissions, project rules, sandboxing and user approval.
OPTIONAL EXAMPLE
Agentic Flow · an independent plugin example
Agentic Flow is for users who want defined stages for complex engineering work. It is installed separately and selected deliberately; it does not replace Agentic's default model-led planning or activate itself in ordinary sessions.
npm ↗ActivationSelect the `flow` primary agent or run `/flow <task>`
Install@chunklib/agentic-flow
Default stateDisabled
Ordinary sessionsUnaffected
UpdatesIndependent from the Agentic engine
MEMORY
Project factsConfirmed decisionsYour preferencesVerified outcomes
Product direction · not shipped as a default featureUSER-CONTROLLED MEMORY
What should Memory remember?
Memory is intended to help Agentic understand your project and working style across long-running collaboration. It should retain only what makes the next task more accurate and continuous.
Memory boundary
It should not keep every conversation forever or turn secrets, unconfirmed inferences, or unrelated personal information into durable memory. You should be able to inspect, correct, delete, and move your memories.