What problem does it solve? AI agents working with Summer Engine need to decide when to open a visible surface for the user (billing, published games, the scene just built) versus acting silently through API tools, and need a reliable way to open the exact page or editor panel without guessing URLs. ## Core Features & Use Cases - Intent-based navigation: Resolves natural-language intents like "billing", "my games", or "res://player.gd" to the correct Studio web page or editor panel using summer_open. - Act-then-show workflow: Enforces the rule that mutations happen through Summer tools first, and surfaces open only afterward when the user asks to see the result. - Honest result handling: Covers every outcome — opened, login required, engine not running, unsupported op, ambiguous match, not found, open failed, blocked origin — so the agent never claims something opened when it did not. - Use Case: After adding a camera node to a scene, the agent runs the mutation, then calls summer_open with the scene target so the user sees the result in the running editor. ## Quick Start Ask the agent to show your billing page or open the scene it just built, and it will resolve the intent and open the correct Summer surface.
