AI writing assistant for Linear issues and updates

No — and it doesn't touch your Linear workspace. Rewrait is a native Mac and Windows app that works at the operating-system level, so it works over Linear's desktop app and Linear in the browser the same way: select text in an issue description, a comment, a project update, or a document, press Cmd/Ctrl+Shift+P, and replace it with the rewrite. There is no API key, no OAuth grant, no webhook, and no access to your issues — Rewrait sees only the text you select, when you select it. That also means it isn't limited to Linear: the same shortcut cleans up the GitHub PR description linked from the issue, the Slack message announcing the fix, and the customer-facing changelog entry. One writing layer across the whole loop, with no integrations to maintain.

It restructures; it doesn't decorate. Rewrait ships with Tech Professional as a default style, built for exactly this kind of writing: it turns a stream-of-consciousness bug note into problem, repro, and scope — preserving your URLs, code references, and markdown instead of paraphrasing them away. It does not add enthusiasm, adjectives, or an AI-flavored closing sentence. If the result is still too long, the Shorter and More direct variants are one click away. Nothing is sent or saved automatically: you see the rewrite next to your draft and replace only if it's better. The engine's contract is to output only the transformed text — no preamble, no chat-style commentary. The honest pitch: you already know what the issue should say. Rewrait gets it from your head into the description thirty seconds faster, in a shape the assignee can act on.

No — preserving structure is part of the rewrite contract. Rewrait keeps markdown, links, inline code, and placeholders intact, so a repro list stays a list and an error string stays verbatim. Because it replaces your selection as plain text, it plays fine with Linear's markdown shortcuts and renders normally once inserted. The practical workflow: write the rough issue with whatever structure you'd naturally use — a few bullets, a pasted error, a link to the PR — select it all, and run Tech Professional. The rewrite comes back with the same structural elements, organized and tightened. If you select only one paragraph of a longer description, only that paragraph changes; the rest of the issue is untouched, because Rewrait never sees it. And since you review before replacing, a bad rewrite costs one keystroke to discard, not a mangled issue.

Yes — that is the Team plan's core job. Create workspace styles like Bug report, Spec section, or Status update, and everyone — engineers, PMs, the designer who files one issue a month — rewrites with the same definitions under the same hotkey. Styles can pull approved context from Notion, Confluence, or Google Docs: if your engineering guidelines doc says updates must lead with status and date, rewrites come out that way without anyone re-reading the doc. Multi-step workflows go further, chaining steps like structure-as-bug-report then tighten-to-100-words into a single shortcut. Team is $20 per seat per month billed annually ($25 monthly), with no seat minimum — and every signup starts with a 14-day free Team trial, no card, which is enough to standardize one squad's issues and see whether triage actually gets faster.