The editor is the design and validation environment for an App. Most work starts in Resources, is edited in the WorkArea, reviewed in Properties, and accepted through Problems, Build, and a runtime page.
When to use this page
- You cannot find a Page, Graph, Object, Script, Safety configuration, PLC resource, or Asset.
- You are unsure where to edit the current selection.
- AI, Git, or an external editor changed a file and you need to handle refresh or conflict state.
- You need the Save, diagnostics, Build, Start, Debug, or AI entry point quickly.
Editor areas
| Area | Main content |
|---|
| Navbar | App menu, Runtime target, Build, Start, Debug, AI, and Inspector toggle |
| Activity Bar | Resources, Files, Screen, and Git; Settings at the bottom opens current-App settings |
| Left panel | The resource tree, file tree, current Page widget tree, or Git status for the active Activity |
| WorkArea | Page, Component, Graph, Script, Safety, PLC, Vision, and text tabs with draggable splits |
| Properties | Properties for the selected Page, Widget, Object, Graph node, or other item |
| Problems / Console | Design and build diagnostics plus runtime logs received by the active connection |
| AI Command Center | Current-App AI sessions in fullscreen or WorkArea-tab form |
Activity Bar entry points
| Entry | When to use it |
|---|
| Resources | Find Pages, Components, Graphs, Scripts, Safety, Assets, and enabled Vision or PLC resources by purpose |
| Files | Inspect the complete App tree and import, move, rename, or delete files |
| Screen | Inspect the Widget hierarchy of the current Page or Component and select covered or nested widgets |
| Git | Review changes, commit, and synchronize the current App repository |
| Settings | Configure the home page, modules, Variables, Recipes, Queries, i18n, App users, and Plugins |
Resources is the default entry point. Use the context menu of the appropriate section to create a Page, Component, Graph, or Script. Switch to Files when you need the actual file path.
Common operations
| Goal | Action |
|---|
| Open a resource | Double-click it in Resources; selecting an Object or configuration item updates Properties |
| Edit properties | Select the target on the canvas, in Screen, or in Resources, then use Properties |
| Save the current tab | Cmd+S on macOS or Ctrl+S on Windows / Linux |
| Reload from disk | Use Refresh in the current tab; Theseus asks before discarding unsaved work |
| View side by side | Drag a WorkArea tab to another edge to create a tab group |
| Test Page interaction | Switch to View mode, or hold Alt while clicking the real Widget in Edit mode |
| Open AI | Use the AI button in the Navbar or Cmd/Ctrl+I |
| Locate a problem | Open Problems, search by code, message, or path, then select the row |
| Read runtime output | Open Console for live logs received by the current debug connection |
Page and Component grids, selection outlines, and guides belong only to the editor. They do not appear on a runtime page. WorkArea splits do not reset canvas zoom automatically; use Fit to window in the zoom menu when needed.
Save and external changes
- An unsaved tab shows a status marker. Closing the tab or leaving the editor requires confirmation.
- When AI, Git, or an external editor changes an open file without a local draft, the tab refreshes from disk.
- If the same tab has unsaved work, Theseus keeps the draft and reports an external-change conflict. Compare the versions before overwriting either one.
- A file event caused by the tab's own Save does not reset its undo history.
- Save updates authoring state only. Graph, Script, PLC, and runtime-model changes still need Build, Start, or Debug validation.
Problems and Console
| Panel | Purpose |
|---|
| Problems | Errors and warnings from Pages, Components, Graphs, Scripts, Safety, PLC, and Build; select a row to return to the source |
| Console | Live runtime logs and fault summaries received after the debug connection is established |
Both panels include an AI analysis action. It sends the current warnings and errors to AI as read-only analysis context; selecting it does not automatically change the App.
Common shortcuts
| Action | macOS | Windows / Linux |
|---|
| Save | Cmd+S | Ctrl+S |
| Close current tab | Cmd+W | Ctrl+W or Ctrl+F4 |
| Next / previous tab | Ctrl+Tab / Ctrl+Shift+Tab | Same |
| Tab 1–8 | Cmd+1–8 | Ctrl+1–8 |
| Last tab | Cmd+9 | Ctrl+9 |
| Open or close AI | Cmd+I | Ctrl+I |
Key rules
- The Runtime target in the Navbar controls deployment and execution only. It does not change local Resources, Files, Git, or AI sessions.
- Properties follows the current selection. With multiple Widgets selected, it shows only fields that are safe to edit in bulk.
- Page View mode is for interaction testing; it does not prove that a new version was deployed to the target.
- Resolve blocking Problems before Build or runtime validation.
- Do not load new build outputs while the App is Running, Debugging, or Paused. Stop first.
How to validate an edit
- Save and confirm that the tab no longer shows unsaved state.
- Review the resource location and key fields in Resources and Properties.
- Confirm that Problems has no blocking error.
- Run Build after Graph, Script, or PLC changes.
- Confirm the Runtime target, then Start or Debug.
- Use a runtime page to verify what an operator actually sees and triggers.