Deleting AI memory vs. revoking access
Work out whether you need to remove stored content, disconnect a client, stop new capture, or make a broader data request.
Choose what gets shared 2 min read
Pausing AI recall is not the same as stopping capture
Capture collects source material. Recall retrieves stored context for an answer. Pausing routine recall does not necessarily stop capture, delete stored memory, or block an explicit request to read it.
Name the behavior you want to stop
If you want an assistant to stop bringing old context into routine replies, a recall control may be the right place to start. If you want new conversations to stop entering the archive, you need the capture control. If you want stored content removed, neither action is enough.
These distinctions matter during a private task. A quiet assistant can make it feel as though the memory system is off even when capture is still running. Check the relevant state directly instead of inferring it from the absence of a mention.
Explicit requests can follow a different path
Dray’s explicit /dray request can read memory while routine recall is paused. A web handoff uses that marker. Review the prepared prompt if you are switching assistants while expecting memory access to be paused.
For a stricter boundary, review access revocation and disconnection options rather than treating pause as a universal switch. The action you choose should match whether you want to stop collection, stop access, or remove content.
TAKE THIS WITH YOU
Choose the control by intent
An illustrative template. Replace the details with material you are allowed to share.
I want fewer unsolicited references → review routine recall. I want new chats kept out → review provider capture. I want a connected client to lose access → review revocation. I want stored content removed → review deletion. I am about to send a handoff → inspect its explicit memory request and source scope.
USING THIS WITH DRAY
Keep the context. Check the source.
Dray’s data notes explicitly distinguish routine recall, capture, handoff requests, and separate experimental channels. Pausing recall does not close a channel.
Dray is in beta. Available sources and connections depend on your setup. Read the data notes before granting access.
Sources & next reads
Product details are grounded in the guides below. Example projects and prompts are illustrative, not customer results.