Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.skrmir.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Web UI Guide

Web UI provides visual operations while staying aligned with the future CLI control-plane boundary.

​
Planned CLI/UI Start Example (Not Yet Implemented)

The repository does not currently ship a command such as aios ui serve. 
aios ui serve --host 0.0.0.0 --port 3000

​
Main Areas

  • Dashboard: health, utilization, and alert summaries
  • Infrastructure: cluster, apps, rollout, and logs
  • Agent Workspace: workflows, runs, statuses, and outputs
  • Settings: credentials, integrations, and governance policies

​
Core Actions

  • trigger application deployments from UI using CLI-equivalent parameters
  • inspect the visual execution tree and outputs for agent runs
  • retry failed tasks or trigger rollback directly from failure views

​
Current Runtime Mode Note

Current Web UI console-related read surfaces need to be interpreted in the context of the control-plane runtime mode:
  • if the control plane is running in bootstrap, the service can still start normally, but read surfaces that depend on durable task state should not be treated as fully available
  • if the control plane is running in persistent and PostgreSQL is wired, those read surfaces enter the currently shipped persistent capability set
For operators, this means an unavailable overview or task-detail surface in bootstrap should not be interpreted as “the system simply has no data yet.” It means the current runtime mode is a non-persistent bring-up path.

​
CLI + UI Collaboration

Use UI for broad monitoring. Once a CLI exists, use it for precise automation and incident response.