Skip to main content
CloudEval has two terminal modes: an interactive terminal UI for humans and explicit commands for scripts, agents, and CI jobs.
CloudEval terminal UI chat workspace with reasoning progress, project context, model, mode, input controls, and account status

The terminal UI opens directly into a project-aware chat workspace with starter prompts, project context, model, mode, and status controls.

​
When to use the terminal UI

Use the terminal UI when you want to stay in a terminal but still inspect CloudEval interactively.
CloudEval terminal UI overview tab showing plan, credits, projects, connections, reports, and activity

The overview tab gives a fast terminal-native read on projects, report status, connection health, and recent activity.

The terminal UI is useful for:
  • browsing projects
  • jumping into project reports
  • reviewing chat or help context
  • opening exact app pages from a project-oriented terminal session
Do not parse terminal UI output in automation. Use explicit commands with --format json instead.
CloudEval terminal UI reports tab showing report status, score, attention count, run commands, and project report shortcuts

The reports tab keeps architecture, cost, unit test, and shareable report status visible without leaving the terminal.

CloudEval terminal UI billing tab showing plan, credits, billing status, subscription controls, and customer portal actions

The billing tab shows plan, credits, subscriptions, and customer portal actions for local account checks.

​
When to use explicit commands

Use explicit commands when another tool needs predictable output.
CloudEval CLI terminal output showing version, MCP doctor JSON, toolsets, tools, resources, prompts, and project report status JSON

JSON mode keeps CLI output predictable for scripts, agents, and CI jobs.

This mode is better for:
  • CI jobs
  • MCP-adjacent automation
  • shell scripts
  • local agents
  • repeatable report generation
  • saving output to files

​
Output rules

For machine-readable commands:
  • stdout is the data channel
  • stderr is for prompts, progress, warnings, and browser-open messages
  • --output <file> writes durable artifacts when supported
  • --profile <name> keeps defaults scoped to one agent or workspace

​
Good defaults for automation

Use those checks before relying on a local CLI install in automation.

​
Next step

Use CLI command reference for the full command surface, or MCP client setup when an agent should call CloudEval through MCP instead of shell commands.
Last modified on June 22, 2026