1d ago

David Cramer builds Slackbot outperforming vendor AI agents

0

David Cramer posted that vendor-specific tools such as the Sentry agent and the Linear agent inside Slack handle only isolated tasks. He described an internal Slackbot connected to Sentry, GitHub, Linear, Notion and other platforms that managed cross-tool workflows more effectively. Subsequent posts in the thread reinforced the same point, contrasting generalized agents such as Devin with narrow vendor chatbots and attributing the performance difference to breadth of system access.

Original post

vendor-specific chatbots are broken by design that means the Sentry agent, the Linear agent, and any others you might have in Slack they are fine for some point situations, they're nice to get started with, but agents with generalized access outperform them in every single scenario some weeks ago we built an internal Slackbot, gave it access to a bunch of systems (Sentry, GitHub, Linear, Notion, etc), and its capabilities overnight far exceed these other bots "Oh cool Linear can now search your code bases" - our bot did that on day one, and then could push that information wherever it needed to go. Its useful to the point where I now discourage use of things like the Linear bot because it _creates worse outcomes_. this also goes beyond the simple generalization of access: we can customize it. we throw in skills-as-runbooks, templates, etc and the outcomes once again incrementally improve if your org hasnt already built a general purpose bot internally you should. if you need inspiration ours is open source on GitHub (albeit fairly unstable still) https://github.com/getsentry/junior

9:22 AM · May 15, 2026 View on X
Reposted by

@benhylak Yeah Devin is pretty good

ben hylakben hylak@benhylak

i think this will just be devin

5:38 PM · May 15, 2026 · 34.9K Views
2:34 PM · May 16, 2026 · 467 Views

i think this will just devin

David CramerDavid Cramer@zeeg

vendor-specific chatbots are broken by design that means the Sentry agent, the Linear agent, and any others you might have in Slack they are fine for some point situations, they're nice to get started with, but agents with generalized access outperform them in every single scenario some weeks ago we built an internal Slackbot, gave it access to a bunch of systems (Sentry, GitHub, Linear, Notion, etc), and its capabilities overnight far exceed these other bots "Oh cool Linear can now search your code bases" - our bot did that on day one, and then could push that information wherever it needed to go. Its useful to the point where I now discourage use of things like the Linear bot because it _creates worse outcomes_. this also goes beyond the simple generalization of access: we can customize it. we throw in skills-as-runbooks, templates, etc and the outcomes once again incrementally improve if your org hasnt already built a general purpose bot internally you should. if you need inspiration ours is open source on GitHub (albeit fairly unstable still) https://github.com/getsentry/junior

4:22 PM · May 15, 2026 · 232.7K Views
5:29 PM · May 15, 2026 · 1.8K Views

i think this will just be devin

David CramerDavid Cramer@zeeg

vendor-specific chatbots are broken by design that means the Sentry agent, the Linear agent, and any others you might have in Slack they are fine for some point situations, they're nice to get started with, but agents with generalized access outperform them in every single scenario some weeks ago we built an internal Slackbot, gave it access to a bunch of systems (Sentry, GitHub, Linear, Notion, etc), and its capabilities overnight far exceed these other bots "Oh cool Linear can now search your code bases" - our bot did that on day one, and then could push that information wherever it needed to go. Its useful to the point where I now discourage use of things like the Linear bot because it _creates worse outcomes_. this also goes beyond the simple generalization of access: we can customize it. we throw in skills-as-runbooks, templates, etc and the outcomes once again incrementally improve if your org hasnt already built a general purpose bot internally you should. if you need inspiration ours is open source on GitHub (albeit fairly unstable still) https://github.com/getsentry/junior

4:22 PM · May 15, 2026 · 232.7K Views
5:38 PM · May 15, 2026 · 34.9K Views

absolutely 100% true

David CramerDavid Cramer@zeeg

vendor-specific chatbots are broken by design that means the Sentry agent, the Linear agent, and any others you might have in Slack they are fine for some point situations, they're nice to get started with, but agents with generalized access outperform them in every single scenario some weeks ago we built an internal Slackbot, gave it access to a bunch of systems (Sentry, GitHub, Linear, Notion, etc), and its capabilities overnight far exceed these other bots "Oh cool Linear can now search your code bases" - our bot did that on day one, and then could push that information wherever it needed to go. Its useful to the point where I now discourage use of things like the Linear bot because it _creates worse outcomes_. this also goes beyond the simple generalization of access: we can customize it. we throw in skills-as-runbooks, templates, etc and the outcomes once again incrementally improve if your org hasnt already built a general purpose bot internally you should. if you need inspiration ours is open source on GitHub (albeit fairly unstable still) https://github.com/getsentry/junior

4:22 PM · May 15, 2026 · 232.7K Views
5:43 PM · May 15, 2026 · 16.2K Views
David Cramer builds Slackbot outperforming vendor AI agents · Digg