Background Agents That Are Always On
Agents start from an event, a schedule, or a person, and work without anyone watching. When the team comes back, the results are waiting for review.
Started by an Event, a Schedule, or a Person
Pair instructions with a recurring schedule, a one-time run, or an event from a connected system.
New automation
When
- ScheduleWeekdays at 06:00
- EventPostHog Log alert
- SlackAsked in a connected channel
Do
Investigate and post a first analysis
Work Happens While the Team Is Away
Agents run on shared infrastructure instead of a developer's laptop.
- 03:12Alert investigated, draft PR #1433 opened
- 04:40Flaky auth tests fixed
- 06:00Dependencies updated, tests green
Results Ready for Review
Open the session to review its transcript, status, and delegated agent activity.
Team sessions
- Automation: Nightly flaky test sweepReady for review
- Webhook: Triage failed build #2291Ready for review
- Person: Update checkout error copyIn review
Common Questions
What can start an agent?
A recurring schedule, a one-time run, an event from a connected system, or a request from the dashboard or a connected conversation.
Which systems can send events?
GitHub, Linear, Asana, PostHog, and Vercel can send events. GitLab and Jira Cloud webhook setup currently needs support. Other systems can use the authenticated generic webhook endpoint with a matching event automation.
Do agents run on developers' machines?
No. They run on shared infrastructure, Felan's managed cloud or your own infrastructure.
Who reviews what agents did?
A person on the team reviews the result.
Learn more about Use cases, Automations docs.
Keep Your Attention for the Hard Problems
Start with one repo and one recurring task.