Linear (in development)
A first-party integration that brings your Linear team board into Omniscio so you can work issues without opening the Linear website: connect with a personal API key, see your columns and cards, open an issue's detail, and start an AI session on an issue in one click. It is gated through the unreleased-feature registry, so it stays hidden until enabled.
On this page
What it is
Status: experimental / in-development. Hidden by default. Turn it on in Settings → Lab → "Linear board" (or set
AMC_SHOW_LINEAR_BOARD=1in dev).
A first-party Omniscio integration that brings your Linear team board into the app so you can work issues without opening the Linear website. It surfaces as a "Linear" row in the projects sidebar (between Job Monitor and Marketplace) that opens a full-pane board view.
It is gated exactly like the Jira board / Pull Requests tab — through the
unreleased-feature registry (linear-board), not a plain feature flag — so it
stays invisible until a developer flips its status to shipped.
Where to find it
Once enabled, a Linear row appears in the projects sidebar (between Job Monitor and Marketplace); clicking it opens the full-pane board view. The enable switch is Settings → Lab → "Linear board".
How it behaves
How to use it
- Enable it: Settings → Lab → toggle Linear board on. A "Linear" row appears in the sidebar.
- Connect (in the panel): open the Linear sidebar row and click Set up Linear (or the header gear, which carries a status dot). In the drawer, paste a personal API key — create one at linear.app → Settings → Security & access → Personal API keys. (Unlike Jira there is no site URL or email — Linear has one fixed API endpoint and the key is the only credential.)
- Click Save. A green dot + "Connected as …" confirms it works. The gear stays in the header to update the key later.
- Open the Linear sidebar row:
- Pick a team from the dropdown (top-left) — a team is your "board".
- See your columns (the team's workflow states: Backlog / Todo / In Progress / Done…) with issue cards (identifier, title, assignee, priority).
- Click a card to open the issue detail drawer on the right — description and comments (Markdown, rendered with the app's shared pipeline), state, assignee, priority, labels, and a link to open the issue in Linear.
Working issues (no browser needed):
- Create a new issue with + New issue (top-right) — write a title / description, optionally set priority, initial state, and labels.
- From the detail drawer you can Move the issue (pick any of the team's workflow states — Linear lets you set any state directly), Assign it (Assign to me, search a teammate, or Unassign), Comment (Ctrl+Enter to send), and edit the title, description, priority, and labels in place.
Hand an issue to an AI session:
- In the issue drawer, click Start session (or press S while the drawer has focus and you are not typing). The usual Start-session window opens (no Base branch picker), with an empty Message box for your own instruction and a collapsed, editable Linear issue details box that names the issue — its identifier, its link, and the title marked as text written in Linear — and tells the agent to read the full issue, description and comments itself. Nothing else from Linear is pasted in. The session receives your message, then a short "About this item" note Omniscio adds (the issue's ids and the routes to read, edit, comment on, move and assign it), then the issue details.
- The project picker starts on the project you last used for that Linear team
(found from the issue's identifier, e.g.
ENGinENG-142). Pick another and it is remembered for that team next time. - Once started, the drawer shows "N sessions from this issue" with Open for the newest. Archived or deleted sessions drop out of the count. Up to 5 sessions per issue (and 200 issues and teams) are remembered.
Getting around a big board:
- Drag a card to another column to move it (sets the issue's workflow state).
- Filter box (top-right) narrows the visible cards by text — identifier, title, assignee, or label.
- Load more at the bottom pulls in the next page when a team has lots of issues (Linear paginates by cursor).
Stop checking the board — let it come to you: turn on
Settings → Lab → "Linear issues assigned to me in Inbox". Omniscio then checks
Linear in the background (every few minutes, only while on) and surfaces your
assigned, not-done issues as rows in the unified Inbox — and when one of them
updates, its row pops back to the top so you notice. Click a row to jump to it on
the board; snooze or dismiss like any inbox item. Requires the Linear board
(above) enabled and connected. Kill switch for power users:
AMC_DISABLE_LINEAR_INBOX_POLL=1.
Your API key is encrypted at rest on your device and is never shown back to you or sent to the renderer once saved.
Troubleshooting
Each message below is the exact copy the app shows.
- "Invalid or unauthorized API key — create a new personal API key in Linear (with read & write access) and try again." — Linear refused the key, or the key's permissions cannot do what was asked. Create a new personal API key at linear.app → Settings → Security & access → Personal API keys, with read and write access, then update it with the header gear.
- "Linear is rate-limiting requests — wait a moment and try again." — wait, then retry.
- "Couldn't reach Linear — check your connection and try again." — the request never got an answer: offline, a proxy, or a Linear outage.
- "Linear had a server error (HTTP 503) — try again in a moment." — Linear's side failed (the number is whichever 5xx status it returned); nothing was changed.
- "Something went wrong talking to Linear. Please try again." — the catch-all for any other response. Retry, and if it persists re-enter the key.
- A team or issue is missing — check the team dropdown and that the issue is not archived in Linear.
Related
- jira-board.md — the closest analog; Linear is a 1:1 port of the same gating → service → IPC → store → UI shape (adapted from Jira's REST+ADF to Linear's GraphQL+Markdown).
- Contract:
.claude/memory/contracts/linear-board-contract.md— the invariants and the tests that lock them.
Last verified 2026-11-05