Cloudeval AI

Cloudeval CLI

Your cloud, in the terminal: evaluated, reported, and agent-ready.

Cloudeval CLI turns ARM templates, GitHub-hosted IaC, and live Azure context into cost, architecture, and Well-Architected signals. Use it as a terminal UI, a scriptable automation client, or an MCP server for Codex, Cursor, Claude, VS Code, and any stdio JSON-RPC client.

Why Use It

Install

Node.js 20+ users can install from npm:

npm install -g @ganakailabs/cloudeval-cli

cloudeval --help

macOS, Linux, WSL2, Git Bash, and PowerShell 7+ on Windows or Linux can use the standalone release installer:

curl -fsSL https://cli.cloudeval.ai/install.sh | bash

irm https://cli.cloudeval.ai/install.ps1 | iex

Then reload your shell and sign in:

source ~/.bashrc   # or: source ~/.zshrc

cloudeval login cloudeval status cloudeval chat

Device login goes through cloudeval.ai and always asks the browser auth provider to show the account chooser, so users can choose the intended work email even when another account is already signed in. No local Azure app registration is needed for normal CLI use.

Installer behavior and controls

The installer:

• downloads checksum-verified GitHub release assets and installs cloudeval;
• creates the eva and cloud aliases on non-Windows platforms;
• can install shell completions for bash, zsh, and fish;
• can offer concise MCP setup for detected Codex, Claude Desktop, Cursor, and VS Code clients, skipping clients where Cloudeval MCP is already configured and avoiding prompts when only manual-only setup remains;
• asks whether to share limited CLI telemetry, defaulting to yes; declining writes telemetry.enabled=false;
• explains credential setup but does not create access keys or write secrets into MCP client config;
• shows compact labeled progress bars in interactive terminals;
• uses connect/stall timeouts so slow CDN transfers fail clearly.

Useful controls:

curl -fsSL https://cli.cloudeval.ai/install.sh | CLOUDEVAL_INSTALL_AGENT_SETUP=0 bash

curl -fsSL https://cli.cloudeval.ai/install.sh | CLOUDEVAL_INSTALL_MCP_CLIENTS=codex,cursor bash curl -fsSL https://cli.cloudeval.ai/install.sh | CLOUDEVAL_TELEMETRY=0 bash

$env:CLOUDEVAL_ASSUME_YES = "1"

irm https://cli.cloudeval.ai/install.ps1 | iex

The bash installer can also detect agent clients and offer MCP setup. The PowerShell installer installs the verified binary, yoga.wasm, license notices, PATH, and optional PowerShell tab completions. Run cloudeval mcp setup afterward when you want MCP client configuration.

Telemetry

Cloudeval CLI sends curated custom events to Azure Application Insights by default. Events cover command family, success, duration, safe option enums, CLI version, Node/runtime version, OS major version, architecture, install source, update/install outcomes, MCP tool names, and TUI launch/exit metadata. After login, events may include the signed-in email and first/last/full name.

Telemetry never sends raw prompts, command output, tokens, local paths, project or resource identifiers, account/session/tenant identifiers, cloud resource names, stack traces, or raw error messages. Disable or re-enable it anytime:

cloudeval config set telemetry.enabled false

cloudeval config get telemetry.enabled --format json cloudeval config set telemetry.enabled true cloudeval config unset telemetry.enabled

Environment overrides take precedence for a single run:

CLOUDEVAL_TELEMETRY=0 cloudeval status --format json

CLOUDEVAL_TELEMETRY=1 cloudeval --help

Update later with:

cloudeval update --check

cloudeval update --yes

After an update, restart or reload configured MCP clients when you are ready to load newly exposed Cloudeval tools, resources, or prompts. Cloudeval does not restart Codex, Claude, Cursor, VS Code, or other MCP hosts automatically.

Uninstall local installer-owned artifacts while keeping Cloudeval config, sessions, and auth by default:

cloudeval uninstall --dry-run

cloudeval uninstall --yes cloudeval uninstall --yes --remove-config # also removes ~/.config/cloudeval npm uninstall -g @ganakailabs/cloudeval-cli # if installed through npm

Start Here

cloudeval                         # Terminal UI

cloudeval tui --graph-diagram ascii cloudeval ask "Summarize my cloud risk" --format json cloudeval agent "Find cost and architecture risks" --format json cloudeval agents list cloudeval agents run cost --project --format json cloudeval recipes list cloudeval projects list cloudeval uninstall --dry-run cloudeval projects graph insights --focus impact --resource --format json cloudeval validate template --template-file template.json --parameters-file parameters.json --rule --details --wait --progress stderr --wait-timeout 600000 --format json cloudeval validate tests --template-file template.json --parameters-file parameters.json --wait --progress stderr --wait-timeout 600000 --format json cloudeval rules search "public network" --format json cloudeval reports list cloudeval actions list --type architecture,cost,unit-tests --format json cloudeval actions open --print-url --no-open cloudeval review --repo owner/repo --ref feature/infra-change --commit-sha --github-checks --sarif --output cloudeval-review --format json --non-interactive cloudeval capabilities --format json cloudeval doctor --deep

Full docs: Get started with the CLI and CLI command reference.

Inside the Terminal UI, use the Thread control or /thread to switch open chat sessions, recent Cloudeval chat threads, and local CLI sessions. /thread new starts another independent open session, and /open jumps to the same chat thread in Cloudeval when the active session has a thread id. Roomy terminals show a context rail with project, thread, model, mode, profile, report artifact chips; narrower terminals keep the chat first and expose the same controls through the composer and slash commands. Typing / opens a bottom command completion strip; use Tab or Up/Down to move, Right to accept the ghost text, and Enter to choose the highlighted command. Streaming work appears as a task ledger in the thread, and the bottom composer stays docked so prompt entry does not compete with the transcript. Grounded answers show numbered citations and a Sources section instead of raw [S_tool_...] tags, with citation numbers highlighted inline; /copy copies the latest assistant response and /download writes a Markdown transcript with the same references. Graph insight blocks render as bordered terminal cards instead of exposing raw graph-insight markers; when a card contains a conservative Mermaid flowchart, --graph-diagram auto renders a terminal diagram in roomy TTYs, unicode or ascii force a mode, and off keeps the Mermaid source fallback. Unsupported Mermaid syntax stays visible as source instead of breaking the transcript. Negotiated chat visualizations render directly in the TUI: line/area trends use Unicode plots; bar, column, histogram, pie, doughnut, radar, and polar data use width-aware bars; scatter and heatmap data use compact terminal grids; unsupported chart families use the artifact's table fallback. Mermaid flow edges render as an edge list, with bounded Mermaid source as the fallback when no edges can be extracted. HITL approval prompts require an explicit option selection or typed answer; pressing Enter on a blank approval prompt does not choose the recommended option. Project and Connection tabs show a selected-item detail pane for backend fields, report coverage, sync state, and linked records; use J/K or Up/Down on Projects and Connections to move the selected row, then Enter to confirm it. The billing header separates credits left from observed credits used so usage does not look like the current budget. Use the Profile control or /profile cost to run the current prompt with an Agent Profile; selecting a profile switches the TUI to Agent mode, and selecting Ask mode clears the profile back to the default chat flow. Starter prompts stay hidden until you run /starter. Press Esc from the prompt to leave text editing so tab, arrow, and number shortcuts move through controls and tabs; type again to resume editing. Busy loaders and the input cursor can be disabled with --no-anim. The banner details include the logged-in user. Focused controls and the active top tab use the shared warm banner-yellow accent, with the active tab filled across its full button interior.

The CLI advertises cloudeval.visualization/v1, flint-v1, and mermaid-v11 capabilities on chat requests. The backend compiles chart intent; the CLI validates the bounded artifact and renders terminal-safe output without a browser or native SVG helper. ask and agent JSON results include data.visualizations when present, and NDJSON emits a visualization event as well as including the artifacts in the final `