GA Release

The Multi-Agent WebGPU Engine & Interactions API are now generally available.

Part 11: Memory — Long-Term Facts That Survive Across Chats

The cure for "As I told you before..." — maintain persistent developer preferences, stack constraints, and project facts across all conversation threads.

Category: Getting Started • Read Time: 20 min read • Updated: August 2026

1. The Problem Memory Base Solves

Standard AI chats are amnesiac. Every new chat thread forces you to repeat your role, preferred tech stack, and project rules.

Chat History (Temporary)

Scoped strictly to one conversation thread. Dies when starting a new chat.

Folder Memory (Scoped)

Scoped strictly to chats inside a specific folder (e.g. "In this folder, use TypeScript").

Memory Base (Global)

Saved facts can be included in relevant chats while active. They remain in browser storage until removed or site data is cleared; optional backup and sync depend on your settings.

2. Opening & Navigating Memory Manager

Click Memory (Brain icon) in the left sidebar to open the full-screen Memory Base Manager.

  • Preferences: Preferred language, framework, styling, and coding conventions.
  • Personal: Role, location, timezone, and communication style preferences.
  • Projects: Long-term facts and architectural constraints for specific active projects.
  • General: Universal facts, domain knowledge, or custom workflow rules.

3. AI Memory Suggestions — Review Before Saving

When memory suggestions are enabled, extraction is attempted only for prompts containing one of the app's memory cues (such as “remember” or “my preference”). The configured completion route receives the eligible prompt and assistant response to suggest facts; it does not run after every response. Suggestions appear above the chat composer and are saved only if you choose Keep within 60 seconds. No more than two AI-created items can be proposed in one conversation.

✅ Possible Memory Suggestions:

  • "I live in Allentown, PA" → Proposed for the Personal category; requires Keep.
  • "I always write TypeScript with strict null checks" → Proposed for Preferences; requires Keep.

❌ Ignored Short-Term Context:

The extraction instructions ask the model to ignore temporary details, code snippets, and attachments. Review every proposal before it is retained; discard anything you do not want saved.

4. Context-Aware Relevance Filtering

To prevent flooding system prompt tokens, Accelerated Logic AI performs keyword relevance matching before each turn. Only memories matching your current prompt context (or category) are injected into the model payload. Asking "What do you remember about me?" automatically injects all active memories.

5. Manual Fact Etching & Presets

Click Manual Entry to etch specific facts. On fresh installations, select from preset templates (Default Stack, Aesthetics, Developer Role, Architecture) for instant 1-click memory initialization.

6. Managing Memory Cards

Toggle Active (Eye Icon)

Mute/unmute individual memories without deleting them.

Inline Editing

Edit phrase wording or update category classification.

Wipe Memory Base

Purge all long-term facts with a single confirmed action.

7. Memory Settings & Deletion Permissions

In Settings → Fact Memory, toggle AI Can Delete Memories. When enabled, saying "Forget that I live in NY" allows the model to output a <delete_memory id="..."> tag to remove outdated facts safely.

8. Memory Best Practices

Do Save: Standard stack preferences, coding conventions, persona roles, WCAG accessibility rules, and long-term project requirements.

Do Not Save: Temporary bug details, raw file contents, secrets or API keys, or conflicting preferences (e.g. both light and dark mode).

9. Cloud Sync & Workspace Export

When Google Drive backup is enabled with Memories toggled ON, facts sync automatically to my_ai_memories.json. You can also export or import standalone JSON files in Settings → Export Workspace.

10. Memory Troubleshooting

Memory Not Applying? Ensure the Eye icon is active (not muted) and verify the memory text includes explicit keywords (e.g. "TypeScript") for relevance matching.

Conflicting Memory? Search for old preferences and delete outdated entries to prevent contradicting instructions.