Developer workflow connector
Linear connector for governed AI agent access
Connect Linear with either an API key or a full OAuth token bundle.
Direct answer
OneQuery supports Linear for governed agent access.
Teams use the Linear connector to give AI agents bounded source API calls for endpoint-specific context while OneQuery keeps credentials centralized, limits access to approved sources, and preserves audit logs for review.
Agent workflow
What this connector enables
Linear becomes an approved OneQuery source instead of a secret copied into an agent prompt, shell session, or model tool. The agent receives a governed access path, and the source credentials stay behind OneQuery.
- Use bounded source API calls for endpoint-specific context for developer workflow context.
- Keep Linear credentials centralized and out of agent runtimes.
- Review agent access through OneQuery audit history instead of reconstructing direct service usage.
Setup checklist
Prepare the Linear connection
Use linear credentials and connect the source through the CLI. Keep credentials scoped to the data the agent is allowed to read.
- Choose either the API key shape (`apiKey`) or the OAuth shape (`accessToken` plus `linearOrganizationId`).
- If you use OAuth, keep the refresh metadata so the server can keep the connection valid over time.
FAQ
Linear connector questions
What is the OneQuery Linear connector?
The OneQuery Linear connector makes developer workflow context from Linear available to AI agents through bounded source API calls for endpoint-specific context. Connect Linear with either an API key or a full OAuth token bundle.
How do AI agents access Linear through OneQuery?
Agents call OneQuery instead of receiving raw Linear credentials. OneQuery keeps credentials centralized, applies source boundaries, and records access in audit logs while exposing bounded source API calls for endpoint-specific context.
How do I set up the Linear connector?
Prepare linear credentials and connect Linear from the OneQuery CLI. Start with this setup step: Choose either the API key shape (`apiKey`) or the OAuth shape (`accessToken` plus `linearOrganizationId`).