Start with a reproducible issue
An issue is most useful when it explains what happened, what should have happened, and how to reproduce the difference. Include the affected route or function and a relevant error message. For example, a report that a checkout form accepts whitespace gives the agent a behavior to reproduce and a regression to test. Avoid adding credentials or customer data to the issue.
Triage before spending time on a fix
Connect a GitHub repository and enable the issue workflow for that repository. With issue triage enabled, Veratex checks requests before starting work. This helps keep unclear or unsuitable requests out of the fix pipeline. A coding agent then investigates the code and prepares a change, rather than leaving your team with another summary of the backlog.
Review the patch and its evidence
Veratex works in a sandbox and runs code review and verification. Inspect the diff, test results, and run logs to understand what changed and what was checked. A passing test is evidence for the covered behavior, not a guarantee that every production condition is safe. Repositories with useful tests give the agent a stronger way to demonstrate a fix.
Choose how changes reach your branch
Use a draft branch when you want to inspect and merge individual changes yourself. For more automation, enable repository auto-merge subject to verification, review, and size limits. Keep merging without a test suite disabled unless you have deliberately accepted that tradeoff. Your existing deployment pipeline decides what happens after a merge.
Common questions
Does Veratex only review pull requests?
No. It can investigate a GitHub issue, write a fix, and verify the change as well as review code. The product covers the maintenance workflow from a reported problem to a proposed or merged fix.
Can I approve fixes before they merge?
Yes. Work on a draft branch and merge the changes you want. Automatic merging is a repository setting and remains subject to merge checks.
What should I try first?
Start with a small, reproducible bug in a repository with a working test suite. Review the first diff and test evidence before increasing automation.
Try it on one repository
Start with a small, well-understood bug and inspect the resulting change. See pricing and usage limits and review our security practices and privacy policy before connecting a source.