ENGINEERING
Agent-driven Sentry triage with GitLab fix branch and MR draft
A Paperclip agent investigates a new Sentry cluster end to end, traces the blame, reads the offending source in GitLab.
How it runs
The automated pipeline, trigger to output.
- TriggerNew high-frequency Sentry clusterSentry
- ActionFetch trace and read source via GitLab blameGitLab
- LogicAgent reasons about root causeOpenAI
- ActionOpen GitLab branch and draft MR with patchGitLab
- OutputSlack the suspected author for reviewSlack
What it does
Hands a fresh Sentry error cluster to an autonomous agent that does the full first-pass investigation. The agent reads the trace, finds the suspect commit through blame, pulls the relevant source from GitLab, reasons about the root cause, and opens a draft merge request with a candidate fix and an explanation. A human reviews and decides whether to merge.
When to use it
Use it for well-scoped, recurring error classes (null guards, off-by-one, missing validation) where a first-draft fix saves engineer time. Best when you want the agent to do the legwork but keep a human firmly in the merge loop.
How it works
- 1Sentry fires when a new high-frequency cluster appears.
- 2The agent fetches the trace and isolates the failing frame.
- 3It runs GitLab blame to find the suspect commit and reads the surrounding source.
- 4It reasons about the root cause and writes a candidate patch.
- 5It opens a GitLab branch and a draft merge request with the patch and rationale.
- 6It posts a Slack note to the suspected author asking for review.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.