Agent
Linear
Assign a Linear issue to Codebot, or mention it in an issue. It works in a sandbox, reports progress in Linear, and opens a pull request.
Connect Linear
An admin connects Linear from Settings → Integrations or Agent → Places; its settings are on Settings → Integrations → Linear. A Linear workspace admin approves the install. After that, Codebot shows up in Linear as a user you can assign issues to and mention.
If the row says Reconnect needed, the install is missing permissions Codebot needs: click Reconnect Linear.
Using Codebot in Linear
- Assign (delegate) an issue to Codebot to have it implement the issue. It works on a branch and opens a pull request when it’s allowed to push.
- Mention @trycodebot in an issue comment to ask a question or give it a follow-up.
Progress shows in the issue’s agent session in Linear as it works. When it’s done it replies there, links the pull request to the issue, and, if it may update Linear issues, moves a delegated issue from triage or backlog to your team’s first started state.
To stop a run, use Stop in the agent session in Linear.
Which repository
Each issue is worked on in one repository, picked in this order:
repo:owner/namewritten in the message;- a
repo:owner/namelabel on the issue; - a project override for the issue’s project;
- the team repository for the issue’s team;
- your organization’s only connected repository, if there is just one.
Set team repositories and project overrides on Settings → Integrations → Linear. Reconnect and Disconnect are in the ⋯ menu at the top of that page. A route can also set the branch to start from; otherwise Codebot starts from the repository’s default branch. Use Check an issue with an issue ID like ENG-128 to see where it would go.
If no repository matches, Codebot replies in Linear with the repositories it can use instead of guessing.
Branches and pull requests
All work on an issue happens on one branch: Linear’s suggested branch name for the issue, or codebot/ENG-128 if there is none. Follow-ups continue on the same branch and the same pull request.
Follow-ups
Reply in the issue to continue. Codebot keeps the issue’s sandbox for a while after each run, so a follow-up resumes with the same checkout and memory of the conversation. After a long idle period the sandbox is cleared; the next run starts fresh from the branch and the issue’s history.