UI Guide

Ona UI
Capabilities

Plain-language overview of what the Ona UI can do today across web and Electron desktop. Use this page when you want a quick answer to what is possible from the UI without terminal or direct API calls.

Core Principle

Ona is designed so users can run day-to-day operations from UI surfaces, not only from CLI/API.

Web and Electron should stay functionally aligned.

Main UI Surfaces

1) Mission Control (Dashboard/Chat)

  • Talk directly to Solin and submit missions or follow-up instructions.
  • Watch live mission progress and active or pending work.
  • Best for daily interaction and steering ongoing missions.

2) Jobs

  • List and filter jobs by status, and open job details/results.
  • View mission progress and execution context.
  • Cancel or re-run jobs where enabled.

3) Approvals

  • Review pending sensitive actions and approve or reject.
  • Inspect approval history with audit context.
  • Best for human-in-the-loop safety control.

4) Squad

  • View available agents and roles.
  • Enable or disable specialists and create custom agents where configured.
  • Adjust local persona behavior and delegation style.

5) Memory

  • View/edit long-term memory and daily notes.
  • Search memory entries and manage "About me" facts.
  • Best for continuity and personalization quality.

6) Knowledge

  • Ingest documents into RAG knowledge.
  • Browse indexed sources, search knowledge, and refresh sources.
  • Best for grounding missions in your own data.

7) Settings

  • Configure models/providers and channels/integrations.
  • Manage secrets/lockbox-backed credentials and advanced runtime behavior.
  • Access A2A and integration settings.

8) Scheduler

  • Create recurring mission jobs and toggle scheduled tasks.
  • Edit or remove cron-style tasks and review next-run behavior.
  • Best for repeat automation workflows.

9) Todos and Follow-ups

  • Add/manage todos and track pending vs completed work.
  • Schedule mission follow-ups and monitor upcoming actions.
  • Best for workflow continuity after mission completion.

10) IDE (`/ide`)

  • Browse workspace files and edit code in-browser.
  • Run developer-agent tasks through terminal bridge.
  • Chat with developer flow in the same screen for build/fix/refactor loops.

Channels in UI Context

  • Telegram
  • WhatsApp
  • Signal
  • Discord
  • Web chat (always available)

From UI, users can configure channels, test connectivity, and run missions through them while monitoring outcomes in Jobs and Approvals.

Mobile Capability

  • Mission chat and follow-ups.
  • Status checks and job review.
  • Approval handling.
  • Settings access for common tasks.

PWA and mobile browser usage are supported for chat-first workflows.

What UI Is Best At

  • Fast mission interaction with Solin.
  • Transparent job execution visibility.
  • Safe approvals and governance.
  • Non-technical configuration through Settings.
  • Bridging chat operations with structured mission tracking.

Current Practical Limits

Some advanced workflows are still stronger in CLI/API:

  • Low-level infrastructure diagnostics.
  • Bulk automation scripts.
  • Certain developer or operator power flows.

Recommended pattern: use UI for daily operations and oversight, and use CLI/API for advanced automation and deep ops.

Related Docs