No Lost Context or Interrupted Sessions

The recompile-resistant architecture ensures zero context loss and zero session interruptions. This is GameCatalyst’s most important architectural feature—it’s what makes AI-assisted Unity development practical and productive.

What persists across recompilation:

Everything important survives recompilation:

• AI client connection — Stays connected to MCP Bridge. Your AI client never sees a disconnection.
• Project selection — Selected project remains active. You don’t need to reselect it.
• Session state — Permissions, tool availability, discovery history all persist in Python memory and SQLite databases.
• Workspace plans — Active plans, task progress, gaps, comments (stored in gamecatalyst.db). If Vex is working on a 50-task plan and Unity recompiles, Vex resumes exactly where it left off.
• Conversation context — Your AI client maintains conversation history. The conversation continues seamlessly.
• Discovery cache — File paths, scene contents, prefab references all persist. Vex doesn’t need to re-scan the project.
• Permission grants — If you granted file.create permission before recompilation, it’s still granted after.

What you can do during recompilation:

While Unity recompiles, you can still interact with Vex:

• Continue talking to Vex (Vex responds but can’t execute Unity commands) — Ask questions, discuss approaches, plan next steps
• Ask questions about GameCatalyst features — Vex can query WhatIs documentation without Unity
• Review plan status — Check workspace.plan progress, read task details
• Query WhatIs documentation — Browse command references, examples, troubleshooting guides
• Approve or pause plans — Manage workspace.plan execution

What you can’t do during recompilation:

Unity commands are blocked until recompilation finishes:

• Execute Unity commands (create objects, modify scenes, etc.) — Layer 5 is offline, so Unity API calls fail
• Read/write project files — File operations require Layer 5 for path validation
• Query scene contents — Scene queries require Unity API access
• Modify GameObjects or components — All Unity Editor operations are blocked

Vex will queue these commands and execute them automatically when recompilation finishes.

Typical recompilation scenario:

Here’s what a real workflow looks like:

1. Vex creates 5 new scripts — PlayerController, PlayerMovement, PlayerInput, PlayerHealth, PlayerInventory
2. Unity starts recompiling — Domain reload begins, Layer 5 goes offline
3. You ask Vex to create a prefab — “Create a Player prefab with PlayerController attached”
4. Vex: “Unity is recompiling. I’ll create the prefab as soon as it finishes.” — Vex acknowledges the request and queues it
5. Unity finishes (10 seconds later) — Layer 5 reconnects automatically
6. Vex automatically creates the prefab — Executes the queued command
7. Vex: “Created PlayerPrefab.prefab in Assets/Prefabs/” — Confirms completion

Seamless. No manual intervention required. No lost context. No reconnection steps.

Comparison to other Unity AI tools:

Most Unity AI integrations run entirely inside Unity. When Unity recompiles:

• Connection drops
• Session state lost
• Manual reconnection required
• Project reselection required
• Conversation context lost

GameCatalyst’s external architecture eliminates all of these problems. Recompilation becomes a minor pause instead of a major interruption.

Performance impact:

The multi-layer architecture adds latency (50-100ms per command), but this is negligible compared to the time saved by avoiding reconnections. A single avoided reconnection saves 10-30 seconds—enough to justify hundreds of commands.