Common use cases
Sentry error triage
Investigate production errors, identify root causes, and propose fixes automatically.
GitHub issue response
Reproduce bugs, draft responses, and suggest code changes.
Linear ticket automation
Triage new tickets and take a first pass at implementation.
Intercom support triage
Route high-impact support tickets to agents for faster resolution.
PostHog session replay
Watch replays, identify root causes, and suggest code changes.
Scheduled maintenance
Run recurring tasks like dependency updates, report generation, or cleanup.
Triggers
Triggers are the starting signal. When a trigger fires, Proliferate launches an agent and passes the right context so it can act immediately. There are two kinds of triggers:- Events — Something happened (an error, a ticket, a message).
- Schedules — Something should happen on a cadence (daily, weekly, etc.).
| Source | Trigger examples |
|---|---|
| Sentry | Errors, new issues, high-severity incidents |
| Linear | New tickets, status changes, tagged issues |
| GitHub | Issues, pull requests, comments, pushes |
| PostHog | Product events, user behavior webhooks |
| Slack | Mentions, messages, reactions |
| Webhooks | Any system that can send an event, including Intercom |
| Schedules | Recurring cadence (hourly, daily, weekly) |
- The event details (error, ticket, issue, or replay)
- Relevant metadata (labels, severity, environment)
- Linked resources (threads, comments, related work)
Instructions
Instructions tell the agent what success looks like. Good instructions are short, concrete, and written like you would brief a teammate. Good vs vague:- Good: “Investigate the error, propose a fix, and report back in Slack.”
- Vague: “Look into this and do your best.”
- The outcome you want (e.g. identify the root cause and propose a fix)
- Constraints (e.g. avoid risky changes, do not touch production data)
- Where to report results (e.g. reply in Slack or comment in the ticket)
Permissions
Each automation can override the default permission settings. Control which actions the agent can take:- Allow — Auto-execute without asking.
- Require approval — Pause and ask a human first.
- Deny — Block entirely.
Execution flow
When a trigger fires, Proliferate runs the automation through a pipeline:Trigger fires
A system event happens — a ticket is created, a new error appears, or a message arrives.
Environment spins up
A coding agent starts in an isolated sandbox with your repo, dependencies, and secrets.
Context is gathered
The agent receives event details from the trigger source — error stack traces, ticket descriptions, issue metadata, and linked resources.
Work happens
The agent investigates, makes changes, runs tests, and prepares outputs based on the instructions.