Skip to main content
Set up CloudEval in a few minutes so you can run your first architecture analysis without setup friction.

​
Why it matters

Most onboarding issues come from auth and environment mismatches. This page gives a verified baseline first.

​
Quick example

curl -fsSL https://raw.githubusercontent.com/ganakailabs/cloudeval-cli/main/scripts/install.sh | bash
cloudeval --help
Expected output: The command list includes chat, ask, login, logout, and banner.

​
Step-by-step instructions

​
1. Install CLI

curl -fsSL https://raw.githubusercontent.com/ganakailabs/cloudeval-cli/main/scripts/install.sh | bash

​
2. Authenticate

cloudeval login
This starts device login in your browser.

​
3. Verify with a command

cloudeval ask "What projects can I access?" --json

​
Code examples

# API key path (non-interactive)
export CLOUDEVAL_API_KEY="<your_api_key>"
cloudeval ask "Summarize active report issues" --json

# Target a specific project
cloudeval ask "List critical findings" --project <project_id> --json

​
Expected output

  • Successful login stores auth state locally.
  • ask returns text or JSON depending on flags.
  • If auth is missing, CLI prompts for cloudeval login.

​
Common mistakes

  • Mixing stale API keys with interactive login state.
  • Forgetting to pass --project for project-scoped checks.

​
Tips / best practices

  • Use --json for scripts and chat for interactive exploration.
  • Keep auth mode explicit in CI.
  • Add a quick smoke test before long pipelines.
Last modified on March 5, 2026