Starlie

Press ⌘K and type an issue key, a word from the summary, or a project name. Results come back as you type. For narrower searches, write JQL directly and the editor suggests fields, operators, and values as you go, which helps when a query needs three conditions and you only remember two. There's also a visual query builder for people who don't want to memorize Jira's syntax.

The board shows the active sprint with its columns and cards. Drag a card to the next column and the transition is written back to Jira, so the board in Starlie matches the board your team sees. It's a practical way to run a standup or clear a queue of ready tickets without opening a browser.

One view holds the description, subtasks, comments, and attachments. Status, assignee, and priority can be changed from the issue itself. Comments support @mentions and attachments, and you can write in a rich text editor or switch to raw Jira wiki markup when you need exact formatting.

Outline pulls epics, stories, and subtasks from several projects into a single tree you can expand and collapse. Grouping, sorting, and saved views let you build a picture of a release rather than a single board. You can see who owns each task and how far along it is, which is the part Jira's board view tends to hide.

Any issue can open in Claude or Codex with its context attached, and the agent starts with the local project folder already connected. That removes the copy and paste step between a ticket and a coding session. It's the feature that makes Starlie more than a faster viewer, especially for developers who already work this way.

Multiple windows, macOS notifications, menu bar access to starred issues, and light or dark mode all work the way Mac users expect. Sign-in uses Atlassian OAuth 2.0, tokens live in the macOS Keychain, and issue data travels directly between your Mac and Atlassian over TLS. Starlie's own server, auth.starlie.app, handles the token exchange and doesn't receive Jira content.