The search index
When you open a project, Summer indexes it so the agent can search by meaning, not only by exact words. Ask “make the player faster” and the agent finds the script that moves the player, even if it is calledhero_controller.gd.
It stays current. Summer remembers a fingerprint of each file and re-indexes only the files that changed. When the agent writes a file, that file is re-indexed right away.
The project map
Summer also keeps a short map of the project: the scripts that matter, theirclass_name, and where each main system lives (player, camera, combat, enemies, UI, saving, networking and more). The agent reads it at the start of a chat, so it knows where to look before it searches.
Direct reads
For exact answers, the agent reads your project directly:- Text search (
grep) for symbols, signals and patterns across every script. - File reads for the exact lines it is about to change.
- The scene tree of a scene, with node paths, types and properties.
What a new chat knows
Each new chat starts with the index, the project map and your project memory. It does not include your other chats. To bring something from an earlier conversation, mention the files or say what you decided. Decisions you want kept for good belong in memory.Privacy
Indexing runs on Summer’s servers. Your file chunks and their search data are stored so search can run over them. Privacy Mode, on paid plans, stops your code being used to train models. See Security Overview.Related
AI Operations
What the agent can do inside your project
Memory
How Summer remembers your decisions across chats
Need help? Ask in Discord first. That is where you get the fastest reply and support. For concrete help, email support@summerengine.com or founders@summerengine.com.

