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.). discover 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
discover Discover (Shadow control plane): scan surfaces, scanners and findings (see docs/DISCOVER2.md)
Metadata
Release files for vijil-console 0.4.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vijil_console-0.4.8.tar.gz | 49.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vijil_console-0.4.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 123.8 kB
Release files / vijil_console-0.4.8.tar.gz
| Download URL | vijil_console-0.4.8.tar.gz |
|---|---|
| Size | 49.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca3fa810deb8b4a8dbe927fca531ce2223afecba682eb1ed39b8a10ebee8547c
|
|
BLAKE2b-256 checksum How to use checksums |
e250efe8d37e2e514ae262e893c34ecf51600232985c69f02e35ec517250c341
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.12.15 Linux/6.17.0-1022-azure
|
Release files / vijil_console-0.4.8-py3-none-any.whl
| Download URL | vijil_console-0.4.8-py3-none-any.whl |
|---|---|
| Size | 74.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
78f4d096157d5c63a7872200d16543666391450afaf786be0108fc5168237ef0
|
|
BLAKE2b-256 checksum How to use checksums |
aae2054504b1b2292aadf2566d6c8f52eb7532612e822416b8591747c9857deb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.12.15 Linux/6.17.0-1022-azure
|
Security for vijil-console 0.4.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
