What OpenTag remembers

Conversation context

OpenTag uses the current request, earlier conversation and accessible sources to continue work. Conversations and execution records persist separately from learned memory; ending a run does not mean all of that information is erased.

Stay in the same thread for a follow-up, or paste the original discussion's link when starting elsewhere.

Personal preferences and facts

OpenTag can learn useful preferences from your messages, including explicit corrections:

Keep my weekly reports under a page.

When I say “the deck”, I mean the Series A deck in Drive.

Use Memory in the web app to inspect your current preferences and search remembered facts for the selected workspace. Learning happens in the background, so check the saved result if an update matters.

Company knowledge

The wiki combines company evidence from accessible channels, documents and meetings. Shared company facts and your private preferences have different audiences.

A request to change a company fact needs a clear target and the appropriate authority. Say whether you mean “remember this for me” or “correct the company's record”.

Who can use memory

Private conversations use the member's personal memory and available team context. Private rooms have their own audience. Public-channel context can serve the team; external Slack rooms have restricted recall.

Sharing a particular private memory with the team is a separate action. Connecting an app also has its own sharing controls; see How connections work.

Forgetting and deletion

Ask OpenTag to forget a specific personal fact or preference. Be precise enough to identify the item. Forgetting a learned fact does not erase the message where you originally said it, the execution record, or information you explicitly shared with the team.

For source data, retained records or a workspace deletion request, follow Deleting your data.