Agent Kernel vs Linear AI Triage Agent

“The simplicity is the feature. Three Markdown files, git-trackable, human-readable. No ORM, no migrations, no database to manage. For agents that need persistent state without infrastructure overhead, this is the pragmatic choice. I would pick this over LangGraph's complexity any day.”

“The primitive is clear: a classifier-plus-router that runs on incoming issues using your team's historical label and assignment patterns as training signal. That's a real problem — triage queues are genuinely painful and the manual work is mind-numbing. The DX bet Linear made is correct: zero new config surface because it learns from what you've already done in Linear, not from YAML you have to write. The moment of truth is when the first real bug report comes in and gets silently miscategorized — that's where I'd probe — but the fact that it's embedded in the workflow rather than bolted on as a webhook or separate dashboard is the specific decision that earns the ship.”

“Agent Kernel proves that the best agent infrastructure might be no infrastructure at all. Markdown as a universal state format means your agent's memory is inspectable, debuggable, and portable. This "files over frameworks" philosophy will age well.”

“Cute for prototyping but falls apart at any real scale. No concurrent access handling, no structured queries over memory, no way to prune state as it grows. You will outgrow three Markdown files the moment your agent needs to remember more than a weekend's worth of conversations.”

“Direct competitors are GitHub Issues with third-party triage bots and Jira's own Smart Issue automation — neither is good, which is exactly why this has room to exist. The scenario where this breaks is small teams under 50 issues/month who don't have enough historical patterns to train on, and the first generation of outputs will be confidently wrong in ways that take longer to fix than manual triage. The prediction: this survives because Linear has the distribution and the workflow data moat — the triage agent gets genuinely better as your team uses Linear longer, which is the one defensibility story I actually believe. What would make me wrong: if Atlassian ships the same thing inside Jira and enterprises just don't switch.”

“The job-to-be-done is laser-focused: eliminate the manual triage step between bug report creation and engineer assignment. That's a single, complete job with a clear before-and-after state, and this product doesn't try to also be a sprint planner or a retrospective tool. Onboarding is near-zero for existing Linear users — the agent activates on your existing workspace data, which means value is visible within the first week without a configuration sprint. The specific product decision that earns the ship is that it routes based on historical patterns rather than asking the team to define routing rules upfront — that's the right opinion to have, because no team will maintain a routing config file.”

“The buyer is already inside Linear's billing relationship — this isn't a new sales motion, it's an expansion feature that makes the existing subscription stickier and raises the cost of switching to Jira or Shortcut. The moat is real and specific: the agent improves with your team's accumulated Linear data, so a team that's been on Linear for two years gets a dramatically better agent than a team that just migrated — that's genuine workflow lock-in, not fake lock-in. The stress test is whether Linear can hold the line on pricing when GitHub Copilot or Atlassian Intelligence ship triage as a bundled feature, and honestly the answer depends entirely on whether Linear's base product keeps winning on DX, which it has so far.”