FRONTIERX AuraOS Documentation

AuraOS User Manual

AuraOS Documentation

From installation and login through chat, 3D viewport, Skill Store, workbench, programming, and file management.

For the current AuraOS release Windows & macOS guide English / 中文
Browse Contents
  1. Download & Install
  2. Connect Aura Daemon
  3. Account & Profile
  4. Level, XP & Quota
  5. 3D Viewport & Devices
  6. Chat
  7. Skills & Personas
  8. Skill Store
  9. Workbench
  10. Programming
  11. File Save & Download
  12. Language Switch
  13. Troubleshooting
01

Download & Install

Download the currently available system package from the AuraOS section on the FrontierX website. macOS uses .dmg; the Windows installer is not yet available — check the download page for current status. Once installed, launch AuraOS from your system application list.

  1. Go to the download page. Open the AuraOS specs & download page and find the Download section.
  2. Choose your system. Download the currently available installer; if Windows shows "coming soon", please wait for the official release.
  3. Complete installation. Follow the system install wizard, then launch AuraOS when finished.
  4. Wait for the service to be ready. The backend service needs to initialize on first launch; the page may briefly show a loading state.
02

Connect Aura Daemon

Aura Daemon is the local service between the AuraOS frontend and the camera, model, skill, file, and robot-control capabilities. Related features only work correctly when the target Daemon is reachable.

Choose a connection target

  • Open the Daemon menu on the right side of the top navigation and select the target you want to use.
  • Local development or desktop installations typically connect to the local Daemon; when connecting to a robot or another device, choose the corresponding target.
  • After switching targets, the WebSocket and device status will connect to the new Daemon.
  • Previously loaded chat history, editor tabs, and Skill Store installation markers may not clear immediately. After switching, refresh the page and recheck history, files, and the Skill Store to confirm the current target.
Connection status affects interaction

When the Daemon is not connected, the chat input will remain disabled, and the camera, skill, file, and control interfaces may also fail to load.

03

Account & Profile

When account services are enabled for the current deployment, "Sign In" will appear in the top navigation. After signing in, chat history, level, XP, quota, and profile are linked to your account.

Sign Up

Switch to Sign Up in the login window, fill in your email, verification code, and password. You can set your display name later in your profile.

Sign In & Reset Password

Sign in with your registered email and password. If you forget your password, you can set a new one via email verification code.

Profile

Click the level badge in the top-right corner to edit your nickname, WeChat ID, birth year, occupation, technical background, and use case.

Sign Out

Choose Sign Out in the profile window. After signing out, locally saved credentials as well as the account and API key configuration in the current Daemon will be cleared, and guest trials for the current browser or IP will not be reopened.

Guest Mode

When account services are enabled but you haven't signed in, plain-text chat and browser voice share 3 guest quota uses. After signing in, you are no longer limited by the 3-use guest quota and can restore your account's chat history, though you remain subject to your account's available service balance.

04

Level, XP & Quota

Your level is automatically calculated from cumulative XP. There are currently 10 levels. The badge in the top-right corner shows your current level; open your profile to see your title, cumulative XP, and progress toward the next level.

Action Current Reward Notes
Daily Check-in +2 XP One successful check-in per day.
First Complete Profile +10 XP Awarded once when birth year, occupation, technical background, and use case are all filled in for the first time.
Publish a Skill (Approved) Default +20 XP Awarded idempotently by the server after the Skill Store PR is merged; actual value subject to service configuration.
05

3D Viewport & Devices

The 3D viewport displays the camera feed, depth map, and Aura model, and provides entry points for media, motion, and haptic glove devices. What's actually available depends on the current Daemon and hardware state.

Switch Preview

  • The main view supports camera, depth map, and 3D model.
  • Click a picture-in-picture window to swap it into the main view; each PiP can be independently closed, restored, and resized.
  • After switching to depth-map main view, you can save a single-frame screenshot or continuously capture 12 frames and save as WebM.

Device Controls

  • The microphone and camera toggles are driven by the current input device state.
  • The speaker slider adjusts media volume.
  • The haptic glove entry supports connect and disconnect, and displays device frame rate and control status.
  • The directional control area sends move and stop commands to the current motion backend.
  • The ASR, VLM, and TTS areas show the current backend type; version and uptime come from the Daemon status.
Check environment safety before controlling the robot

Directional controls and haptic gloves may trigger real robot motion. When connected to a physical robot, check your surroundings and device state first.

06

Chat

Select "Chat" in the top navigation. Type your message and send — Aura returns progress updates, streaming text, and the final result via WebSocket.

Send & Stop

  • Press Enter to send, Shift + Enter for a new line.
  • While a response is in progress, the send button becomes a stop button — click to cancel the current request.
  • The send button is disabled when the input is empty, the Daemon is not connected, or guest quota is exhausted.

Session History

  • Use "New Chat" to start a fresh session; use "History" to open the session list.
  • You can switch between or delete existing sessions; signed-in users' sessions are saved to the Daemon's account namespace.
  • Guest chats are temporary sessions and will not be restored under a signed-in account.

Voice & Code Blocks

  • The voice entry only appears when the browser supports the Web Speech API; after opening the voice panel, if the current device provides EVA Voice, the device-side voice mode is available.
  • EVA Voice is handled by the device-side pipeline; its availability and quota behavior may differ from plain-text or browser voice, subject to the current deployment and device state.
  • Code blocks in responses can be copied; Python, Bash, and Shell code blocks can also be run directly.
  • Choose "Open in Editor" to send code to the Programming area for further editing.
07

Skills & Personas

Skills extend Aura's action or tool capabilities; Personas switch the conversation style and character setting. Both come from projects published to the current Daemon.

  • Expand "Skills" or "Personas" below the 3D viewport. Selecting a Skill pre-selects it for the next conversation.
  • Selecting a Persona immediately sends a switch command to the conversation — it does not wait for the next user message to take effect.
  • The current mode is shown above the chat input.
  • Only one Skill or Persona is active at a time; choose "Restore Default" to exit the current mode.
  • Deletion has no confirmation step and may also remove the corresponding published project and draft of the same name from the Daemon. Back up anything you want to keep first.
08

Skill Store

Select "Skill Store" in the top navigation to browse installable Skills and Personas. The store catalog comes from the AuraOS preset skill registry; installation results are written to the current Daemon. Connecting a GitHub account in the Workbench does not change the store catalog source.

Confirm the current Daemon

The "Installed" and "Update Available" badges on cards come from the installation records saved in the current browser — they are not automatically isolated by Daemon target. After switching Daemons, recheck the target and the actual installation results.

  1. Find a project. Use the search box, Skill/Persona categories, and tags to filter.
  2. View details. Read the name, description, author, version, install count, and other info.
  3. Install or update. Choose Install; for installed projects with a newer version, choose Update.
  4. Use the project. After a successful install, go back to the Skills or Personas area and select it.
  5. Uninstall. Choose Uninstall on an installed project. After the card status updates, if the Skill is still usable in the current runtime, restart the Daemon and check again.
When installation fails

First confirm the Daemon is online, the network can reach the skill registry, and manually compare the minimum AuraOS version in the details against your current version. The UI only displays the minimum version; it will not automatically block incompatible installations.

09

Workbench

The Workbench is for creating and maintaining Skill or Persona drafts. Drafts are saved in the current Daemon's development workspace and are not automatically published to the Skill Store on save.

Create & Edit Drafts

  1. Choose Skill or Persona, enter a name, and create a new draft.
  2. Select a Markdown or code file from the file list on the left.
  3. Edit content in the right-side editor; once unsaved changes appear, click "Save".
  4. An empty draft can create Markdown / Python files, or you can choose "AI Implement" to send an implementation request to the chat.

Publish to Skill Store

  • When account services are enabled for the current deployment, viewing and creating drafts requires signing into AuraOS; submitting a Skill Store PR requires connecting GitHub.
  • The first connection will open the GitHub device authorization page — enter the device code shown to complete authorization.
  • Publishing submits the draft to the Skill Store repository and creates a Pull Request; it does not bypass review and merge directly.
  • The Workbench clearly shows "In Review" and "Merged" statuses; other statuses may show "Publish to Store" again — check the GitHub Pull Request for details.
  • After the Pull Request is merged, the system will automatically attempt to award the publish reward when refreshing the status; no manual claim is needed. The specific XP amount is subject to service configuration and final crediting.
10

Programming

The Programming area combines a chat, project files, and a code editor. You can ask Aura to generate code, or directly open local draft files to continue editing and running them.

Start from Chat

Describe your requirements in the chat area on the Programming page. Code blocks in responses can be copied, run, or sent to the editor.

Editor Layout

Use "Widen" to expand the editor area; use "Focus" to hide other panels. Click the button again to exit; press Escape only exits Focus mode.

Run & Output

The Run button sends the current code to the Daemon for execution and displays stdout, stderr, and exit status in the output area.

Terminal

Terminal mode starts an interactive process via WebSocket, supporting input, stop, and viewing process output.

Python Environment & Dependencies

  • Python files can switch between the two virtual environments vibe_1 and vibe_2 managed by the Daemon.
  • The pip panel is used to view, install, and uninstall third-party packages in the selected environment; when account services are enabled, installing and uninstalling dependencies requires sign-in.
  • C and C++ code depends on the gcc or g++ compiler on the current Daemon host.
Code runs on the current Daemon host

Running code and terminal commands launches processes directly on the host where the current Daemon resides; when connected to a remote Daemon, the remote host is affected. Python virtual environments only isolate dependencies — they are not security sandboxes. Only run trusted code.

11

File Save & Download

Saved programming files are managed by the current Daemon's Vibe file interface. After switching Daemons, refresh the page and reopen the file tree to confirm you're viewing files on the new target.

Save Chat-Generated Code

  1. Choose "Open in Editor" on a code block in a chat response.
  2. In the Programming area, choose "Save as Draft", then select an existing folder or create a new one.
  3. Enter a filename and save. Once saved, the file appears in the project file tree.

Manage Project Files

  • You can create new folders and files, open files, modify content, and save.
  • Files can be renamed and moved to other folders via drag and drop.
  • Use the folder download button to package the entire project folder as a ZIP and download it to your computer.
  • Closing a saved editor tab only closes the current view — it does not delete the file from the Daemon.
  • Code that was just opened from a chat but hasn't been "Saved as Draft" yet is a temporary tab that only exists in the current page memory; closing the tab or refreshing the page will lose this content. After switching Daemons, even if the tab is still displayed, it does not mean the content has been saved to the new target.
12

Language Switch

The top navigation supports Chinese and English. After switching, the interface text updates, and Aura's reply language setting is also synced to the current Daemon. Existing chat messages, file contents, and user input are not automatically translated.

13

Troubleshooting

Symptom What to Check
Page loads for a long time or input shows "Connecting" Confirm Aura Daemon is started and the correct target is selected in the top Daemon menu. The first launch may need to wait for initialization to complete.
Camera or microphone unavailable Check system permissions, device contention, and the input device status returned by the Daemon; entries remain unavailable when no corresponding hardware is present.
Cannot continue guest chat Guest trial limit is 3 uses; please register or sign in to continue.
Skill install or uninstall fails Confirm the Daemon and skill registry are reachable; after refreshing the store list, recheck the installation status and error message.
Code cannot run or terminal cannot start Confirm the Daemon version supports the code execution interface, and check that the language, Python environment, and dependencies are correct.
History or files change after switching targets Device status and subsequent requests will use the new Daemon; existing history, editor tabs, and store markers may temporarily retain old state. Refresh the page and reopen relevant content to verify.