Troubleshooting GitHub

Published

Updated

Wallfacer connects to GitHub through your account's agent: you attach a token for the GitHub account the agent acts as, and the agent clones repos, pushes commits, and opens or reviews pull requests as that identity. Manage the token under Team > your agent > Integrations > GitHub. Here's how to fix the most common integration issues.

Token Rejected

Symptom: You paste a token to connect the agent, and the connection fails or shows an error.

Cause: The token is invalid, has expired, or lacks repository access. Wallfacer validates the token when you connect and resolves the GitHub account from it.

Fix: Generate a fresh token for the GitHub account the agent should act as, with access to the repositories you want. Use a dedicated bot account so the agent's activity is clearly attributable. Paste the new token under Team > your agent > Integrations > GitHub and connect again.

Can't Edit the Connection

Symptom: You can see the agent's GitHub section but cannot connect or disconnect.

Cause: Managing agent credentials is admin or owner work. Members without that role can view the connection but not change it.

Fix: Ask an account admin or owner to connect or update the agent's GitHub token.

Repository Not Showing

Symptom: A repository doesn't appear when creating an environment or browsing issues.

Cause: The agent can only see repositories its GitHub token has access to. If the repo belongs to an organization, the org may need to grant the token access, or SSO authorization may be required.

Fix: Make sure the token's GitHub account has access to the repo (push access for environments). For organization repositories, grant the token access to that organization, and complete any SSO authorization the org requires. Then reconnect the token on the agent if you changed its scope.

Clone Failures Inside VM

Symptom: The VM boots but fails to clone the repository. You see errors related to authentication or access during the clone step.

Cause: Usually a token issue. The agent's GitHub token may have expired or been revoked, or it may not have access to the repo.

Fix: Attach a fresh token to the agent under Team > your agent > Integrations > GitHub. If the repo belongs to an organization, make sure the token's account has access to that organization.

Pinned Source Branch Missing

Symptom: Environment setup fails during source cloning and names a requested branch, repository, and available remote branches.

Cause: The manifest pins a branch that no longer exists on the remote. Clone stops before retrying because another attempt cannot restore that branch.

Fix: Change the source's branch in the environment manifest to an existing branch, or omit it to follow the repository default. Regenerate the base snapshot before starting a new session. See Manifest Reference for how branch pins work.

Actions Attributed to the Wrong Account

Symptom: Commits and pull requests show up under an unexpected GitHub account.

Cause: Work on GitHub runs under the agent's connected identity, not under any person's account. If the token belongs to your personal account, the agent acts as you.

Fix: Connect the agent to a dedicated bot account instead of a personal one, so its activity is clearly separate and attributable. Update the token under Team > your agent > Integrations > GitHub.