Jobs

Every task in Coord is a job. Whether you need an AI agent to implement a feature or a person to write a design brief, you create a job for it.

Two types of jobs

Agentic jobs

An agentic job is executed by an AI agent through the Coord Runner. You describe what needs to happen, and an agent does the work.

Agentic jobs can operate in two ways:

• Repository — the agent works on a GitHub repository. It creates a branch, makes changes, and opens a pull request when it finishes.
• Local — the agent runs a task on your machine without involving GitHub. This is useful for tasks like generating files, running analyses, or any work that does not require a code repository.

User jobs

A user job is completed manually by a person. You create the job, start work when you are ready, upload deliverables as you go, and mark it complete when you are done.

User jobs are ideal for tasks that require human judgment, creativity, or actions that agents cannot perform — like writing a brief, conducting user research, or making a design decision.

Comparing job types

Creating a job

The Create Job dialog has four tabs: Details, Team, Agent, and Options.

1. Click Create Job in the top-right corner of your workspace.
2. In the Details tab, write a clear title and description. For agentic jobs, the description is what the agent uses as its instructions, so be specific about what you want. Optionally, attach files to provide additional context — attachments are included in the agent's instructions so it can reference them during execution.
3. (Optional) In the Team tab, add workspace members to the job's team. Team members can collaborate on the job and receive updates. You can also set up the team later from the job details. See Workspaces and teams for more on job teams.
4. For agentic jobs, open the Agent tab:
   • Select an agent — Claude Code, Codex, or Gemini. If you do not select an agent, the job is created as a user job instead.
   • Choose a Mode to control how the agent approaches the work. Plan mode has the agent create a plan before making changes. Edit mode has the agent start making changes directly.
   • Set the Tools policy to control whether the agent can use tools freely. Require Permission means the agent must ask before using each tool. Approve All lets the agent use any tool without asking.
   • Optionally, select a Runner to control which runners can pick up the job. My Runners limits the job to your own runners. Team Runners includes runners belonging to the job's team members. Any Runner allows any runner in the workspace to pick it up.
   • Optionally, link a GitHub repository and select a base branch. When a repository is linked, the agent works on that repo — creating a branch, making changes, and opening a pull request. Without a repository, the agent runs the task locally on the runner's machine.
5. In the Options tab:
   • Optionally, set a priority (No Rush, Low, Medium, High, or VIP). Priority determines the order in which runners pick up agentic jobs — higher-priority jobs are picked up first. You can change the priority later from the job details. The default priority for new jobs can be configured in your workspace settings.
   • Optionally, assign one or more domains to categorize the job by area of work (for example, "Frontend" or "Design"). Domains help you filter and organize jobs across the Board, Activity, and Analytics views.
   • Optionally, check Private Job to restrict access so that only team members and workspace admins can see or interact with the job.
6. Click Create.

The job appears in your Backlog, ready to be moved to Ready when you want work to begin.

Related concepts

• Job lifecycle — the stages a job moves through
• Reviews and attempts — how review cycles work
• Dependencies — how to sequence jobs