The agent you talk to
Everything starts with the main agent. It is the one reading your messages, asking questions when something is unclear, and writing the plan for what to build next. Think of it as the lead on your project. The important thing to know is that the main agent spends most of its time thinking and directing, not typing out code itself. When you ask for a jump mechanic or a new enemy or a whole game, it works out what needs to happen, breaks it into pieces, and hands those pieces to the specialists best suited to each one. That keeps the planning focused and lets the hands-on work run cheaply and in parallel. You will sometimes see it stop to consult an advisor before committing to a plan. That is a good sign. It means the agent hit something tricky and wanted a second opinion before spending your credits building the wrong thing.The specialists
Summer keeps a team of specialist agents, each shaped for one kind of work. You do not pick them. The main agent chooses based on the task, and often runs several at once. Here is the team in plain terms. A researcher reads your project and answers questions about it. When the main agent needs to know how something is wired before it changes anything, this is who it asks. Read only, fast, and cheap. A builder does the hands-on construction. It writes scripts, edits scenes, sets the main scene, binds input actions, and runs compile checks. When you ask for a new game or a feature slice, this is who builds it end to end. An asset maker creates art, models, audio, and animations, then hands them back for you to review before anything lands in your project. A verifier checks that things actually work. It traces the scene, scripts, and running game to confirm a feature does what it should, and reports back honestly when something is broken. An advisor is the one the main agent turns to when it is stuck or unsure. It reasons more carefully than the others and is happy to say when it does not know, which is exactly what you want from a second opinion. You can also use Design Mode to click nodes or draw on your 2D and 3D viewport while this team works. The viewport bar feeds into the same chat the orchestrator supervises. We keep the exact lineup and the models behind it flexible on purpose, because we are always improving it. What stays the same is the shape. A lead that plans, and specialists that execute.Work runs in parallel
Because the specialists each keep their own focused context, Summer can run several of them at the same time. While one builds your player controller, another can be generating the enemy art, and a third can be researching how your save system works. None of them block the others, and none of them clutter your main chat with the details of their work. You get the finished results stitched back together, not the mess of getting there.You can watch them work
When a specialist is running, you see it live in your chat as its own clean thread. You can follow what it is doing and thinking in real time without it taking over the conversation. When it finishes, it folds a short summary back into the main chat and the details stay tucked away in that thread if you ever want to look. This is the balance we care about. Full transparency when you want it, and a calm, uncluttered chat when you do not.Working with the team
You do not manage the agents directly, but the way you talk to the main agent shapes how well the team performs. Be specific about what you want and why. The clearer your intent, the better the brief the main agent can write, and the better the specialists execute it. If you have a reference image or a particular feel in mind, say so early. If a specialist is heading in the wrong direction, tell the main agent. It supervises the work and can redirect a running specialist mid task, or stop one that has gone off the rails and start fresh with a better approach. You do not have to wait for a bad result to land before course correcting. And when something genuinely does not work, say that plainly. The verifier exists for exactly this, and the main agent would rather run a real check than take its own word for it.When Summer works alone
Not everything needs the full team. For a quick single edit, a direct answer to a question, or a small tweak, the main agent just handles it. Delegation kicks in when the work is bigger than that. A multi step build, art generation, a wide search across your project, or anything that benefits from running several things at once. You never have to decide which path applies. Summer makes that call for you, and you can always nudge it either way.You approve anything risky
Summer keeps you in control of the actions that matter. Pick a permission mode in the composer to set how much runs automatically. Manual approves every edit and generation. Accept edits auto-runs file changes but asks before spending credits. Auto approve (default) runs edits and generation but still blocks destructive actions. Bypass runs everything except hard safety blocks. Shell commands, file deletions, and credit-spending generation respect the mode you chose. The building and editing happen freely when you want speed, and the irreversible steps wait for you when you want control.Related
Design Mode
Click nodes or draw on your viewport to build in the scene
Skills
Teach Summer your way of building and reuse it across every project
Memory
How Summer remembers your decisions across chats
AI Operations
What Summer can do inside your project
Project Intelligence
How Summer indexes and searches your project
Need help or have questions? Reach out at founders@summerengine.com or join Discord.