Memory
Vuti uses workspace context to make planning and drafting less generic. Some context is ordinary workspace data, some is explicit memory, and some may live outside Vuti when you connect Vuti to another assistant.
What Vuti remembers
- Workspace context: brand profile, Brand Kit, banned phrases, Catalog items, inspiration, assets, posts, analytics, and agent runs.
- User voice: writing guidance saved for one user inside one workspace.
- Vuti chat history: recent conversation history for a user, workspace, and thread.
- Explicit memory: inspectable Vuti memories for preferences, corrections, facts, workflow rules, outcomes, and campaign context.
Memory scopes
- Workspace memory applies to the whole workspace, such as "do not show pricing unless asked."
- User memory applies to one user in one workspace, such as a personal summary style.
- Channel memory applies to a platform or connected account, such as "X threads should be max 5 posts."
- Campaign memory applies only to the matching campaign or planning goal.
- Thread memory stays tied to one conversation.
Current instructions win over old memory. Brand, Catalog, and current workspace facts also win over stale preferences.
Automations
The Weekly Planner automation uses active workspace, user, and platform memory when creating drafts. It keeps memory separate from brand profile, voice, performance guidance, and live research. Automation run details record which memory ids were used so the run can be audited.
ChatGPT connector memory
If you connect Vuti to ChatGPT, ChatGPT may use or save relevant information from connected apps depending on your ChatGPT settings and organization controls. That is ChatGPT memory, not Vuti memory.
Vuti settings control first-party Vuti memory. ChatGPT settings control ChatGPT memory.