botctl vs Linear AI Issue Triage Agent

“This fills a real gap. Running AI agents as persistent processes with proper lifecycle management — sleep, pause, resume, memory — is something every serious builder eventually cobbles together themselves. botctl gives you that scaffolding out of the box. The BOT.md format is a genuinely clever design choice: your bot is just a file you can git commit.”

“The primitive here is straightforward: an event-driven classifier that reads Slack thread context or GitHub webhook payloads, runs them through a model, and writes structured output back into Linear as labels, assignees, and priority fields. The DX bet is zero-config bootstrapping — the agent infers team conventions from existing issue history rather than requiring you to hand-craft routing rules. That's the right call because the alternative is a YAML file someone writes once and never updates. The moment of truth is whether the label inference survives contact with a repo that has 40 overlapping labels from three different PMs, and I'd want to see that demo before fully committing. Still, this isn't a wrapper around three API calls — it's a feature embedded in the tool where the context lives, which is exactly the right architecture.”

“25 stars and v0.3.5 with no public adoption story. The concept is sound but the execution is completely unproven at scale. Most teams running serious agent workloads are building on Kubernetes or Modal, not a Go CLI from a solo dev. Check back when there's a community behind it.”

“The direct competitor is every Zapier/Make flow that routes GitHub issues to Linear with a regex label matcher — and this genuinely beats that because it operates on natural language context rather than keyword rules. The specific scenario where this breaks is a monorepo team with five squads, divergent label taxonomies, and no shared convention: the model will learn the noise as readily as the signal, and you'll get confident mislabeling instead of obvious failures. The kill scenario in 12 months isn't a competitor — it's GitHub Issues native AI triage shipping as a Copilot feature, which would eliminate the need for Linear as the receiving system for teams not already bought in. What would have to be true for me to be wrong: Linear's installed base is sticky enough that even if GitHub ships this, teams don't migrate.”

“The future of software is armies of persistent agents running 24/7, each with a job and a memory. botctl is betting on that future early. The BOT.md format could become a community standard for sharing and distributing agent definitions — like Dockerfiles but for AI workers.”

“”

“The idea of defining a bot as a markdown file with YAML frontmatter is elegant and approachable. It's the same mental model as a blog post or documentation page — creators who aren't full-time engineers can understand and modify it. That lowers the barrier to deploying personal automation agents considerably.”

“The job-to-be-done is precise: eliminate the human gatekeeping step between 'someone reports a thing' and 'the right person knows about the thing.' That's a real job, it's universally hated, and Linear is the right place to solve it because the routing context — labels, teams, past assignments — already lives there. Onboarding to this feature should be near-zero since it reads existing issue history, but the critical gap is escalation confidence thresholds: if the agent can escalate critical bugs without human intervention, what's the override mechanism and how loud is it? A product that auto-escalates with no obvious snooze or audit trail is a feature that gets turned off after the first false positive at 2am. Ship if that escalation surface is designed thoughtfully; the core triage loop earns it.”