Support engineers using Cursor: there might be a better fit
No vendor spam, but I keep seeing support and ops people adopt Cursor because their dev counterparts swear by it. It works, sort of.... but it's the wrong shape of tool for what most support work actually looks like.
Cursor is built for sitting inside a codebase for hours. Most support work isn't that. A normal day for a T2/T3 or escalation engineer is more like:
- Tailing logs across five customer environments
- Running ad-hoc DB queries to verify a repro
- SSHing into a box that's misbehaving
- Grepping traces, pivoting between tools, context-switching every few minutes
That workflow lives in a terminal, not an editor. So in comes building yaw.sh, a terminal with AI built directly in.
What that actually means:
- AI right at the prompt. Pipe a log, paste a stack trace, ask "why is this pod crashlooping" with the output you just pulled..... without leaving the shell or alt-tabbing to a chat window.
- Multi-provider. Claude, OpenAI, whatever. Switch per task instead of getting locked in.
- Encrypted connection management built in. SSH keys, jump hosts, per-customer creds, one pane, encrypted, no more hunting through
~/.ssh/configor pasting things out of 1Password notes.
Where it lands vs Cursor:
Cursor is the right tool if your day is writing features. Yaw is the right tool if your day is reading logs, running queries, and SSHing into systems you've never seen before. They don't really compete. They just both have "AI" in the description, so people lump them together.
If you're a support engineer who's been using Cursor as a glorified ChatGPT wrapper, you can probably get the same value (and a lot less context-switching) from a terminal that just has the model right there.
Available on macOS and Windows. Linux on the roadmap.