Project workbench and tool panels
The workbench keeps the conversation and current project artifact together. Its stage can show the conversation, a preview, or both when the layout offers a split view. A tool rail opens a contextual panel; close it to restore more space to the stage.
Conversation and preview
Use Conversation to send follow-up requests and answer Agent questions. Use Preview to inspect the current Web app or Native device rendering. In a Prototype design project, the central artifact is the canvas. The preview selector can expose desktop, tablet, mobile, or device-size presets depending on the project route.
History and tools
Open History to review runs and project checkpoints. The available tool rail can include Review, Layers, Design, Runtime, App tests, Terminal, Git, Data, Integrations, Code, and Agent. A panel appears only when relevant to the route and current project state. For example, a new project may not yet have source for Code, a checkpoint for some testing actions, or an active deployment for operations controls.
Tool availability by route
Web projects can expose Web preview, app tests, data and integration tools, and Web publication. General-purpose Web-hosted projects can expose compatible Web capabilities. Native projects use native-oriented preview and build operations, not Web deployment. Prototype design projects expose Layers and Design tools; Git, Review, or Code can appear when their prerequisites exist. The project route capability is authoritative if a tool is absent.
Access and changes
Your organization role can make the workbench read-only or hide sensitive actions. A disabled action usually indicates a missing prerequisite, active work, or insufficient authority. Read the adjacent status before trying again. Closing a panel does not discard the project or its saved changes.