ProofRun / Your projects
Checking setup
BEFORE YOU SHIP

Put your software to the test.

Bring your project. See what fails. Decide what changes.

Your project. One workspace.

ProofRun asks Bob how your software works, prepares an isolated environment, and exercises real behavior. Every failure has evidence. Every source change needs your approval.

AnalyzeRun & testReview findingsApprove & verify

Upload any source type. Execution depends on an available Linux runtime and the services your project needs. Unsupported requirements are reported.

Test your application

Choose the project folder. Source, configuration, assets and tests are copied into a new workspace.

No folder selected

Upload a ZIP

ProofRun copies the source folder into an isolated workspace.

Up to 2,000 files / 3 MB, with 2 MB per file. Dependency folders, symlinks and credential files are excluded. Bob receives bounded source context through your configured IBM account.

Connect Bob & execution

1. Configure your key on the server

Create .env beside ProofRun's package.json. Add:

BOBSHELL_API_KEY=YOUR_IBM_BOB_INFERENCE_KEY

The browser never receives the key. Restart ProofRun after saving it. Do not put your key in an uploaded project.

Use an IBM Bob Inference key. General keys also require BOB_TEAM_ID in the same server .env file.

2. Install Bob Shell

If it is missing, run this from ProofRun's folder:

npm run setup:bob

Complete IBM's first-run license/sign-in setup if prompted. Bob runs without file or command tools for this integration.

3. Start Linux containers

Install and start Docker Desktop with Linux containers, or use Docker Engine on Linux. On Windows, Docker may require WSL 2 and a restart.

4. Start ProofRun

npm start

Edit proposed repair

Edit the replacement contents. Saving creates a new diff revision; source is unchanged until you approve that revision.

Source file