Product tour · Developer
Findings you can fix from your editor, with your coding agent.
See your agent fix a finding through MCP, the assistant explain a blocked pull request, and a false positive dismissed once.
The product tour for your role: PDF·PowerPoint
Developer with a coding agent
From finding to fix, with your coding agent
As a developer, I want my coding agent to read OpenTremor's findings and fix them, so I do not have to copy findings into a prompt.
Findings are in a dashboard. The agent that writes the code never sees them, unless someone copies them into a prompt.
What to notice
- OpenTremor is part of the agent's loop: OpenTremor finds, the agent fixes, and the next review checks the fix.
- The agent uses your access token. By default, it can only read.
- The calls to OpenTremor are real. The agent's words and its edit are scripted for the recording.
Step 1 of 6
OpenTremor flags a critical finding on the pull request.
OpenTremor's comment on the pull request lists a critical finding: the invoice query reads every customer's data.
Any team member
Ask why a pull request is blocked
As a developer, I want to ask why my pull request is blocked and get an answer from our own data, so I do not have to wait for the platform team.
A red check says that something failed. To find out why, you read the docs or ask an expert.
What to notice
- An organization admin turns the assistant on. It uses the organization's own AI model connection.
- Each answer links to the docs it uses.
Step 1 of 3
A pull request is blocked.
OpenTremor's comment shows one critical finding, and the check fails.
Reviewer
Dismiss a false positive once
As a reviewer, I want to dismiss a false positive with a reason, so it does not come back after every push.
Most review tools forget. The same false positive comes back on the next commit, and people start to ignore the tool.
What to notice
- The note stays with the finding, for the next reviewer and for audits.
- Each decision counts against the rule. When reviewers often reject a rule, OpenTremor suggests a change to it.
Step 1 of 3
Every pull request is reviewed against your rules.
OpenTremor's comment on the pull request lists two findings: the customer data bug and a slow, blocking call in a script.
Tech lead
Every pull request checked against your team's rules
As a tech lead, I want every pull request checked against our written standards, so reviewers stop repeating the same comments.
Your standards are in a wiki and in people's heads. A pull request follows them only if the reviewer knows them and has time.
What to notice
- The rule is your team's own, written in plain words. You do not need a special rule language.
- The finding explains the risk, not only the line of code.
- The fix is a normal GitHub suggestion. OpenTremor never commits code for you.
Step 1 of 5
A developer opens a pull request.
The pull request adds a list of invoices. Its database query returns the invoices of all customers, not only the caller's.
Try it on your own pull requests.
Connect a repository, write one rule, and open a pull request.