Workers on GitHub
An AI worker set to work on GitHub hands its tasks to the code agent in your repository and brings the pull request back to the task for review.
Projik doesn’t run code. An AI worker set to Works on GitHub hands each of its tasks to a code agent that runs in your own repository, and its pull request comes back to the task for review. Pixel, the starter code worker, works this way.
A code task from Projik to a merged pull request
Video coming soon2:00
What you need#
- GitHub connected, and the project linked to a repository. See GitHub. The worker’s tasks must be in a project linked to a repository.
- A code agent in that repository. Projik is built to work with Claude Code running in GitHub Actions. The agent’s workflow must start when it’s mentioned in an issue comment, and must allow comments from Projik’s GitHub app to start it. Many workflows ignore comments from apps unless they’re allowed. The agent runs on your GitHub account with your own model key, so its work doesn’t use Projik’s AI allowance.
- A worker set to Works on GitHub. An owner or admin chooses it under Who does its work on the worker’s page. How it should work holds standing instructions for the agent, such as “Run the tests before opening the pull request. Keep changes small and follow the existing style.”
The hand-off#
- Invite the worker to a task. With Auto-accept invitations on, the task moves to In progress at once.
- Projik makes sure the task has an issue in the project’s repository, and opens one if it hasn’t.
- Projik comments on that issue. The comment starts by mentioning the agent (
@claude) and asks it to work on the issue and open a pull request. It includes the task’s title and description, the team’s latest comments from Projik (up to eight) and the worker’s standing instructions. It asks for the pull request’s description to sayFixes #and the issue number, which is how the pull request finds its way back to the task. - The worker comments on the task: “Handed to the code agent on GitHub”, with a link to the issue.
The worker’s page lists the hand-off under Recent runs, for example “Handed to GitHub: acme/website#12”.
While the agent works#
The agent’s comments on the issue appear on the task as the worker’s comments, each with a link back to GitHub. Claude Code posts one comment and edits it as it goes, so the comment on the task updates in place. Comments that people write on the issue stay on GitHub.
The pull request and review#
When a pull request that names the issue is opened, the task moves to In review and the worker comments with the link: “Opened a pull request for review”. Review the pull request on GitHub as you would any other.
- Merging the pull request finishes the task. You don’t need to mark it done in Projik.
- To ask for changes, comment on the task and choose Send back to progress. Projik hands the task over again, with your comments, and asks the agent to address them on its existing pull request. When the agent pushes new commits to that pull request, the task returns to In review.
A pull request also links to the task if its title or branch names the task’s key, as long as the repository is linked to the task’s project.
When something goes wrong#
In each case the worker says what happened in a comment on the task. If the task was still In progress, it moves to In review so someone looks at it.
| What happened | What the worker tells you |
|---|---|
| The agent hit an error | “The code agent hit an error on GitHub”, with a link. Check its job run on GitHub. |
| The agent finished without a pull request or a branch | Its answer is on the task and on GitHub. |
| Nothing came back for two hours: no pull request and no comment from the agent | “Nothing has come back from the code agent on GitHub in 2 hours.” Check that the workflow ran on the issue. |
| The pull request was closed without being merged | “The pull request … was closed without being merged.” |
To hand the task over again, move it back to In progress. If a closed pull request means the work is no longer wanted, finish or reassign the task instead.
Only Claude Code’s own “finished” and “error” messages are read as the agent’s last word. With another agent, the wait ends when a pull request opens or after two hours of silence.
When the task can’t be handed over#
The hand-off fails, and the worker says why on the task, when:
- the project isn’t linked to a repository (“Link the project to a repository in its settings, then move this back to In progress”);
- GitHub isn’t connected for the workspace;
- the task already has an issue in a different repository from the one the project is now linked to. Create a new task for the new repository.
The task stays In progress with the worker. Fix what’s missing, then move the task out of In progress and back to hand it over again.
Plan#
Workers on GitHub need the Business plan, and are included in a new workspace’s trial. On another plan the worker keeps its settings but hands nothing over: its runs are listed as Skipped. A task that was already handed over is still followed to its pull request.