Repository navigation
probe 0.2.0: write your own cases
Operators can now work a job without an AI key, by writing cases themselves.
Added
probe case new <job> <Name>writes a case that already meets the job's structural rules, with the fixture's helper functions and their docs listed in it.probe case check <job> <file...>runs the rule check and a local run on your case files, says which test failed and why, and exits 1 when a case would be rejected, so it can gate CI.probe work <job> --case <file>runs and submits your files instead of the agent's or the seed cases.probe job <job>prints a job's brief: chain and contract with explorer links, snapshot, reward, budget left, deadline, eligibility, scope, acceptance rules, and verdicts so far with each payout's transaction.probe doctorchecks Node, Foundry, git, the verifier, the chain RPC, the operator key and its gas, and agent credentials, with the fix for each problem. Exits 1 whenprobe workcould not run.probe submissions [job]lists your submissions across jobs, newest first.--allshows every operator's.--jsononprobe jobs,probe jobandprobe submissions.probe --version.
Fixed
probe workfailed on a machine that had never compiled with the job's pinned solc, because it built with--offline. It now downloads the compiler once when it is missing.- Without Foundry,
probe worksaid "the job workspace does not compile". It now says Foundry is missing and how to install it. - A failed build or local run shows forge's error, not a generic message.
Install or upgrade
git clone https://github.com/probecli/probe && cd probe/protocol # or: git pull
npm install && npm link
probe --version # probe 0.2.0
probe doctorFull changelog: CHANGELOG.md