Memory in CodeWords
How Cody learns about you through structured memory, what it remembers, and how memory improves every new conversation.
How Cody learns about you and how that makes every conversation better.
What is memory?
Every time you chat with Cody, build a workflow, or connect an integration, CodeWords builds a structured profile of how you work. This is not a raw conversation log. It is a summary layer that helps Cody skip setup questions and move faster toward solving your task.
Think of memory like a coworker who remembers your projects, tools, and preferences, without you having to repeat them every time.
What does Cody remember?
Memory is built from six sources. Each source has its own schedule for how often it updates.
1) Your profile
Account basics such as name, email, role, experience level, and join date.
Example:
Rithul, PM at Agemo AI, some automation experience
2) Onboarding answers
First-time context captured during signup, such as your role, goals, and discovery source.
Example:
Found CodeWords via Reddit. 200 emails/week, 66% promotional.
3) Your workflows
A live view of the workflows in your account, including names, descriptions, how often they run, and how they're performing. This updates continuously.
Example:
Your Gmail Auto Labeler workflow and how often it runs
4) Integrations
Names of connected services only (for example Gmail, Stripe, Slack, LinkedIn, Notion). Credentials and token values are never stored in memory.
Example:
Gmail, Stripe, Slack, LinkedIn, Notion
5) Behavioral signals
Patterns Cody notices over time, like the topics and tools you use most. These are summaries, not chat transcripts.
For example, Cody might notice that you often ask about LinkedIn, frequently work with AI features, and tend to ask building-related questions rather than just exploratory ones.
6) Recent activity
A compact list of your most recent chat topic titles and dates (for example last ~10) so Cody knows what you have been working on recently.
Example:
Figma UI Build (May 1), Stripe Checkout (Apr 29)
Behavioral signals: a closer look
Cody doesn't re-read your old chats. Instead, your conversations are reviewed from time to time to spot recurring patterns, like which integrations you use most or what types of automations you tend to build. Cody only sees that summary, not the actual messages.
This helps Cody personalize your experience without holding on to raw conversation content.
How memory is used
When you start a new conversation, Cody receives your compiled memory profile before your first message.
Without memory, Cody may need to ask:
What email provider do you use?
Do you have Stripe connected?
What is your technical level?
What have you been working on recently?
Have you built something similar before?
With memory, Cody can already infer:
Which tools and integrations you use
Your likely experience level
Your recent context and active projects
Related workflows it can build on
What Cody does not have access to
Memory is designed to be useful without being invasive.
Full conversation transcripts (only a summary of patterns and stats)
API keys, tokens, or passwords (only the names of secrets are visible, never the values)
The data your workflows process
Personal data from connected services outside of active workflow runs
Activity outside CodeWords
Memory vs chat history
What it is
Messages in a single conversation
Compiled profile across all conversations
Scope
One chat thread
Your entire CodeWords account
Availability
Inside that chat only
Available at the start of every new chat
Persistence
Ends with the chat
Persists across sessions
Format
Raw messages
Structured, tagged, summarized
Frequently asked questions
Can I edit or correct my memory?
There is no dedicated memory editor UI today. If something is incorrect, tell Cody. As your workflows and activity change, your memory profile updates over time.
Does Cody remember what I said in a previous chat?
Not word-for-word through memory. Cody retains patterns (for example, frequent LinkedIn work) and structured facts (for example, number of active workflows), not a transcript replay of a prior conversation.
Can I reset my memory?
Contact CodeWords support to request a memory reset. This clears compiled behavioral signals and memory profile data so you can start fresh.
Privacy and security
Credentials are never stored in memory. Secrets stay in a separate, encrypted system.
Cody doesn't re-read your old chats — only summarized patterns are used.
Memory is private to your account, with no cross-user sharing.
Platform data retention and privacy policies apply to memory data.
Last updated
Was this helpful?