Once Linear is connected at organization scope, you can put Indent on an issue and follow what it does without leaving Linear. To connect the integration first, see Connecting Linear.
Delegate an issue to Indent
There are three ways to start Indent from an issue:
- Delegate the issue to Indent. Indent owns the issue and implements it.
- @-mention Indent in the issue description. Indent answers what the description asks, and implements only if you ask it to.
- @-mention Indent in a comment. Indent answers in that thread, and implements only if you ask it to.
Delegation and assignment are separate fields in Linear, so delegating to Indent leaves the issue’s assignee alone.
To keep going, reply in the thread Linear opened. Every reply there reaches Indent, so you don’t need to mention it again.
What Indent reads
Indent gets the issue’s identifier, title, URL, description, and assignee, plus the comments in the thread it was mentioned in. A new mention on the same issue adds the comments posted since the last turn. A reply in a thread Indent is already working in carries only that reply.
It doesn’t read the issue’s labels, status, project, cycle, parent or sub-issues, other comment threads, or files attached to the issue. Ask for anything else in your request. The Linear tools are available from the first turn of the session, so Indent can also look it up.
One session per issue
Indent keeps one session per issue. A second delegation or mention on the same issue continues that session, and Indent picks up from what it has already done. Each Linear thread is answered on its own. Two requests on the same issue run one after the other.
The session is titled with the issue identifier, such as ENG-231: Rate-limit the export endpoint,
and is visible to your organization.
Follow the work
Linear opens a thread for each delegation or mention, and Indent posts its progress there as it works. Progress updates arrive as thoughts, and the last message of a turn is the response. A turn that fails ends with an error in the thread instead.
- Each thread has an Open in Indent link, and the issue gets an Indent session attachment.
- A pull request Indent opens is linked on the thread, and attached to the issue when the issue is delegated.
- On a delegated issue, Indent’s answer also lands as a comment on the issue.
- Images render inline. Other files are attached as links. A file over 25 MiB links to the session in Indent instead.
- If Indent has a question for you, it posts a link to answer it in Indent. Commenting in Linear instead dismisses the question and steers the run.
On a delegated issue, Indent opens pull requests as the issue’s assignee, falling back to whoever delegated the issue. The assignee needs an Indent account for that.
To stop a run, use Linear’s Send stop request. Indent replies that it was stopped before it finished.
Teammates who don’t have an Indent account
Indent matches whoever delegates or mentions it by their Linear email address. If your organization signs people up automatically by email domain, a teammate gets an account there and then.
Without a match, Indent replies in the thread and the run doesn’t start. A Linear email that matches no Indent account gets a link to sign up. One that matches several accounts gets asked to link their Linear account in Indent.
Limits
Indent doesn’t change an issue’s status, assignee, or labels on its own. Ask for it in your request.
A tool call that needs your approval isn’t shown in Linear. The run waits until you approve it in Indent, so open the session from the thread if a run goes quiet.
Delegating or mentioning Indent from a Linear project or document does nothing. Use an issue.