Loading...
Product
Core Features
Top Extensions
Company
Subscribe to our newsletter.
Get product updates and news in your inbox. No spam.
Triage your Jira, Linear, and GitHub tickets without leaving Raycast. Search, check your Today board, change status, drop comments, log work — all hitting your local Mach Triage desktop app over localhost. No cloud relay. No token exposure. No bullshit context switching.
This extension talks to a local HTTP bridge running inside the Mach Triage desktop app on your machine. Your issue data never leaves your box through this extension — Raycast sends requests to 127.0.0.1 and gets back what it needs. Provider credentials (Jira OAuth, Linear API keys, GitHub tokens) stay locked in the desktop app's encrypted storage.
That's it. If the bridge URL isn't default (http://127.0.0.1:17847), paste that too.
| Command | What it does |
|---|---|
| Search Tickets | Full-text search across your active workspace. Finds by key, title, or description content. |
| Today Board | Your Active / Stuck / Next / Done Today lanes — same as the desktop, keyboard-first. |
| Mach Triage Status | Health check. Shows version, connection state, and workspace info. |
| Action | Shortcut | Notes |
|---|---|---|
| View Detail | Enter | Full description, comments, worklogs, metadata |
| Open in Mach Triage | ⌘O | Deep links to the ticket in the desktop app |
| Change Status | ⌘⇧S | To Do, In Progress, Done, Backlog, Canceled |
| Add Comment | ⌘⇧M | Markdown body, optional sync-to-provider toggle |
| Log Work | ⌘⇧W | Hours + minutes, provider-aware (Jira pushes, Linear/GitHub local-only) |
| Copy Key | ⌘C | Copies the issue key to clipboard |
Why does Mach Triage need to be running?
Because this extension doesn't talk to Jira/Linear/GitHub directly. It talks to the Mach Triage bridge on your machine, which already has your synced data and credentials. This means zero OAuth setup in Raycast and zero token exposure.
What providers are supported?
Whatever you've connected in Mach Triage: Jira, Linear, GitHub, and local-only workspaces. The extension doesn't care — it queries the local database.
Does my data go to the cloud?
Not through this extension. Requests go to 127.0.0.1 only. The desktop app handles its own sync to Jira/Linear/GitHub, but that's a separate concern.
What about Pro features?
If the desktop app enforces Pro gating on certain features, the bridge returns a 403 and Raycast shows a clear message. No silent failures.
Can I use this on Windows?
Yes. Raycast Windows is in beta, and Mach Triage runs on Windows. The bridge works identically on both platforms.
| Problem | Fix |
|---|---|
| "Mach Triage is not reachable" | Launch the desktop app. Bridge only runs when the app is running. |
| "Bridge token rejected" | Regenerate in Settings → Raycast Integration → Generate Token. Paste the new one in Raycast Preferences. |
| "Raycast bridge is disabled" | Settings → Raycast Integration → flip the Enable toggle. |
| Search returns nothing | Check your active workspace has synced tickets. Try "Sync Now" in the desktop app. |
| Worklog says "local only" | Linear and GitHub don't have worklog APIs. Time is tracked locally in Mach Triage. Jira worklogs push normally. |
This extension sends HTTP requests only to your local Mach Triage bridge (127.0.0.1). Issue data never routes through Mach Triage cloud services from Raycast. Provider credentials remain exclusively in the desktop app's encrypted storage.
Full policy: https://mach-triage.com/privacy
MIT — see LICENSE. The Mach Triage desktop app is proprietary.