Create jobs from GitHub issues
Use
Create Coord jobs directly from GitHub issues by adding #coord tags to the issue body.
This page is a reference for the #coord tag syntax. Bookmark it and come back when you're ready to create your first issue-based job.
Before you start
- You have the GitHub integration set up with Coord Bot installed on your organization.
- Your GitHub account is linked to your Coord account. Go to Account Settings > Linked Accounts to verify.
How it works
When you create a GitHub issue with #coord tags in the body, Coord Bot detects the tags, resolves your workspace, and creates a job. Coord Bot then comments on the issue with a link to the new job and a summary of its settings.
Create a user job
Add #coord to a GitHub issue body to create a user job:
Fix the broken login form on the signup page.
#coordCoord creates a user job in your workspace with the issue title as the job title and the issue body as the description.
Create an agentic job
Add #coord:agent:claude (or another agent) to create an agentic job that runs on the repository where the issue was created:
Refactor the authentication middleware to use the new token format.
#coord:agent:claudeThe agentic job automatically targets the repository where the issue lives.
Specify a workspace
If your GitHub organization is linked to a single workspace, Coord resolves it automatically. If you belong to multiple workspaces linked to the same organization, add a workspace tag:
Fix the API timeout bug.
#coord:agent:claude
#coord:ws-slug:my-projectFour ways to specify a workspace:
| Tag | Description |
|---|---|
#coord:ws-slug:<slug> | Workspace slug (the short name you see in Coord URLs) |
#coord:ws-alias:<alias> | Your personal workspace alias (set in Coord Settings) |
#coord:ws:<name> | Workspace name (must be unambiguous) |
#coord:ws-id:<id> | Workspace ID (for automation) |
The workspace slug is often the easiest option — you can find it in your browser's address bar when viewing a workspace (the part after /w/).
Set up a workspace alias
Workspace aliases are personal short names that make tagging easy.
- Open your workspace in Coord.
- Open Workspaces under Settings in the sidebar.
- Under GitHub Alias, enter a short name (for example,
mpfor "My Project"). - Click Save.
You can now use #coord:ws-alias:mp in any issue.
Configure job settings
Add tags to customize the job. All tags are optional — Coord uses sensible defaults.
Agent options
| Tag | Values | Default |
|---|---|---|
#coord:agent:<type> | claude, codex, gemini | (required for agentic jobs) |
#coord:agent-mode:<mode> | plan, edit | plan |
#coord:agent-tools:<mode> | require-permission, approve-all | require-permission |
#coord:repo-branch:<branch> | Any branch name | Repository default branch |
Both #coord:agent:claude and #coord:agent-type:claude are accepted.
Job options
| Tag | Values | Default |
|---|---|---|
#coord:priority:<level> | vip, high, medium, low, no-rush | medium |
#coord:stage:<stage> | backlog, staged, ready | backlog |
#coord:private-job:<value> | yes, no | no |
#coord:domains:<name> | Any domain name in your workspace | (none) |
You can add multiple domain tags — they are additive:
#coord:domains:frontend
#coord:domains:authFull example
Here is an issue body that creates a fully configured agentic job:
The signup form submits twice when the user double-clicks the button.
Add a debounce guard to the submit handler.
#coord:agent:claude
#coord:ws-alias:acme
#coord:agent-mode:edit
#coord:agent-tools:approve-all
#coord:priority:high
#coord:domains:frontend
#coord:stage:ready
#coord:repo-branch:developThis creates a high-priority agentic job with Claude in edit mode, targeting the develop branch, assigned to the frontend domain, and moved directly to Ready.
Edit and retry
If Coord cannot create the job (for example, you forgot a workspace tag), Coord Bot comments on the issue explaining what went wrong.
To fix it, edit the issue body to add or correct the tags. Coord detects the edit and retries job creation.
If a job has already been created and is still in the Backlog, editing the issue updates the job settings. Jobs that have moved past the Backlog are not affected by edits.
Troubleshooting
Coord Bot did not comment on my issue
- Verify Coord Bot is installed on the repository's organization.
- Check that the issue body contains at least one
#coordtag. - Issues created by Coord Bot (with the
coord-joblabel) are intentionally skipped.
"Couldn't find an account" error
Your GitHub account is not linked to a Coord account. Go to Account Settings > Linked Accounts in Coord and connect your GitHub account.
"Couldn't determine which workspace" error
Your organization is linked to multiple workspaces. Add a #coord:ws-alias, #coord:ws, or #coord:ws-id tag to specify the target workspace.
Agent-specific tags were ignored
You added tags like #coord:agent-mode:plan without specifying an agent. Add #coord:agent:claude (or another agent) to create an agentic job. Without an agent tag, Coord creates a user job and ignores agent-specific settings.
Next steps
- Set up GitHub integration — install Coord Bot and link repositories
- Create your first job — create jobs from the Coord UI
- Review agent work — review pull requests created by agents