If unassigned Linear issues stack up while you run product eng, this Linear triage agent drafts the boring half so you only make the calls.
Linear Triage Agent is a public jurniti template (/templates/linear-intake-and-triage-sf). You fork it into a paid claudecode microVM — not a Notion checklist and not a free shared sandbox.
If you searched for Linear AI agent template, this page maps that intent to a concrete fork: product truth, gates, BYOK, and the demo you should run before real customers see anything.
What searchers mean by Linear AI agent template
People typing Linear AI agent template usually want one of three things: a hire-me agency, a course, or a runnable operator.
Hire-me pages sell retainers. Courses sell modules. jurniti sells a running agent seat you can fork, key, and operate — with Firecracker isolation and a human still on the hook for dangerous sends.
This post is written for the third group: operators who will pay for a real box and own the demo.
Why Linear Triage Agent runs on a Firecracker microVM
Laptop agents die when the lid closes. Docker density is not the same as multi-tenant isolation.
jurniti provisions a Firecracker microVM per fork. The claudecode harness install lives on the platform golden path; your template persist (skills, instructions, config shapes) restores on top. Boot is fast; full provision is still about three minutes, not a marketing 124ms hand-wave for the whole journey.
More on the harness: claudecode guide.
Related gallery family: Software Factory collection.
What you get when you fork Linear Triage Agent
When you fork Linear Triage Agent, you are not buying a PDF.
- The linear-intake-triage skill under ~/.claude/skills/
- A vault file at ~/vault/team.md for team and project context (you fill it in after forking; capture scrubbing drops secrets)
- A human gate on every write that would ping a person
You still configure secrets after fork. Nothing valuable should be baked as a live credential in a public capture.
The undeniable demo for linear-intake-and-triage-sf
After keys are set, run the demo the gallery About body describes for Linear Triage Agent.
Do it against a dry-run or your own inbox first. If the demo cannot complete, do not point the agent at real customers yet.
BYOK, human gates, and what you still own
BYOK: model keys and third-party API keys are yours. jurniti does not mark up tokens in v1.
BYOK: your keys live only inside your VM and never leave it. The VM keeps running when your laptop is closed.
- Claude login or ANTHROPICAPIKEY
- LINEARAPIKEY
Where outbound mail, social publish, or paid fulfillment exists, treat human approval as product. Auto-spam is the wrong fit for this gallery.
No free trial. No free tier. First purchase: 30-day money-back guarantee. Model and SaaS fees stay on your accounts.
Linear Triage Agent vs building the same stack yourself
| Path | What you get | Cost of time |
|---|---|---|
| DIY scripts + laptop | Fragile glue | Nights and weekends |
| Generic course | Concepts, no seat | Weeks of setup |
| Fork Linear Triage Agent | Pre-wired agent on microVM | Minutes to first demo |
Courses do not remove wiring. Shared multi-tenant toys do not give you isolation. The template is the middle path: paid, isolated, opinionated.
Fit and not-fit for linear operators
For you if you want intake help without agent noise flooding the team channel.
Not for you if you want full auto-assign to unsuspecting humans. That is what this template refuses to do.
How to fork Linear Triage Agent on jurniti
- Open Linear Triage Agent.
- Fork on a paid plan.
- Wait for the microVM (about three minutes).
- Export BYOK keys listed in the About body.
- Run the undeniable demo before real traffic.
That is how Linear AI agent template becomes an operated system instead of another bookmark.