Addons

An addon is a self-contained module that adds a capability to arka-deck: memory, governance, artifact panel, squad, connector, etc. Addons subscribe to chat events and enrich the experience without modifying the core.

Pre-installed (first-party) addons

arka-deck ships its foundational addons. No third-party installation is needed to start.

Addon	Role	Status
`cortex-actions`	Cortex artifact panel (modes, blocs) in chat	beta
`cortex-lite`	Local Cortex runtime sidecar (project materialization, agent context)	stable
`memory-local`	Per-project agentic memory (capture, consolidation, augmentation)	beta
`gouvernance-lite`	Local Cortex-compatible policies, snippets and followup	beta
`mission-guardian`	Mission state, leader and QA gates, evidence	beta
`squad-leader`	Squad composition and coordination	beta
`squad-orchestration`	Multi-agent LangGraph orchestration (mission, report, verdict)	beta
`notion-connect`	Notion connector (pages, blocks, OAuth)	beta

Enable an addon

The Addons view lists available modules. Some addons can be enabled or disabled per project (e.g. you can disable memory-local on a project that doesn’t need persistent memory).

For always-active addons (cortex-actions, cortex-lite), activation is managed by arka-deck.

Current public limits

The addon contract is stabilized to eventually allow external extensions.
For today, all production addons stay first-party and explicitly wired in arka-deck.
There is no active third-party marketplace loading. This possibility remains a product trajectory, not a current promise.

This posture is intentional: until third-party addon sandboxing and signing are mature, we prefer a controlled perimeter.

For contributors

If you want to write an addon:

Read the addons-firstparty sheet of a similar addon (e.g. memory-local)
Follow the tutorial write an addon
Check the addon contract

What next?

Understand where your data lives: 07-securite-et-donnees
See addon-driven use cases: 04-cas-usage/