Tbench Actions / built around your next push
Run your CI on your own computer. Add Jira-linked AI repair, retest the change, and bring the result to your lead in Slack.
Your 15-day trial starts after organization approval. No automatic charge.
GitHub records the exact commit and workflow.
$ tbench-worker pushPush accepted · current branchWaiting for its signed GitHub job event…See Tbench at work
Step inside the workflow. Explore the terminal, the requirement, the repair and the approval.
Execution trail 8 steps
The original revision is retained, including its failure.
$ tbench-worker pushOriginal commit dd9b0a3b2c75GitHub run 41341232214Runner invoking computerReplay a real internal QA run: Jira requirements, a source-only AI patch, unchanged tests, fresh GitHub CI and approval in Slack.
The replay uses the recorded internal QA flow with an owner-operated free OpenRouter adapter. Public CLI provider qualification is tracked in the run evidence.
Your push runs on your computer.
Your existing CI. Optional AI repair.
Scoped access. Bounded execution.
Choose how you run
GitHub stays the trigger and workflow control plane. Choose the developer’s own computer for local CI, or separately approved hosted compute with an organization budget.
A push or pull request starts the GitHub workflow. The opted-in runner executes only on its owner’s device; another developer’s computer is never borrowed.
$15 / contributor / monthOne-time organization and device approval; no Tbench compute-minute fee.Use linked requirements to assess selected code, propose a bounded repair and rerun unchanged tests before lead approval. Hosted demo capacity has a monthly budget and per-run ceiling.
Hosted demo · $0.10 / started runApproved CPU compute included for up to ten minutes. Model access is configured separately.Code checks & business context
Link a Jira ticket or Confluence specification to a GitHub repository, pull request or workflow run. Then run your repository’s named checks and optional local AI review.
Authorize read-only access, choose the exact ticket or page, and decide whether its selected text may be shared with your Tbench organization.
Connect project contexttbench verify runs required repository checks with commit-bound evidence. Optional model review remains advisory; your test policy decides the required gate.
Infinity’s versioned 14-stage methodology audits Terminal-Bench tasks, environments, reference solutions and verifiers. It is distinct from a customer’s ordinary application CI check.
Explore the Infinity methodologyThe idea
Bring builds, tests and reviews to the capacity your organization already owns. Keep execution close to your team and manage each device, repository and job from one place.
Your repository defines the commands. Keep GitHub orchestration or approve a portable policy for your custom CI. Required checks remain explicit.
Compare execution and verificationEnroll a computer you own, set resource caps and choose when to serve jobs. Your team controls the capacity, the repository scope and the execution window.
Understand worker placementJobs wait for an eligible device and run within the profile you select. Customer-owned compute keeps execution capacity and spend under your organization’s control.
Check the supported profileExecution with a clear trail
Repository-scoped access, single-job runners, signed GitHub completion events and controlled cleanup. Follow the execution path in our published run records.
Explore execution resultsConnected engineering teams
Start with an approved account or configured company sign-in. Add approved teammates by email, follow your first-run checklist and link authorized Jira or Confluence context. Your repository’s tests and review rules define business acceptance.
From approval to your first job
Try Actions execution and local application verification on your own compute. Your team keeps the same approval and workload controls throughout the trial.
Use your work email. We review your company, repositories and intended workload before activating the trial.
Connect approved GitHub scope or register an immutable Tbench policy. Enroll each consenting device.
Inspect the queue, results and resource limits. Add named required/advisory checks with the separate verifier command.
Review contributor seats and monthly or annual terms. Trial expiry never creates an automatic charge.
15 days to put it to work
Apply with your company email. We review your organization, repositories and device scope. Your 15-day trial starts after organization approval. No automatic charge.