SORCERESS
Browse the wiki

Checkpoints & Project Memory

Updated July 4, 2026Open the tool

WizardGenie includes two safety-and-context systems for larger game projects: Checkpoints and Project Memory.

Checkpoints let you save named restore points so you can roll back after an experiment or AI-assisted change. Project Memory gives WizardGenie a searchable long-term memory of conversations, decisions, debugging notes, agent insights, and code structure, so you can ask questions about earlier work and understand how your project is connected.

Open WizardGenie

What Checkpoints do

Checkpoints are project restore points. When you create one, WizardGenie records the current state of your project files and attaches your description to it. Later, you can restore a checkpoint to bring project files back to that saved state.

Use checkpoints before risky edits, major refactors, AI-generated changes, engine upgrades, asset import passes, or any moment where you want an easy way back.

WizardGenie can also create checkpoints automatically during agent work, so the checkpoint list may contain entries you did not create manually.

Using the Checkpoints panel

Open a project in WizardGenie, then open the Checkpoints panel.

Create a checkpoint

  1. In the checkpoint description field, type a short note describing the current state.
    • Example: “Before inventory refactor”
    • Example: “Working player movement”
    • Example: “Pre-boss-AI experiment”
  2. Click Create, or press Enter while the description field is focused.
  3. Wait for the confirmation message.
  4. The new checkpoint appears in the list.

The Create button is disabled until you enter a non-empty description. While WizardGenie is creating the checkpoint, the button shows a loading indicator.

If there are no file changes since the previous checkpoint, WizardGenie may report that there were no changes to save. The latest restore point remains available.

View existing checkpoints

The checkpoint list shows recent checkpoints with:

  • The checkpoint message
  • The date and time it was created
  • A relative age, such as “just now”, “12m ago”, “3h ago”, or “2d ago”
  • A numbered marker in the list
  • A LATEST badge on the most recent checkpoint

The most recent checkpoint is highlighted. If the list is empty, WizardGenie shows No checkpoints yet with a note that you can create one manually or let the AI agent create them automatically.

Restore a checkpoint

  1. Find the checkpoint you want in the list.
  2. Hover over it to reveal the Restore button.
  3. Click Restore.
  4. Wait for the restore confirmation.

Restoring applies the saved project state from that checkpoint. Use this when an experiment goes wrong, generated changes are not useful, or you want to return to a known-good version.

Before restoring, save or close files in other editors so you do not confuse their unsaved state with the restored project files.

Important checkpoint behavior and limits

Checkpoints are designed to be helpful without interrupting your workflow, but there are a few practical limits:

  • Checkpointing requires project file access and a compatible local project directory.
  • If WizardGenie cannot access the project directory, checkpoint creation and restore can fail.
  • Extremely large projects may take longer to checkpoint.
  • Some very large or unusual project layouts may be skipped if WizardGenie determines checkpointing is not reliable for that project during the current session.
  • If checkpointing repeatedly fails for the current project, WizardGenie may stop trying until the project is reopened or a different project is loaded.
  • If there are no file changes since the previous checkpoint, WizardGenie may confirm that there were no changes to checkpoint while still keeping the current restore point available.
  • Restore operations affect project files. If you have unsaved changes in other editors, save or close them before restoring to avoid confusion.

For best results, create manual checkpoints before big changes even if automatic checkpoints are enabled. Manual descriptions make it much easier to recognize the right restore point later.

What Project Memory does

Project Memory is WizardGenie’s long-term recall system for your project. It has two parts:

  • MemPalace stores conversations, agent insights, decisions, discoveries, conventions, debugging history, and other useful project memories.
  • Graphify indexes your codebase as a knowledge graph of symbols and relationships, such as functions, classes, imports, dependencies, callers, and file connections.

Together, these systems help WizardGenie answer questions using targeted retrieval instead of relying only on the visible chat context. This is especially useful in long-running projects where important decisions happened many sessions ago.

Memory panel overview

Open the Memory panel inside WizardGenie to see three tabs:

  • Overview — status and statistics for memory and code indexing
  • Chat — ask natural-language questions about project memory and code structure
  • Visualizer — generate and view an interactive graph of the codebase

The panel also includes a refresh button for updating displayed stats.

Overview tab

The Overview tab shows the status of both memory systems.

MemPalace status

MemPalace displays:

  • Whether memory is Active or Inactive
  • The number of stored memories
  • Whether the memory system is Ready or Not initialized
  • A shortened local storage location when available

The memory count represents stored conversations and insights for the project.

Graphify status

Graphify displays:

  • Whether the code graph is Indexed or Not indexed
  • The number of indexed symbols
  • The number of relationships, when available
  • Whether the graph system is Ready or Not indexed
  • The current project name when available

Symbols can include functions, classes, imports, and related code elements.

Initialization and retrying

When you open a project, WizardGenie attempts to initialize memory services automatically if they are not already ready. The first initialization may take a minute.

If initialization is still running, the Overview tab shows an initializing message. If one or both systems are not ready, it shows a warning and a Retry Initialization button.

To retry:

  1. Open Memory → Overview.
  2. Click Retry Initialization.
  3. Wait for the status message.
  4. Use the refresh button if needed to update the displayed stats.

Possible outcomes include:

  • Both systems initialize successfully.
  • One system initializes and the other reports a warning.
  • Initialization fails and shows an error message.

The Overview tab also includes a short explanation of how the two memory systems work together: MemPalace stores conversation and insight history, while Graphify maps project code relationships. WizardGenie uses both for targeted recall when you ask memory questions.

Memory Chat

The Chat tab lets you ask questions about the project’s remembered history and code structure. WizardGenie searches project memory and the code graph before answering, then summarizes what it found in plain language.

You can ask about things like:

  • “What did we decide about player inventory?”
  • “Why did we change the enemy spawn logic?”
  • “Find debugging notes about the save system.”
  • “What files are related to combat?”
  • “How does the player controller connect to input and movement?”
  • “Do we have any conventions for naming abilities?”

Requirements for Memory Chat

Memory Chat requires an API key configured in Settings → API Keys. If no key is configured, the Chat tab explains that Memory Chat is unavailable until you add one.

Memory Chat also depends on the memory and code graph systems. If they are still initializing, a question may return a message saying memory or the code graph is not available yet. Wait a moment, then retry initialization from the Overview tab if needed.

How to use Memory Chat

  1. Open Memory → Chat.
  2. Type a question in the message box.
  3. Press Enter to send, or click the send button.
  4. Use Shift+Enter to add a line break without sending.
  5. Read the streamed response as WizardGenie searches memories and the code graph.

During a response, WizardGenie may show a brief searching message, such as searching memories or searching the code graph. The response may include simple formatting such as headings, bullet points, numbered lists, emphasis, and inline labels.

While a response is in progress, the send button is disabled and a loading indicator may appear.

Clear the chat

Click the trash icon to clear the current Memory Chat conversation. This clears the visible chat thread and resets the chat context for this panel. It does not delete the project’s stored memories.

Code Graph Visualizer

The Visualizer tab creates an interactive force-directed graph of your codebase. It is intended to help you see how files, symbols, and relationships connect.

Generate a graph

  1. Open Memory → Visualizer.
  2. If the code graph is indexed, click Generate Graph.
  3. Wait for the visualization to be created.
  4. The graph appears in the panel.

Once generated, the Visualizer shows:

  • That it is a force-directed graph
  • The number of nodes
  • The number of edges or relationships, when available
  • A Regen button for regenerating the visualization after changes or re-indexing

If the graph is not indexed yet, the tab explains that you need to open a project in WizardGenie so the codebase can be indexed.

Common workflows

Before a risky AI change

  1. Open the Checkpoints panel.
  2. Create a checkpoint with a clear description, such as “Before AI combat rewrite”.
  3. Run the AI-assisted change.
  4. Test the project.
  5. If the result is not useful, restore the checkpoint.

Understanding why something was built a certain way

  1. Open Memory → Chat.
  2. Ask a question about the decision or system.
  3. If the answer is too broad, ask a more specific follow-up using names from your project.
  4. Use the answer to decide whether to preserve, revise, or remove the old design.

Exploring an unfamiliar codebase

  1. Open Memory → Overview and confirm Graphify is indexed.
  2. Open Memory → Visualizer and generate the graph.
  3. Look for highly connected areas or systems you recognize.
  4. Open Memory → Chat and ask how a specific gameplay system connects to related files or symbols.

Tips & troubleshooting

“No checkpoints yet”

Create a manual checkpoint by entering a description and clicking Create. Automatic checkpoints may appear later during agent work, but manual checkpoints are recommended before important changes.

Checkpoint creation failed

Try the following:

  1. Make sure a project is open.
  2. Make sure the project directory is writable.
  3. Close other tools that may be heavily modifying the project at the same time.
  4. Try again with a short, clear checkpoint description.
  5. If the project is extremely large or has an unusual layout, checkpointing may be unavailable for the current session after repeated failures.

Restore failed

Check that the project is still available and writable. If external editors, build tools, or game engines are actively modifying files, close or pause them and retry.

Memory systems not initialized

Click Retry Initialization in the Overview tab. First-time initialization can take longer than later runs. If it continues to fail, restart WizardGenie and reopen the project.

Memory Chat says an API key is not configured

Open Settings → API Keys and add the required API key. Then return to Memory Chat and try again.

Memory Chat says memory or the code graph is unavailable

The memory system may still be initializing or the project may not be indexed yet. Wait briefly, refresh the Overview tab, and use Retry Initialization if needed.

Memory Chat finds nothing relevant

Try a more specific question. Include the feature name, system name, bug, mechanic, convention, or decision you are looking for. For code relationships, ask about a concrete file, class, function, or gameplay system by name.

Code graph is not indexed

Open a project and wait for indexing to complete. Use Retry Initialization from the Overview tab if the status remains Not indexed.

Graph generation fails

Confirm that Graphify is indexed in the Overview tab, then try Generate Graph or Regen again. If it still fails, refresh stats, retry initialization, and reopen the project if necessary.

Best practices

  • Create a checkpoint before accepting large AI-generated edits.
  • Use descriptive checkpoint names so you can recognize them later.
  • Before restoring, save or close files in external editors.
  • Ask Memory Chat about past decisions before changing architecture.
  • Use the Visualizer when onboarding to an unfamiliar project or investigating tightly connected systems.
  • Retry initialization if memory or graph status looks stale after opening a project.
  • Ask targeted follow-up questions instead of one very broad question when exploring complex systems.

FAQ

Do checkpoints replace a full backup system?

No. Checkpoints are a convenient project-level restore tool inside WizardGenie, but you should still keep normal backups for important projects.

Are automatic checkpoints enough?

Automatic checkpoints are helpful, but manual checkpoints are still recommended before risky changes so the restore point has a description you recognize.

Does clearing Memory Chat delete project memory?

No. It only clears the visible chat conversation and resets the chat context. Stored project memories remain available.

Why does Memory Chat sometimes say it is searching?

WizardGenie searches long-term memory and the code graph before answering so it can ground the answer in your project instead of guessing.

What should I do if a memory answer seems incomplete?

Ask a more targeted follow-up, mention specific systems or names, or check that MemPalace and Graphify are both ready in the Overview tab.

Why is the Visualizer unavailable?

The Visualizer needs an indexed code graph. Open a project, wait for indexing, and check Memory → Overview. If Graphify remains Not indexed, click Retry Initialization.