Skip to main content
Nuphos connects to Linear through OAuth — you authorize once in the browser and there’s no API key to manage. The agent can then work with issues in your workspace: file a ticket for an incident it found, comment progress, and close the issue when the fix is verified.

​
Connect

1

Start the authorization

In Connectors → Connect → Linear, click Authorize Linear. Your browser opens Linear’s consent screen.
2

Approve the request

Nuphos asks for read and write access — enough to read issues, teams, and workflow states, and to create and update issues and comments.
3

Return to Nuphos

Linear redirects back to the desktop app and the connection completes automatically — there’s nothing to copy and paste.
The access token is stored encrypted. Re-authorizing the same workspace updates the existing connection instead of creating a duplicate.

​
In the Nuphos app

There’s no separate Linear browsing surface — the connector’s value shows up inside agent sessions, where issues the agent files or updates are linked in the conversation. The binding itself lives in Connectors, where an Administrator can manage its allow-list or remove it.

​
What the agent can do for you

The agent can create issues, comment on them, look up and search issues, and move them through your workflow states. The pattern that makes this shine is pairing it with your infrastructure connectors:
  • “Investigate the elevated error rate — and file a Linear issue with what you find.” — the agent diagnoses via your cloud and observability connectors, then opens a ticket with the evidence.
  • As it works a fix, it comments progress on the issue, and when the fix is verified it moves the issue to Done.
  • Triggers can kick off sessions that track their work in Linear without you in the loop for the paperwork.

​
Permissions & authorization

Two boundaries govern what happens through this connector:
  • Hard boundary — who can use it. Only team Administrators can connect or remove the binding, and they can restrict it to specific members with a member allow-list. Within a session the agent only holds credentials you explicitly selected, re-checked on every request.
  • Soft boundary — what the agent may do with it. Reads are free-form; creating or changing issues goes through plan approvals unless you gave an explicit instruction (e.g. “file a ticket for this”), with Auto-authorization governing the individual actions.
The outer limit is the OAuth grant — read and write on issues and comments, and nothing beyond it.

​
Good to know

Issues and comments are authored by the Nuphos app in Linear, not by the person who authorized the connection — activity is clearly attributable to the agent.