Ona UI Capabilities

Plain-language overview of what the Ona UI can do today (web and Electron desktop app).

Use this doc when you want a quick answer to: "What is possible from the UI without using 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)

What you can do:

  • talk directly to Solin
  • submit missions and follow-up instructions
  • watch live mission progress
  • view active/pending work at a glance

Best for:

  • daily interaction with Solin
  • starting and steering ongoing missions

2) Jobs

What you can do:

  • list and filter jobs by status
  • open job details and final results
  • view mission progress and execution context
  • cancel or re-run jobs (where enabled)

Best for:

  • operational visibility and debugging mission outcomes

3) Approvals

What you can do:

  • review pending sensitive actions
  • approve or reject actions
  • inspect approval history and audit context

Best for:

  • human-in-the-loop control and safety

4) Squad

What you can do:

  • view available agents/roles
  • enable or disable specialist agents
  • create custom agents (where configured)
  • adjust local persona behavior

Best for:

  • shaping how Solin delegates work

5) Memory

What you can do:

  • view/edit long-term memory content
  • review daily memory notes
  • search memory entries
  • manage "About me" user-memory style facts

Best for:

  • continuity and personalization quality

6) Knowledge

What you can do:

  • ingest documents into RAG knowledge
  • browse indexed sources
  • search ingested knowledge
  • re-ingest or refresh sources

Best for:

  • grounding missions in your own documents/data

7) Settings

What you can do:

  • configure models/providers
  • connect channels and integrations
  • manage secrets/lockbox-backed credentials
  • configure advanced runtime behavior
  • access A2A and integration settings

Best for:

  • system setup and operational configuration

8) Scheduler

What you can do:

  • create recurring mission jobs
  • enable/disable scheduled tasks
  • edit or remove cron-style tasks
  • review next-run behavior

Best for:

  • automation and repeat workflows

9) Todos and Follow-ups

What you can do:

  • add/manage todos
  • track pending vs completed work
  • schedule follow-ups from missions
  • monitor upcoming follow-up actions

Best for:

  • workflow continuity after mission completion

10) IDE (/ide)

What you can do:

  • browse workspace files
  • edit code in-browser
  • run developer-agent tasks through terminal bridge
  • chat with developer flow in the same screen

Best for:

  • build/fix/refactor loops with live agent assistance

Channels in UI Context

The UI supports channel-centric operation, including:

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

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

Mobile Capability

UI is mobile-capable for core operations:

  • mission chat and follow-ups
  • status checks and job review
  • approval handling
  • settings access for common tasks

PWA/mobile browser usage is 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/operator power flows

Recommended pattern:

  • use UI for daily operations and oversight
  • use CLI/API for advanced automation and deep ops

Related Docs