Memory Local
Status
Section titled “Status”First-party addon shipped with arka-deck. Current registry is static / first-party; no active third-party marketplace.
| Field | Value |
|---|---|
| Manifest | addons/memory-local/manifest.json |
| Entrypoint | addons/memory-local/src/index.ts |
| Maturity | beta |
| Exposed inbound port | ForMemory |
Memory Local captures a per-session memory, consolidates a per-agent profile memory, composes a project memory and injects it into upcoming turns through the BeforeTurnAugmenter mechanism.
The addon is provider-neutral: any chat runtime that emits the expected events can feed memory.
Surfaces
Section titled “Surfaces”| Surface | Location |
|---|---|
| Addon options | <project>/.arka-deck/addons/memory-local/options.json |
| Memory storage | <project>/.arka-deck/addons/memory-local/memory.json |
Events listened
Section titled “Events listened”chat.session.ended— triggers a milestone capturechat.runtime.failure— notes runtime errors useful to memorychat.memorize— explicit capture request
Memory model
Section titled “Memory model”The addon exposes:
- a
registerLocalMemoryAddonfunction that wires the subscriptions and the inbound port; - a
ForMemoryport to read and write options, overview and captures; - a before-turn augmenter that reads recent local memory before a turn;
- a subscriber that reacts to session/failure events.
Boundaries
Section titled “Boundaries”- Local-first memory: no cloud service required.
- Cortex Runtime can enrich prompts and context atoms, but it is not the storage authority for local notes.
- arka-deck never mutates
CLAUDE.mdor other agent instruction files as a default memory path. - No secret or credential should be persisted in a memory note.
Going further
Section titled “Going further”- Addon contract: ../extension/contrat-addon (coming)
- “Write an addon” tutorial: ../extension/ecrire-un-addon (coming)