Linear Issue Triage Agent with OpenClaw
Read the instructions here and most of them are refusals: do not create a label, do not touch priority, do not move the issue out of triage, do not merge the duplicate you just found. What it may actually do fits in one sentence. OpenClaw is a sensible harness to point at a job drawn that narrowly, and the narrowness is what makes an open agent reasonable in a workspace your whole team reads.
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.
iOS app signs the user out when the phone hands off from wifi to LTE
created by Aditi Raghunathan
Started with build 5.9.1, which shipped Tuesday. On iOS 18.4, walk out of wifi range with the app open and the session token gets dropped, so the next tap lands on the login screen. Nine people in the beta channel hit it today, two of them on the Kerslake account. Android is unaffected.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
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 guide
Your triage rules in plain English - which labels you genuinely use and what each one means, what clears the urgent bar, and the repro details your engineers always end up chasing. Nothing gets classified from anywhere else.
Team map
Each area of the product and the Linear member who owns it, and where to send an issue whose area is not obvious.
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 short list of allowed writes
Two labels, one assignee, one comment, and a Slack line for genuine outages. There is very little surface for a plain agent to get creative on.
Set up once, left alone
Hosted with nothing to install, so triage keeps happening while the person who configured it is on holiday and nobody else remembers it exists.
Before you fork
If OpenClaw turns out too blunt, what does moving cost me?
A dropdown on the agent node. Your triage guide, area map, Linear credential and Slack channel all stay exactly as they are, and the next issue filed is handled by the new harness. Teams often start here precisely because the exit is cheap, then move once they can point at the calls they disagree with.
Run it with a different agent
Put Linear Issue Triage Agent to work on OpenClaw
Free to start. Guided setup, a test run against staged conversations, and it's live.