hoziron memory
Manage agent memory — the per-agent key-value store.
Synopsis
hoziron memory <subcommand> [options]
Subcommands
| Subcommand | Description |
|---|---|
list <agent> | List KV pairs for an agent |
get <agent> <key> | Get a specific value |
set <agent> <key> <value> | Set a value |
delete <agent> <key> | Delete a KV pair |
hoziron memory list
hoziron memory list <agent> [--json]
Example
$ hoziron memory list claims-agent
KEY VALUE
claims_processed_count 142
avg_processing_time_ms 3200
last_claim_number CLM-2026-142
escalation_count 7
shift_start 2026-06-04T08:00:00Z
$ hoziron memory list claims-agent --json
{
"claims_processed_count": 142,
"avg_processing_time_ms": 3200,
"last_claim_number": "CLM-2026-142",
"escalation_count": 7,
"shift_start": "2026-06-04T08:00:00Z"
}
hoziron memory get
hoziron memory get <agent> <key> [--json]
Examples
$ hoziron memory get claims-agent claims_processed_count
142
$ hoziron memory get claims-agent last_claim_number
CLM-2026-142
$ hoziron memory get claims-agent nonexistent_key
(not set)
hoziron memory set
hoziron memory set <agent> <key> <value>
Examples
$ hoziron memory set claims-agent escalation_threshold 5
✓ Set claims-agent.escalation_threshold = 5
$ hoziron memory set claims-agent notes "Agent paused for maintenance at 10:00"
✓ Set claims-agent.notes = "Agent paused for maintenance at 10:00"
hoziron memory delete
$ hoziron memory delete claims-agent notes
✓ Deleted claims-agent.notes
Memory Isolation
Each agent has its own isolated memory scope:
- Agent A cannot read or write Agent B's memory
- Cross-agent access returns a
MemoryViolationerror - This is enforced by the
ScopedMemorywrapper at every operation - In workflows, data passes between agents only through step outputs (with PII tokenization)
How Agents Use Memory
Agents read/write memory through their equipped skills and competency logic. Competencies define [[metrics]] that reference memory keys:
[[metrics]]
label = "Claims Processed"
memory_key = "claims_processed_count"
format = "number"
The agent increments this key as it processes claims. The dashboard and memory list command expose the current values.
Use Cases
| Pattern | Example |
|---|---|
| Counters | claims_processed_count, errors_today |
| Last-seen state | last_claim_number, last_run_at |
| Configuration | escalation_threshold, auto_approve_under |
| Operator notes | notes, maintenance_reason |
| Agent preferences | preferred_format, verbose_mode |
See Also
- agent.md — Agent lifecycle
- ../competency-authoring.md — Defining metrics that use memory keys