GitHub Integration

Wallfacer connects to GitHub so your agent can clone your repos, create branches, commit code, and open or review pull requests.

Every task runs as an agent, and the agent holds its own GitHub identity. You connect GitHub once on the account's agent, and all of its work on GitHub uses that identity. People on your account do not connect their personal GitHub accounts.

When You Need GitHub

GitHub is required only when your work uses a code repository. An environment that clones a repo needs a connected GitHub account to clone it, create branches, and push commits. An environment with no repository (an empty sources list in its manifest) needs no GitHub connection, so you can finish setup and start tasks on it without connecting an account.

Setup reflects this. The GitHub step is skippable and shows Not needed when none of your active work requires a repository. You're prompted to connect only when an environment actually clones code.

A connected identity still reaches a computer that clones nothing. Whenever the agent holds a GitHub token, Wallfacer puts it on the computer whether or not the computer declares any repository, so the agent can create a repository, clone one you point it at, or open a pull request on a computer that started empty. Those commits carry the connected account's name and email.

An agent with no GitHub token gets no GitHub access on that computer, which is how an environment with no repository has always behaved.

Connecting Your Agent to GitHub

1. Go to Agents and open your account's agent.
2. In Credentials, find the GitHub section.
3. Paste a token for the GitHub account the agent should act as. Use a dedicated bot account so the agent's work is clearly attributable and separate from any person's activity.
4. Tap Connect.

Once connected, the section shows the account the agent is connected as. Connecting GitHub is admin or owner work, so members without that role see the credentials but cannot change them.

During onboarding, the Connect your agent to GitHub setup step takes you to the same place.

What the Agent Accesses

With GitHub connected, the agent can:

• Read your repositories, branches, and issues.
• Create branches and push commits.
• Open and review pull requests.

All of these actions use the agent's GitHub token and appear as the connected account's activity on GitHub, not as any person's.

Working from Issues and Pull Requests

Three ways to put a GitHub issue or pull request in front of an agent.

From the new task screen. Click New Chat, pick the agent, and the empty task screen offers Fix an issue and Work on a pull request above the input. Both open a picker over the repos the agent's computer clones:

• Search by title or number, or browse the list.
• Issues and pull requests each have their own pill, so you land directly in the kind you want. The + menu beside the input opens the same picker unscoped.
• Each row shows its title, repo name, and number.

Select one and send. If you have not typed anything, Wallfacer writes the message for you: one issue sends Fix <issue title>, several send "Fix the attached issues and pull requests".

By assigning it on GitHub. Point a playbook trigger at the issue's assignee, and assigning the issue to the agent's GitHub account starts the task with the issue attached. See Playbooks.

Over the API. POST /v1/accounts/{account}/tasks takes attachments when you create a task, and POST /v1/accounts/{account}/tasks/{task}/attachments adds them afterwards. Pass the GitHub URL as the attachment's uri. See Task Attachments.

However it arrives, Wallfacer turns the issue into an attachment with resolved content and the original GitHub URL, preserving a reference back to your existing tracking.

Disconnecting GitHub

Open the agent in Agents, go to Credentials > GitHub, and tap Disconnect.

Steps that run as this identity then have no GitHub access until you connect a token again. Reconnect at any time by pasting a new token.