A clear path forward
Why does an environment build get a 403 when my chat can read the repo?
For a shared environment build, check the workspace’s repository connection if checkout returns a 403. Your chat’s personal Git access does not prove that the build has the same permissions.
A 403 is an access refusal. Checkout is the step that fetches the code. If that step fails before setup commands run, check repo access rather than change the app's code.
- Find the failed build step and the repo it tried to fetch.
- Open Repos in the affected workspace. Check the provider's Workspace connections.
- Ask the right admin to check access to each repo in the setup, including scripts and code it depends on.
- Rebuild after access is fixed. Check that checkout succeeds and that the rest of the build finishes too.
If checkout succeeds but a later step fails, check that step on its own. Keep the build details, exact error and next result. Do not put a personal token in a build script to bypass shared-access setup.
Was this page helpful?
Still stuck? Try troubleshooting with Agent.
Still stuck? Try troubleshooting with Agent.
Copy this prompt and paste it into Agent. For a project issue, open the project where it happens first. Add what happened and anything you've already tried. Don't include passwords, API keys, database connection strings or payment-card details.
Copying does not open Agent or send a support request. Agent availability and usage depend on your account.
Can't open your project, or need another kind of help? Get help.