check

Check with Vibium

Use vibium check "<claim>" to hand a specific acceptance claim to a fresh verifier context. The coding agent builds and fixes the application; Vibium's verifier investigates the running behavior with constrained browser tools. Your own browser inspection does not substitute for this invocation.

Setup

Use the project's configured Vibium binary. Otherwise try vibium, ./clicker/bin/vibium, then ./node_modules/.bin/vibium. Confirm vibium check --help works. Local Chrome is the tested baseline for live checks. For initial live setup, run vibium ready browser --json with the selected engine/channel. It inspects browser and driver files without launching them or touching the current browser; launch and BiDi connectivity remain untested. Follow its install/fix guidance if needed. Saved-input checks do not require a browser; skip browser readiness for them.

For OpenAI, export VIBIUM_AI_PROVIDER=openai, VIBIUM_AI_MODEL, and OPENAI_API_KEY. For xAI, select xai and export XAI_API_KEY (for example --model grok-4). For Anthropic, select anthropic and export ANTHROPIC_API_KEY; for Google, select google and export GOOGLE_API_KEY. Set a model available to that provider. Leave VIBIUM_AI_REASONING_EFFORT unset for Anthropic/Google. local uses the compatible adapter, defaults to http://127.0.0.1:8080/v1, and requires no key. Never manage or install a model runtime as part of Check.

An OpenAI-compatible service uses VIBIUM_AI_PROVIDER=openai-compatible and VIBIUM_AI_BASE_URL. Use the project's existing configuration. Vibium loads ~/.config/vibium/ai.env for empty AI variables; nonempty process environment still wins. If none exists, tell the user to run vibium config init and fill in that file — do not write credentials to it yourself. Never print or log credentials. Do not choose another provider or model to work around a missing configuration without the user's direction.

After loading settings, run vibium ready ai --json during initial setup or when provider configuration changes. Exit 0 and result.ready: true mean the configuration and provider tool round-trip passed; exit 1 includes failed checks and fixes. It makes up to two small model requests and does not launch or change a browser. It does not check the application or replace Check. Resolve reported setup problems before the browser workflow; do not rerun it before every claim when the configuration is unchanged.