Clear Tickets, Turned Into Tested PRs
Assign a well-described bug or small feature, and get back a pull request with the implementation and tests.
Small Tickets Wait Behind Big Ones
Every backlog has well-described bugs and small features that would take an engineer an hour. They keep losing to bigger work, and the backlog grows. The ticket already says what to do; what's missing is someone to do it.
Assign It, Review the PR
A Linear or Jira issue event, or a person asking, starts the agent. It reads the repository's structure and conventions, implements the change with targeted tests, runs the checks, and opens a pull request for review.
Show last login date on the profile page
3 tests added, checks passed
Common Questions
Which tickets work best?
Well-described bugs and small features with clear acceptance criteria. The clearer the ticket, the better the result.
Which issue trackers are supported?
Linear and Jira issue events can start an agent. Jira Cloud event delivery is set up with Felan support. Integrations also include Azure DevOps, Asana, and ClickUp.
Does it follow our conventions?
It reads the repository's structure, package manager, conventions, and project instructions before changing files.
Which models can it use?
Any major provider, plus local and private models. Bring your own keys or subscription, and there's no markup on tokens.
Related: Software engineering docs, First-pass code review.
Keep Your Attention for the Hard Problems
Start with one repo and one recurring task.