vijil-console

CLI for the Vijil AI trust platform. Manage agents, evaluations, evolutions, and more from the command line against a Vijil Console deployed in your VPC.

Install

pip install vijil-console
# or isolated:
pipx install vijil-console

Connecting to a deployed environment

The CLI talks to the Vijil Console nginx gateway — the single load balancer that routes to all backend microservices. You need one URL: the external address of the vijil-console-nginx service.

1. Find your Console API URL

If you have kubectl access to the EKS cluster:

kubectl get svc vijil-console-nginx -n vijil-console \
  -o jsonpath='{.status.loadBalancer.ingress[0].hostname}'

This gives you the raw ELB hostname. If a DNS record exists (e.g., console-api.dev05.vijil.ai), use that instead — check Route 53 for CNAME records pointing at this ELB.

2. Initialize the CLI

vijil-console auth init
# Prompt: Vijil Console URL []: http://console-api.dev05.vijil.ai

This saves the URL to ~/.vijil/config.yaml. The init command verifies connectivity by hitting /teams/healthz through the gateway.

Note: The gateway does not expose a root /healthz — health checks are routed per-service (e.g., /teams/healthz, /evaluations/healthz). The CLI uses /teams/healthz as the connectivity check since the teams service handles authentication and is always required.

3. Authenticate

vijil-console auth login
# Prompt: Email: user@example.com
# Prompt: Password: ********

The CLI sends a JSON POST /auth/jwt/login with {"email": "...", "password": "..."} to the teams service. On success it stores the JWT access token and (if available) refresh token in ~/.vijil/config.yaml.

If your account belongs to a single team, the CLI auto-selects it. If you belong to multiple teams, select one:

vijil-console team list
vijil-console team use <team_id>

The active team_id is injected automatically into API calls that require it (evaluations, harnesses, etc.). discover2 commands send it as the X-Vijil-Team header instead, and refuse to run until a team is selected.

4. Use

vijil-console agent list                         # list agents
vijil-console agent get <agent_id>               # agent details
vijil-console eval run --agent-id <id> --wait    # run evaluation, poll until done
vijil-console eval list                          # list evaluations
vijil-console eval results <evaluation_id>       # get results
vijil-console harness list                       # list standard harnesses
vijil-console evolution run <agent_id> --wait    # trigger Darwin evolution
vijil-console proposal list                      # list mutation proposals
vijil-console dashboard show --json              # trust dashboard

Every command supports --json for machine-readable output and --help for usage details.

Configuration

All CLI state is stored in ~/.vijil/config.yaml:

console_url: http://console-api.dev05.vijil.ai
auth_token: eyJhbG...
refresh_token: ...
default_team_id: c58aea71-3861-4f28-b8c4-20832a2f22ee

Token refresh is automatic — if a request returns 401, the CLI attempts POST /auth/jwt/refresh before failing.

Commands

Run vijil-console --help for the full list:

auth        Authentication and CLI configuration (init, login, logout, change-password)
team        Manage team context (list, use)
agent       Manage AI agents (list, create, get, update, delete, import)
eval        Run and manage evaluations (run, status, list, results)
harness     Manage test harnesses (list, custom-list, custom-create, ...)
dome        Dome guardrail configuration and detection
telemetry   Query observability telemetry (metrics, traces, logs)
evolution   Darwin evolution engine (run, status)
proposal    Manage mutation proposals (list, approve, reject)
genome      Manage agent genomes (list, get, create, extract)
persona     Manage test personas
policy      Manage compliance policies and rules
dashboard   Trust dashboard
discover2   Discover scan surfaces, scanners and findings (see docs/DISCOVER2.md)