Security Patches, Prepared for Review
When a new vulnerability affects your code, an agent prepares the patch, runs the tests, and hands it to your team for review.
Knowing About a Vulnerability Isn't Fixing It
Scanners report vulnerabilities faster than teams can patch them. Each one needs someone to check whether it applies, update the affected package or code, run the tests, and open a pull request. The queue of known issues grows while engineers work on everything else.
An Agent Does the Patch, a Person Approves It
Use an event or a schedule to start an agent. Ask it to check whether your code is affected, propose a patch, run the tests, and prepare a pull request. Your team reviews and merges it.
Patch PR waiting for review
Common Questions
What starts a patch?
An event, a schedule, or a person asking can start the agent.
Does the agent see our production credentials?
Do not provide production credentials for patch preparation. Felan filters platform runtime credentials, such as model keys, out of workspace environment variables. Give the agent only the repositories and test access the work needs.
Who approves the fix?
A person on your team, through a normal pull request review.
Can it run on our own infrastructure?
Yes. Use Felan's managed cloud, or run Felan on your own infrastructure with the Enterprise plan.
Related: Security docs, Dependency updates, Isolated by default.
Keep Your Attention for the Hard Problems
Start with one repo and one recurring task.