You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/linear.mdx
+23-2Lines changed: 23 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -21,8 +21,8 @@ Connect your Linear workspace to Codegen to enable agent interactions.
21
21
</Card>
22
22
23
23
<Note>
24
-
API access allows agents to interact with issues and projects according to
25
-
your permissions in Linear.
24
+
API access allows agents to interact with issues and projects according
25
+
to your permissions in Linear.
26
26
</Note>
27
27
28
28
## Capabilities
@@ -31,6 +31,7 @@ The Linear integration provides read and write access, enabling agents to manage
31
31
32
32
-**Read Access:** Fetch issue details, read comments, view project status, list team members.
33
33
-**Write Access:** Update issue status (e.g., to "In Progress", "Done"), add comments, link GitHub PRs to issues, create new issues, assign tasks.
34
+
-**Multi Agent Systems:** Create sub-issues and assign child agents to break down complex tasks into manageable pieces. [Learn more](#multi-agent-systems).
34
35
35
36
## How Agents Use Linear
36
37
@@ -40,3 +41,23 @@ Agents use the Linear integration to streamline project management:
40
41
-**Link Code:** Connect implemented changes (GitHub PRs) directly to the relevant Linear issue.
41
42
-**Provide Updates:** Post comments on issues with progress reports, results, or questions.
42
43
-**Create Tasks:** Generate new issues for follow-up work, bugs discovered, or sub-tasks.
44
+
45
+
## Multi Agent Systems
46
+
47
+
### Overview
48
+
49
+
Once you've enabled linear self assign, a codegen agent, which is assigned to a linear issue (or has been tagged in one), can spawn child agents by creating sub-issues and assigning itself to those sub issues. Once the child agents are finished with their tasks they will send a message to their parent agent notifying them that their task has been completed.
50
+
51
+
### Best Practices
52
+
53
+
#### Triggering the Child Agents
54
+
55
+
If you'd like to have codegen break up a linear issue into small issues and assign child agents to them you should instruct it to do so in the description of the original linear issue.
56
+
57
+
#### Shared Context/Code
58
+
59
+
If you'd like the child agents to share any context please instruct the parent to include this in the description of the sub-issues. You can also instruct the parent agent to include code that the child agents may need to share in the git branch it will provide to the child agents as scaffolding.
60
+
61
+
#### Grandfather Agents
62
+
63
+
If you'd like the child agents to themselves spin off child agents, you'll have to explicitly instruct the parent to do so. We do not recommend going beyond a depth of 3.
0 commit comments