Most software engineering organizations track and manage their codebase through GitHub, and use project management tools like Asana, Jira, or even GitHub's Projects to coordinate work. Across these systems, engineers are frequently performing the same repetitive workflows: triaging and addressing bugs, updating documentation, or implementing well-defined changes for example.

Coder Tasks provides a method for automating these repeatable workflows. With a Task, you can direct an agent like Claude Code to update your documentation or even diagnose and address a bug. By connecting GitHub to Coder Tasks, you can build out a GitHub workflow that will for example:

1. Trigger an automation to take a pre-existing issue

1. Automatically spin up a Coder Task with context from that issue and direct an agent to work on it

1. Focus on other higher-priority needs, while the agent addresses the issue

1. Get notified that the issue has been addressed, and you can review the proposed solution

This guide walks you through how to configure GitHub and Coder together so that you can tag Coder in a GitHub issue comment, and securely delegate work to coding agents in a Coder Task.

The below steps outline how to use the Coder[Create Task Action GHA](https://github.com/coder/create-task-action) in a GitHub workflow to solve a bug. The guide makes the following assumptions:

- You have access to a Coder Server that is running. If you don't have a Coder Server running, follow our[Quickstart Guide](https://coder.com/docs/tutorials/quickstart)

- Your Coder Server is accessible from GitHub

- You have an AI-enabled Task Template that can successfully create a Coder Task. If you don't have a Task Template available, follow our[Getting Started with Tasks Guide](https://coder.com/docs/ai-coder/tasks#getting-started-with-tasks)

- Check the[Requirements section of the GHA](https://github.com/coder/create-task-action?tab=readme-ov-file#requirements) for specific version requirements for your Coder deployment and the following

- GitHub OAuth is configured in your Coder Deployment

- Users have linked their GitHub account to Coder via`/settings/external-auth`

This guide can be followed for other use cases beyond bugs like updating documentation or implementing a small feature, but may require minor changes to file names and the prompts provided to the Coder Task.

In your repository, create a new file in the`./.github/workflows/` directory named`triage-bug.yaml`. Within that file, add the following code:

name:Start Coder Task

on:

issues:

types:

-labeled

permissions:

issues:write

jobs:

coder-create-task:

runs-on:ubuntu-latest

if:github.event.label.name == 'coder'

steps:

-name:Coder Create Task

uses:coder/create-coder-task@v0

with:

coder-url:${{ secrets.CODER_URL }}

coder-token:${{ secrets.CODER_TOKEN }}

coder-organization:"default"

coder-template-name:"my-template"

coder-task-name-prefix:"gh-task"

coder-task-prompt:"Use the gh CLI to read ${{ github.event.issue.html_url }}, write an appropriate plan for solving the issue to PLAN.md, and then wait for feedback."

github-user-id:${{ github.event.sender.id }}

github-issue-url:${{ github.event.issue.html_url }}

github-token:${{ github.token }}

comment-on-issue:true

-Pass as a prompt to the Coder Task

-Post an update on the GitHub ticket with a link to the task

You must set the following inputs as secrets within your repository:

-`coder-url`:the URL of your Coder deployment, e.g. https://coder.example.com

-`coder-token`:follow our [API Tokens documentation](https://coder.com/docs/admin/users/sessions-tokens#long-lived-tokens-api-tokens) to generate a token. Note that the token must be an admin/org-level with the "Read users in organization" and "Create tasks for any user" permissions

You must also set `coder-template-name` as part of this. The GHA example has this listed as a secret, but the value doesn't need to be stored as a secret. The template name can be determined the following ways:

-By viewing the URL of the template in the UI, e.g. `https://your-coder-url/templates/<org-name>/<template-name>`

-Using the Coder CLI:

Add the `coder` label to that GitHub issue. You should see the following things occur:

-A comment is made on the issue saying `Task created:https://your-coder-url/tasks/username/task-id`

-A Coder Task will spin up, and you'll receive a Tasks notification to that effect

-You can click the link to follow the Task's progress in creating a plan to solve your bug

We recommend that you further adapt this workflow to better match your process. For example, you could:

-Modify the prompt to implement the plan it came up with, and then create a PR once it has a solution

-Update your GitHub issue template to automatically apply the `coder` label to attempt to solve bugs that have been logged

-Modify the underlying use case to handle updating documentation, implementing a small feature, reviewing bug reports for completeness, or even writing unit test

-Modify the workflow trigger for other scenarios such as:

-Read users in organization

-Create tasks for any user

1. Verify the template name using:`coder templates list --org your-org-name`

"title":"Security\u0026 Boundaries",

"description":"Learn about security and boundaries when running AI coding agents in Coder",

"path":"./ai-coder/security.md"

},

{

"title":"Create a GitHub to Coder Tasks Workflow",

"description":"How to setup Coder Tasks to run in GitHub",

"path":"./ai-coder/github-to-tasks.md",

"state": ["beta"]

}

]

},