assay
any model, verifiedassay runs any model — cloud, local, or your Claude/Cursor CLI — against your codebase and tools, then checks the work with real builds, tests, and commands before it calls anything done.
One line in a terminal. Needs Node 18+. No GitHub, no account.
curl -fsSL https://assay.qbcsys.com/install.sh | sh
Installs the runtime in ~/.assay and the assay command in ~/.local/bin. Rich terminal UI: assay --tui.
Desktop app: just open it — the Setup screen picks your model and takes your key, then use Chat or Run a task. No commands. In a terminal:
assay to start.:setup — OpenAI, Anthropic, Gemini, Ollama (local), or your Claude / Cursor CLI.:key sk-… stores it in ~/.assay/config.json. Skip it for local or CLI providers.:connect wires in MCP servers — databases, mail, files, SSH.In the terminal UI (assay --tui) these are slash commands, not colon — see below.
Type to chat. Use :run when the work has to actually pass.
# just ask — the agent can read code and use your tools what does this project do? # verified work — multi-step, and re-checked by real commands :run add a /health route and make the tests pass ✓ verified — build + tests passed # manage runs :jobs # recent tasks :resume # continue an interrupted run :trace # step-by-step audit
Full command list any time with :help · interactive menu with :menu.
Want a richer terminal? Run assay --tui — markdown, syntax highlighting, attachments, and clipboard paste. Same config and keys.
assay --tui # or the installed: assay-tui # commands here are slash, not colon: /model <name> /provider <name> /key sk-… /host <url> /attach file.png /paste /copy all /new /yolo /help
The TUI is chat-only. Verified :run jobs and tool setup (:connect) live in the plain assay CLI — all three share ~/.assay/config.json.