Sign-in, App Hub, and the editor
The most common first-use confusion is not a button; it is “where am I signed in?” Theseus separates editor cloud services, runtime-target administration, and business permissions inside an app.
Remember this table
| Account | When it is used | What it does not mean |
|---|---|---|
| Editor Qixin account | Qixin code hosting, online License, AI entitlement, and other cloud services | It does not automatically sign in to any Runtime target |
| Runtime target account | Enter the target runtime; a User can start deployed apps, while an Admin can build, upload, debug, and manage from the editor | It is not an operator identity inside an app |
| App user | Open protected runtime pages and apply page or widget permissions | It does not grant editor or target-management access |
See Three account domains and permissions for the complete role matrix.
App Hub
The desktop app opens App Hub first. App Hub is used to:
- Create, import, and register local apps
- Open the editor or runtime page
- View app status
- Open system settings and learning resources
Creating and editing a local app does not require a Qixin sign-in. When a cloud service is needed, the account menu or the specific action prompts you to sign in.
Enter the editor
Double-click an app card in App Hub, or choose the editor action from the card menu.
The main editor entries are:
- Resources: project assets such as Pages, Components, Graphs, Scripts, Vision, Safety, PLC, and Assets
- Files: workspace files organized by path
- Interface: page and interface-related tools
- Git: version control for the current app
- Settings: General, Variables, Recipes, Queries, I18n, Users / Roles, and settings for enabled modules
- WorkArea: tabs for Pages, Graphs, PLC, Safety, Vision, and text files
- Problems / Console: diagnostics, build information, and runtime messages
- AI Command Center: AI inspection and authoring for the current app
The editor can open before a Runtime target is connected. Target authorization is required only for runtime, debugging, deployment, or target-management operations.
Return to App Hub
Select the logo or app name in the upper-left corner of the editor, then choose the return-to-App-Hub action. If there is unsaved work, save it or discard the draft when prompted.
Open a runtime page
- Confirm that the app has a home page.
- Select Open runtime page on the app card.
- If the app is not running, follow the on-screen startup flow.
- If the page requires a business identity, sign in with an app user belonging to that app.
An on-site terminal can also use Player to open runtime pages served by RuntimeHost. Player does not include the editor. See Build, remote target, and Player for setup and delivery.
Common misunderstandings
- A successful Qixin sign-in does not authorize the current Runtime target.
- Runtime target Admin access does not grant business roles inside an app.
- Selecting a remote Runtime target does not move the local editor or workspace to that machine.
- Saving a Page updates project assets. Whether the running instance changes depends on the resource type and the next explicit Start, Debug, or load action.
Continue with Your first AI-assisted app, or go directly to Connect a Runtime target.