You can now assign a GitHub issue to a specific one of your agents, and it does the work as that agent, on that agent's own computer and git identity, through every review round, wait, and retry until merge.
A sticky performer. The issue's assignee picks the performer. The task is stamped with that agent when it starts and keeps it for its whole life, so the branch, the commits and the pull request carry that agent's git identity. Assign an issue to a GitHub handle Wallfacer does not recognize and your default agent takes it, with the miss recorded in the task's history.
Two mentions, two tasks. @-mention more than one of your agents in a single issue or comment and each one picks up its own task and does the work as itself. Mention an agent that is already working the issue and the comment folds into the task it has open, so a review round does not start a second run.
Routing beyond handles. A trigger can also match an agent by email, name, display name or job title, for events that carry one of those in place of a GitHub username.
Performs as. A step's computer and model come from the agent performing it, so choosing the performer is all a step needs. The trigger composer shows that routing as one line, and a trigger with no routing reads "Performs as the default agent".
Waits and retries. A waiting step can watch several events and wakes on whichever arrives first. After a task fails, repeating the action that started it, such as reassigning the issue, starts a fresh task.
Start here
Three things sit between you and an assignment that starts work.
A GitHub identity. Routing matches the issue's assignee against your agents' GitHub usernames, so an agent takes an issue only once it holds a token for the GitHub account it is assigned as. Open the agent, go to Apps & access, open Advanced work access, and connect a token for a dedicated bot account under GitHub.
A listening playbook. In your account's Handbook, give a playbook a When to run this sentence describing the assignment, and set Performs as to the issue's assignee. The trigger pickers offer only event types your account already receives, so get GitHub's issue events flowing to Wallfacer first, assignments included.
The assignment. Assign the issue to the agent's GitHub user and the task starts.
Assigning a GitHub issue to an agent walks through all three, and Playbooks covers the Performs as line.