recall
Search durable memory and poll for new signals using metadata filters, returning matching entries with a cursor for continuous polling.
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 and usually kind="signal".
Returns matching items plus a next_since cursor that can be reused for the next
polling cycle.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| namespace | Yes | Namespace to search or poll, such as `project:<workspace>`, `domain:<name>`, or `global`. | |
| query | No | Optional text query for full-text recall. Leave empty to use filter-only retrieval or polling. | |
| limit | No | Maximum number of entries to return. Smaller values keep context tighter. | |
| kind | No | Optional type filter. Use `memory` for durable knowledge recall and `signal` for coordination or polling flows. | |
| signal_status | No | Optional status filter for signals. Useful when you want only pending handoffs, currently claimed work, or already-acked coordination events. | |
| tags_any | No | Optional OR-style tag filter. Any matching tag is enough for an entry to qualify. | |
| session_id | No | Optional session filter to narrow results to one conversation or run. | |
| actor | No | Optional actor filter for entries written by a specific agent or user. | |
| correlation_id | No | Optional correlation filter to recall entries linked to the same workflow, handoff, or task. | |
| since | No | Optional cursor for polling only entries newer than a previously seen entry id. Most useful with `kind="signal"`. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||