Operate and observe with confidence—terminal or dashboard
CLI for fast local control. GUI (planned) for live plans, approvals, artifacts, and logs.
What GUI & CLI does
GUI & CLI provide operator interfaces for controlling and observing the assistant. The CLI offers fast local control with scriptable commands. The GUI (planned) will visualize live plans, approvals, artifacts, and logs in a dashboard.
CLI capabilities Available
- Create and run tasks
- Approve pending steps
- Inspect audits and artifacts
- Scriptable for automation
GUI capabilities Planned
- Live plan DAG visualization
- One-click approvals
- Artifact preview and download
- Real-time logs and status
Who benefits from GUI & CLI
Individuals
One-click approvals and simple dashboards
Teams & Managers
Shared visibility and status
Developers & IT
Fast local control and scriptable CLI
Security & Compliance
Role-based controls (planned)
How it works
CLI: Create and run tasks
Use mcp task create to start a new task. The CLI wraps the orchestrator API.
CLI: Approve pending steps
Use mcp approve to approve or reject pending steps.
CLI: Inspect audits and artifacts
Use mcp logs to view audit logs and mcp artifacts to download outputs.
GUI (planned): Visualize and control
The GUI will visualize plan DAGs, show real-time status, and provide one-click approvals.
Example workflows
Create and approve a task via CLI
CLImcp task create "Summarize weekly notes"
- Task created; orchestrator plans steps
mcp status— view progressmcp approve— approve pending stepsmcp artifacts— download results
Task completed; artifacts downloaded
Inspect audit logs via CLI
CLImcp logs --task-id 123
- Retrieve audit log for task 123
- Display steps, approvals, and timestamps
Full audit trail displayed in terminal
Visualize live plan in GUI (planned)
GUI (planned)Open GUI dashboard
- View live plan DAG with step status
- Click to approve pending steps
- Preview artifacts inline
- View real-time logs
Full visibility and control in one dashboard
Technical details
Configuration
AUTH— local by default (SSO/SAML planned)PORTS— CLI and GUI portsTLS— optional (planned)
Observability
- Real-time task status
- Approval latency metrics
- Artifact download counts
Security posture
Local access by default
CLI and GUI run locally. No network exposure unless explicitly configured.
SSO/SAML (planned)
Team access with SSO/SAML and role-based permissions.
Audit logs
All CLI and GUI actions logged for compliance.
TLS (planned)
Optional TLS for GUI connections.
Roadmap & status
Current features
- CLI for task creation and approval
- Audit log inspection
- Artifact download
Coming soon
- GUI with live plan visualization
- Role-based permissions and SSO/SAML
- Real-time status updates
Frequently asked questions
Can I script CLI commands for automation?
Yes. All CLI commands can be scripted for automation and CI/CD integration. Use exit codes and JSON output for programmatic control.
When will the GUI be available?
The GUI is planned for a future release. Check the roadmap for updates. The CLI provides full functionality today.
Does the GUI require network access?
No. The GUI will run locally by default, just like the CLI. Network access is optional for team features (SSO/SAML).
Can I use the CLI and GUI together?
Yes. Both interfaces control the same orchestrator. You can create tasks in the CLI and approve them in the GUI (when available).
Are there role-based permissions?
Role-based permissions are planned for team deployments. Today, access is local-only.
Can I export audit logs from the CLI?
Yes. Use mcp logs --export to export audit logs in JSON format.
Does the GUI support dark mode?
Yes. The GUI will support both light and dark modes with system preference detection.