PostHog Exception Triage Agent with OpenClaw
Per exception the shape never varies: look up the person, list what they did, run one count, check for a recording, search Linear, file once. OpenClaw needs very little to be aimed at something, and this something is a straight sequence with a single decision inside it, namely whether your triage rules say to file at all.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
TypeError: t.workspaceId is undefined
at resolveWorkspace (assets/index-4f2a91.js:1:88214), at WorkspaceSwitcher (assets/index-4f2a91.js:1:91002), at renderWithHooks. Thrown on /settings/members three minutes into the session, with flag new-workspace-switcher active.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect PostHog
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Linear
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Triage rules
How you decide an exception matters and where it goes - the person and occurrence counts for each severity, the window you count over, the Linear team that receives issues, and the exceptions you already know about and want left alone.
Runs on OpenClaw
Preselected for this page — connect your OpenClaw account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenClaw for this agent
A sequence with one branch
Everything before the filing decision is gathering. The only fork is whether an open Linear issue already covers this, which is a search result rather than a judgement.
Slack stays nearly empty
Only top-severity exceptions earn a line and everything else lives in the tracker. An agent that mostly writes to Linear is a quiet thing to leave running.
Before you fork
Does an engineer have to babysit this?
The triage rules are the only maintenance, and they amount to counts, a window, a Linear team and the exceptions you already know about. Whoever owns the bug backlog can edit those without touching the workflow. The part that goes stale is the known-exceptions list, since it grows every time you fix something.
Run it with a different agent
Put PostHog Exception Triage Agent to work on OpenClaw
Free to start. Guided setup, a test run against staged conversations, and it's live.