Skip to main content

​
Overview

The Linear connection lets Qontext read issues, projects, and documents from your Linear workspace and sync them into your context repository. Each record becomes a structured text document (its key fields together with the discussion around it) so your agents can retrieve the planning context behind your product: what is being built, why, where it stands, and what was said about it. Qontext connects to Linear through the GraphQL API over OAuth.
Qontext only reads data; it never creates, edits, or deletes anything in Linear. Access is always bounded by the connected user’s own Linear permissions, so Qontext can only sync what that account can already see.
Supported objects: Unsupported:
Use a dedicated integration user in your Linear workspace to ensure a stable and uninterrupted connection.
Create a service account such as qontext@yourcompany.com, add it to your Linear workspace, and give it access to the Linear teams you want Qontext to sync. This prevents sync disruptions when employee accounts or permissions change.
The integration user will:
  • Authenticate the connection between Qontext and Linear.
  • Access the selected issues, projects, and documents with read-only permissions.
Qontext requests a single Linear scope, read, and uses OAuth with PKCE. It deliberately does not request admin, which Linear only requires for managing webhooks.

​
Setting up the connection

You can connect Linear from your Qontext workspace, authorize access with your Linear account, then choose what to sync and how often. Linear needs no workspace URL or subdomain, so authorizing is a single step.
You can also manage all your credentials, including Linear, from the Sources page.
1

Open Sources in your workspace

In the Qontext app, open your workspace and go to the Sources tab, then click + Connect data source.
2

Select Linear as the data source

Choose Linear from the list of available data sources. This starts the Linear connection flow.
3

Connect your Linear account

You can reuse existing Linear credentials (if you have already connected this account to Qontext) or create a new connection.If you create a new credential, sign in with Linear when prompted. On the consent screen, review the requested access and authorize Qontext to read your workspace.
4

Configure what to sync (filters)

Choose which projects, issues, and documents Qontext should sync into your context repository. By default all three are included and scoped to everything in the workspace.See Filtering what gets synced below for the full set of options.
5

Set sync frequency

Choose how often Qontext should refresh data from Linear (e.g. daily, weekly, monthly). More frequent syncs keep the context repository up to date but use more resources.
6

Review and create connection

Review your choices (workspace, selection, frequency), then confirm to create the connection. Qontext will start the initial sync shortly after.

​
Filtering what gets synced

Linear filters are organized as three independent rules: one for projects, one for issues, and one for documents. Each rule can be switched off entirely, and each carries its own scope, because the same word means different things per content type. An issue belongs to exactly one Linear team, a project can span several, and a document hangs off whichever container it was created in. By default all three rules are on and set to sync everything.
  • All: every project in the workspace.
  • Filtered: narrow by Linear team, by status (Backlog, Planned, In Progress, Paused, Completed, Canceled), by project label, by project lead, and by last-updated date.
  • Specific: hand-pick individual projects.
  • All: every issue in the workspace.
  • By team: only issues belonging to the Linear teams you select.
  • From included projects: only issues belonging to the projects your Projects rule already includes, so the two selections stay consistent.
An issue does not have to belong to a project, and in most workspaces many do not. The From included projects mode therefore also offers a checkbox to include issues without a project, which adds those back.
Whichever scope you pick, issues can be narrowed further by state (Triage, Backlog, Todo, In Progress, Done, Canceled), by issue label, by assignee, and by last-updated date.
Issue labels and project labels are separate things in Linear, so they are chosen in separate pickers and cannot be used interchangeably.
  • All: every document in the workspace, whether it is attached to a project, a Linear team, or an issue.
  • From included projects and issues: only documents attached to a project or an issue that is already in scope, which keeps your documents aligned with the rest of the selection.
Documents can also be limited by last-updated date. Documents attached to an initiative are not synced in either mode.

​
Sync latency

The initial sync time depends on how many issues, projects, and documents are in scope. Large workspaces can take up to 6 hours to fully sync.
Subsequent syncs are incremental: Qontext processes only the records that were added or changed since the last sync, which runs much faster than the initial sync.

​
Managing permissions

​
Linear OAuth scope

When connecting, you authorize Qontext against your Linear workspace. Qontext requests one scope:
Qontext uses this access only to read. It never creates, edits, or deletes anything in Linear, and because read operates as the connected user, Qontext can only ever see what that account can see.

​
Linear permissions

  • Use a single integration user to manage Linear access for Qontext to avoid permission conflicts.
  • If a project, Linear team, or document does not appear during filter setup, check that the connected account has access to it in Linear.
  • Linear access tokens are short-lived, and Qontext refreshes them automatically in the background. If a refresh is rejected, for example because the authorization was revoked in Linear, the connection stops syncing and prompts you to reconnect it from the Sources tab.

​
FAQ

Any workspace member with a Linear account that has access to the relevant content. Qontext syncs exactly what that account can see, so an account with access to every Linear team gives the most complete result.
No. Qontext only reads issues, projects, and documents. It never creates, edits, or deletes data in Linear, and it never comments on an issue.
Yes, by default. An issue in Linear belongs to exactly one Linear team but does not need a project. If you scope issues to From included projects, use the include issues without a project checkbox to keep those issues in scope.
They are retrievable as part of the record they belong to. A comment thread is synced with its issue, and project updates are synced with their project, so agents read the discussion in the context that gives it meaning rather than as a detached fragment.
Yes. You can create multiple Linear connections from the Sources tab in your Qontext workspace. Add each Linear workspace as a separate data source.
Manual refresh is available via the Sources tab. Navigate to the respective Linear connection and open the Syncs tab. In the sync settings, you can select Resync all data.
Disconnecting stops further syncs. Content already synced from Linear remains in your context repository. For data removal, contact support@qontext.ai.
By default, Qontext only syncs content the connected Linear account can access. Additionally, you can add filters to every connection as described in the setup flow.