Laylight + Linear

What Laylight reads

Issues, projects, cycles, statuses, assignees, labels and comment history for the teams you connect.

Access is read-only and scoped to what you connect. Laylight does not write to, modify or delete anything in Linear.

What it adds to your context

Work in flight: what is planned, what is blocked, who owns it and how its state has changed over time.

How it works

You authorise Linear through OAuth and choose which teams Laylight indexes. State transitions matter as much as current state, because the history of what moved when is what answers questions about whether something is stuck. Issues are linked to the pull requests that close them and the conversations that raised them, so a ticket carries its full context rather than just its title.

Because Laylight resolves entities across every connected system, a Linear answer is not limited to Linear. The same customer, project or person referred to here is understood to be the same one referred to in the other systems you connect, so an answer drawn from Linear can be cross-checked against the document, ticket or thread elsewhere that describes the same thing.

What you will be able to ask

• What is blocking this project?
• What is in flight this cycle, and who is on it?
• When did this issue last move, and why?
• What did we plan for this cycle that did not get done?

Each answer names the Linear record it came from, with its timestamp, so you can open the source and check it rather than taking the summary on trust.

How the connection is authorised

You connect Linear through its own OAuth flow and choose the scope Laylight may index. Laylight never receives your Linear password, stores its access token encrypted, and loses access the moment you revoke the connection. See Security for the full detail.

Availability

Laylight is pre-launch and connectors are rolling out to waitlist customers. Join the waitlist to get access to the Linear integration, or see all integrations.