monoswarm memory command (monomind)
Scanned 9/10/2026
Install to Claude Code
npx -y skills add monoes/monomind --skill monomind-monomind-monomind-monoswarm-memory --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Monomind Monomind Monomind Monoswarm Memory?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/monoes-monomind-monomind-monomind-monoswarm-memory)More formats (shields.io, HTML) on the badges page.
---
description: monoswarm memory command (monomind)
type: flow
name: monomind-monomind-monomind-monoswarm-memory
---
# monoswarm memory
Access and manage monoswarm shared memory — a key-value blob on the run's
state file, readable/writable by all agents coordinating in the current run.
There is no `npx monomind monoswarm memory` CLI command — this is invoked
directly as an MCP tool call (see below).
## Parameters
| Param | Type | Default | Description |
|---|---|---|---|
| `action` | string | `list` | Action: `get`, `set`, `delete`, `list` |
| `key` | string | — | Memory key (required for `get`, `set`, `delete`) |
| `value` | any | — | Value to store (required for `set`) |
## Examples
```javascript
// List all keys in shared memory
mcp__monomind__monoswarm_memory({ action: "list" })
// Store a value
mcp__monomind__monoswarm_memory({ action: "set", key: "project-goal", value: "Build auth module" })
// Retrieve a value
mcp__monomind__monoswarm_memory({ action: "get", key: "project-goal" })
// Delete a key
mcp__monomind__monoswarm_memory({ action: "delete", key: "project-goal" })
```
## Actions
- **`list`** — Show all keys currently in shared memory with count (default)
- **`get`** — Retrieve the value at a key (requires `key`)
- **`set`** — Store a value at a key (requires `key` and `value`)
- **`delete`** — Remove a key from shared memory (requires `key`)
## Relationship to `monomind memory`
`monoswarm memory` operates on the **run's shared memory namespace** — a
single JSON blob on the run state file, visible to all agents coordinating
in the current run. This is distinct from the global memory tools
(`memory_pattern-store` / `memory_pattern-search` / CLI `monomind memory`), which are
backed by local SQLite (with `sql.js`/WASM as a fallback) — not LanceDB,
which has been fully removed from this codebase.
Use monoswarm memory for transient inter-agent coordination data (task
results, intermediate state). Use global memory for patterns and knowledge
that should persist across sessions.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!