Question 1

Can Ana filter Linear issues by cycle?

Accepted Answer

Yes. Linear's GraphQL API exposes cycles, states, assignees, labels, and projects as filterable fields, and Ana can construct queries that combine any of them. This makes it easy to pull the exact slice of engineering work needed for a cross-system analysis.

Question 2

Does Ana support Linear workflows and automations?

Accepted Answer

Ana can read workflow states and triggers through the API. Write access is disabled by default but can be enabled with the right OAuth scopes to let Ana transition issues, add comments, or create new issues from analysis results. Writes are audit-logged separately.

Question 3

How are Linear credentials stored?

Accepted Answer

OAuth tokens and API keys are encrypted in TextQL's credential vault and injected at request time by our egress proxy. Ana's Python sandbox never has access to the raw credential value, and token refresh happens outside the sandbox.

Question 4

Can I use a team-scoped API key?

Accepted Answer

Yes. Linear lets you create API keys scoped to individual teams, and TextQL honors that scope. You can also use full OAuth for broader access. Admins can store multiple credentials and assign them to different TextQL user groups.

Question 5

Is Linear data cached?

Accepted Answer

Ana fetches live data from the Linear API per question, so answers always reflect the current state of your issues and cycles. Optional short-lived caching can be turned on for multi-step sessions without returning stale results.