recall
Retrieve matching memory entries or poll for new coordination signals by filtering on metadata like namespace, tags, actor, or session.
Instructions
Recall matching entries or poll for new signals from the bridge.
Use this tool to search durable memory, filter by metadata, or poll for fresh
coordination signals. For issue-like work, prefer project and domain recall before
external search. For workflow polling, pass since, an empty query, and kind="signal".
Empty-query Signal recall returns a next_since cursor for the next polling cycle;
other recall modes return next_since=null. The cursor tracks later insertions,
not status changes to older Signals.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Optional type filter. Use `memory` for durable knowledge recall and `signal` for coordination or polling flows. | |
| actor | No | Optional actor filter for entries written by a specific agent or user. | |
| limit | No | Maximum number of entries to return. Smaller values keep context tighter. | |
| query | No | Optional text query for full-text recall. Leave empty to use filter-only retrieval or polling. | |
| since | No | Optional cursor for polling only entries newer than a previously seen same-namespace entry id used as a Signal polling anchor. Requires an empty query and `kind="signal"`. | |
| tags_any | No | Optional OR-style tag filter. Any matching tag is enough for an entry to qualify. | |
| namespace | Yes | Namespace to search or poll, such as `project:<workspace>`, `domain:<name>`, or `global`. | |
| session_id | No | Optional session filter to narrow results to one conversation or run. | |
| signal_status | No | Optional status filter for signals. Useful when you want only pending handoffs, currently claimed work, or already-acked coordination events. | |
| correlation_id | No | Optional correlation filter to recall entries linked to the same workflow, handoff, or task. | |
| evidence_context | No | Optional caller-declared evidence labels. Only `model`, `harness`, and `chat_template` are accepted; signed receipts contain bounded SHA-256 digests, never raw values. These labels are not authenticated and do not affect retrieval order or feedback identity. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||