A clear path forward
Why does GitLab ask me to reconnect or fail to create a merge request?
Check the GitLab source-control connection in the workspace where the action fails. A connected badge on another GitLab tool does not prove that Agent can change the code.
A merge request is GitLab's proposed code change for review. Agent needs write access to the target repo, not just a tool that can read data.
- Open Repos in the affected workspace. Check the GitLab account and target project.
- Confirm that Agent uses GitLab Source Control for code work, not a separate read-only tool.
- For a shared environment build, ask your workspace admin to check access to the group and selected projects too.
- Fix the specific setup issue and retry the action. Check that the merge request exists.
Do not disconnect every GitLab tool as a general reset. If the same action still fails after you’ve confirmed the correct GitLab account and repository access, contact Replit Support. Include the exact error message, repository URL, affected chat and workspace links, and what you’ve already tried. Remove any passwords, tokens, or other secrets from screenshots and logs before sharing them.
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.