store
Store compact memory records or coordination signals to a bridge for later retrieval and workflow handoffs.
Instructions
Store one entry in the bridge for later retrieval or coordination.
Use this tool when you want to persist a compact memory record or write a signal
that another workflow can poll later. Write durable knowledge as kind="memory"
and transient coordination events as kind="signal".
Returns the stored entry identifier, timestamp, and duplicate information. Repeated
memory writes may deduplicate; signal writes are intended to remain append-like.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| namespace | Yes | Logical memory bucket to write into, such as `project:<workspace>`, `domain:<name>`, or `global`. | |
| content | Yes | Machine-readable memory payload to persist. Prefer compact claims, fixes, decisions, or signals over long transcript-style prose. | |
| kind | No | `memory` stores durable knowledge for later retrieval. `signal` stores pollable coordination events for handoff or workflow triggers. | memory |
| tags | No | Optional stable labels for retrieval and filtering, for example `kind:gotcha`, `domain:retrieval`, or `project:demo-app`. | |
| session_id | No | Optional session or thread identifier used to trace entries back to one conversation or work unit. | |
| actor | No | Optional writer identity such as an agent, reviewer, or user profile. | |
| title | No | Optional short label for UI display or scanning. Keep it concise and stable when possible. | |
| correlation_id | No | Optional shared identifier used to link related writes, handoffs, or workflow events across entries. | |
| source_app | No | Optional source name for the writer, such as `codex`, `codex-session-watcher`, or another local automation. | |
| source_client | No | Optional external client identifier such as `codex`, `antigravity`, or `claude-code`. | |
| source_model | No | Optional external model identifier such as `gpt-5.4` or `gemini-2.5-pro`. | |
| client_session_id | No | Optional external client session or thread identifier when the caller can provide one. | |
| client_workspace | No | Optional external client workspace root or project label when useful for provenance. | |
| client_transport | No | Optional transport label such as `stdio`, `http`, or `sse`. | |
| expires_at | No | Optional ISO-8601 expiry timestamp for a signal. Use this when a coordination event should stop being claimable after a deadline. | |
| ttl_seconds | No | Optional relative expiry in seconds for a signal. Useful for short-lived handoff or review events. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||