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
Add Multi Agent Systems documentation to Linear integration page (#1101)
This PR adds documentation about Multi Agent Systems to the Linear
integration page.
The changes include:
1. Adding a new "Multi Agent Systems" bullet point in the Capabilities
section with a link to the new section
2. Adding a new "Multi Agent Systems" section at the end of the page
with:
- Overview of how child agents work with Linear issues
- Best practices for triggering child agents
- Guidelines for sharing context and code between agents
- Information about "grandfather agents" (child agents creating their
own child agents)
These additions will help users understand how to effectively use Multi
Agent Systems with Linear integration.
---
[💻 View my work](https://codegen.sh/agent/trace/21175) • [About
Codegen](https://codegen.com)
---------
Co-authored-by: codegen-sh[bot] <131295404+codegen-sh[bot]@users.noreply.github.com>
Co-authored-by: jemeza-codegen <[email protected]>
Copy file name to clipboardExpand all lines: docs/integrations/linear.mdx
+28-2Lines changed: 28 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,28 @@ 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 in the settings [page](https://www.chadcode.sh/settings/permissions), a codegen agent, that has been assigned to a linear issue (or has been tagged in one), can spawn child agents
50
+
by creating sub-issues and assigning itself to those sub-issues. For each sub-issue that codegen assigns to itself a child agent will be spawned and tasked with completing the sub-issue. Once the child agents are
51
+
finished with their tasks they will notify their parent by sending it a message. The parent will then incorporate the child's work into its own as appropriate.
52
+
53
+
### Best Practices
54
+
55
+
#### Triggering the Child Agents
56
+
57
+
If you'd like to have codegen break up a linear issue into smaller issues and assign them to child agents you should instruct it to do so in the
58
+
description of the original linear issue.
59
+
60
+
#### Shared Context
61
+
62
+
Before creating sub-issues and assigning them to child agents the parent agent will produce scaffolding in the form of a git branch and include details
63
+
of this branch in the description of the sub-issues. The child agents will then work off of this scaffolding branch. If you have specific scaffolding requirements
64
+
or context you'd like the child agents to share, please include them in the description of the parent issue.
0 commit comments