Users say Linear’s Slack agent still lacks memory, speed and thread context
var_epsilon · x · 2026-07-23
A user says Linear’s Slack agent still feels brittle in real ticketing workflows
The post lists several frustrations after using Linear’s Slack agent to create tickets:
- it often checks Done issues for duplicates
- there appears to be no memory or system prompt support, so instructions must be repeated
- it won’t attach issues to projects unless explicitly told
- it requires tagging each time, instead of continuing to listen in a thread
- it should be 2–3× faster, though that is not the main blocker
The takeaway is that the agent is useful enough to adopt, but still lacks the persistence and workflow ergonomics users want from a production tool.
More from coding & agent
- Carson Farmer says Codex can validate product hunches in hours — carsonfarmer · 2026-07-23
- Carson Farmer says the Codex experiment stayed within budget and fed the knowledge base — carsonfarmer · 2026-07-23
- Carson Farmer uses Codex for a micro-rewrite in a standalone side app — carsonfarmer · 2026-07-23
- X says its API overhaul now powers agents, monitoring tools, and real-time workflows — XFreeze · 2026-07-23
- A B2B SaaS founder runs the company with six agents in Claude Code — jacob_posel · 2026-07-23
- SandsDX says its AI-native operation runs in Claude Code with six agents — jacob_posel · 2026-07-23