Skip to main content

Use Theseus Player on a site terminal

Theseus Player is the runtime entry point for an operator terminal. It opens a Page already delivered to a Runtime target and remembers the Page assigned to that terminal. Player has no project editing, Build, or Deploy capability and is not a project backup.

Before you start​

  • The App has been built to the correct Runtime target and has a Home Page.
  • A target Admin has started the App to Running according to the site plan. A terminal using User cannot start a Stopped App.
  • You have a plain HTTP or HTTPS target address. Use trusted HTTPS at a remote site.
  • A target account is ready for the terminal. When Pages use business roles, the required App user is ready as well.
  • Delivery staff have verified the Player version, source, and installer signature.

Configure Player​

  1. Start Theseus Player.
  2. Enter the complete Runtime target address, such as https://runtime.example.com. Include only the scheme, host, and port. Do not append credentials, query parameters, an API path, or a Page path.
  3. Select the interface language.
  4. Leave runtime-page AI disabled when it is not required. To enable it, enter the model-service address and API key, refresh the model list, and choose a model. Refresh again after the address or key changes.
  5. Select Save and connect, then wait for Player to check the connection and open the runtime page.

If the terminal cannot store model credentials securely, Player refuses to save the AI configuration. Do not work around this by placing a shared key in an ordinary file or distributing it to unrelated terminals.

Sign in and bind a Page​

  1. Sign in to the runtime page with a Runtime target account.
  2. Confirm that the current App is Running. When it is Stopped, a target Admin must verify site conditions and use Start. A User terminal cannot start it.
  3. Open the App Home Page or the Page that this terminal should show continuously.
  4. If the App uses business roles, sign in or switch to the actual operator with the corresponding App user.
  5. After the Page opens successfully, Player remembers the current binding.
  6. Exit and restart Player. Confirm that the terminal returns directly to the bound Page.

The Runtime target account grants entry to the runtime surface and state viewing. App user identifies the actual operator. See Runtime target accounts and permissions for the complete boundary.

Site acceptance​

  • The terminal connects to the approved Runtime target with the correct address and certificate
  • Target User can view the Running App but cannot Start, Debug, or Stop it
  • Home and the terminal-specific Page open correctly
  • App user sign-in, sign-out, and role restrictions match operator responsibilities
  • Player returns to the same bound Page after restart
  • Layout, fonts, touch input, scanning, and keyboard input work on the physical terminal
  • Network loss, target restart, and reconnection paths have been tested
  • Normal, boundary, fault, recovery, and shutdown scenarios have acceptance records
  • If runtime-page AI is enabled, the model works and sensitive calls still require human confirmation
  • Owners have approved site accounts, certificates, License, networking, backup, and recovery

Change the target or Page​

To assign the terminal to another target or Page:

  1. Open Reconfigure in Player.
  2. Verify and save the new Runtime target address.
  3. Sign in to the target again.
  4. Open the new target Page and allow Player to record the new binding.
  5. Restart Player and confirm that the old target and Page no longer open.

Common issues​

SymptomCheck and recovery
Cannot connectCheck the address, DNS / IP, port, network, and certificate. Do not append an API or Page path
Signed in but no App is visibleConfirm that an App is delivered to the target, Home exists, and the App is Running
User sees Stopped but cannot startThis is the intended permission boundary. Start through a controlled Admin process
The Page asks for another sign-inThis is App user sign-in for operator identity and business roles; it is separate from the target account
Restart does not return to the PageReconfigure the target, open the Page to bind, and verify again after restart
AI configuration cannot be savedConfirm that secure credential storage is available on the terminal; do not bypass it with a plaintext file
The Page works on the development computer but not the terminalCheck physical resolution, scaling, fonts, touch input, networking, and external-equipment conditions

Security requirements​

  • Prefer target User for operator terminals and do not retain Admin credentials on them.
  • Connect only to approved target addresses and never bypass HTTPS certificate checks.
  • Player is for runtime operation. Preserve project source and recovery backups through a separate delivery process.
  • Being able to open a Page does not prove equipment actions are safe. Accept interlocks, emergency stops, and safety controllers independently.

Next steps​