File a Linear issue from the bug on screen.

A bug on your screen becomes a structured Linear ticket in Jarvis (getjarvis.eu), a desktop AI assistant. Press Cmd+/ on macOS or Ctrl+/ on Windows and ask it to file the bug in Linear. It reads the console error, broken UI, or failing test, then writes the title, reproduction steps, expected versus actual behavior, and environment details before creating the ticket through the Linear connector. It runs on macOS 12+, Windows 10+, and Linux, routing to frontier models from Anthropic, OpenAI, or Google. It can also link a related GitHub commit. Tokens are AES-256-GCM encrypted, GDPR-aligned, and never used for training. A free plan (40 requests/week); paid plans from $16/month.

The friction in filing bugs is reconstructing context: what was the error, which version, what did you click. Jarvis already sees it. From a visible stack trace or a misbehaving screen it drafts the title, the exact error text, the steps that led there (as much as it can infer), and the expected versus actual outcome. You confirm or fill the gaps, and it writes a ticket a teammate can actually act on — not the one-line "it's broken" that bounces back for more info.

Through the Linear connector, Jarvis creates the issue directly — with the priority, team, and labels you specify — so you never leave your editor. If the bug traces to a recent change, it can attach the related GitHub commit or PR link so the assignee has a head start. Filing from a Slack complaint? It can pull that thread for context too. The ticket lands fully formed in the right project, which is the difference between a bug that gets fixed this cycle and one that rots in the backlog.

Code & tickets