STEMProduct boundaries
STEM capabilities, limits and recovery
Check shared memory, retrieval limits, file access, export limits, retries and the workflows STEM does not perform.
Documentation reviewed . Host verification dates are listed separately.
Use STEM to preserve selected context and retrieve it in another authorized conversation. A connection is not an import of every chat, a copy of a provider's built-in memory, or a way to remotely run another agent.
| Capability | Boundary |
|---|---|
| Shared memory | Both assistants authorize the same STEM account. The destination must call recall. |
| Conversation transfer | Selected, reviewed notes can be saved. No bulk history importer or transcript synchronization. |
| Agent coordination | Shared context only. STEM does not send agent-to-agent messages, schedule their work or make them read every note. |
| Automatic memory | Optional, per eligible OAuth connection, best effort, with current permission and host approval. |
| Uploaded media | Private by default; separate explicit sharing. Memory tool availability is not access to every uploaded file. |
Retrieval and graph limits
recall returns at most 50 ranked candidates. Results can be weak matches or empty; use a distinctive project name and inspect the retrieved text and IDs. Retrieval can use semantic search when available, with keyword/recency fallback. It is not exhaustive archive search.
graph includes at most 1,000 memories and reads up to 3,000 edges. A smaller visual graph does not establish that older records were deleted. The authenticated memory export currently requests up to 100,000 memory records and 200,000 links. Contact support for a larger export; do not treat a bounded result as proof of a complete archive.
Writes, retries and removal
A successful remember creates a record and can autolink it. Repeating it can create duplicates. A repeated link is also not promised to be idempotent. If a write times out, recall the distinct test note before retrying. Never report “saved” based only on an assistant's prose.
forget removes the specified memory and its STEM links. Confirm the exact returned ID and the user's deletion request. It cannot erase copies already shown elsewhere. No universal one-click restore or arbitrary provider-export importer is currently offered.
Recover without guessing
- 401 or OAuth challenge: reconnect through the client and complete browser authorization.
- No tools: enable STEM in the current host conversation and refresh its tool catalog.
- No expected memory: check the same account, actual successful save and distinctive query.
- Storage full: review usage; recall and export remain available.
- Storage accounting unavailable: the save failed closed. Retry later or contact support; do not delete data to guess at a repair.
- Automatic saving disallowed: stop automatic writes. Do not silently substitute an explicit-save tool.
See protocol details and errors, plan allowances and permissions and data control.
← Back to the agent hub · Machine-readable tool schemas