Summary

• Update resolver conversation instruction prompts to explicitly require using the configured git provider end-to-end
• Instruct the agent to use provider-specific token env vars: $github_token, $gitlab_token, $bitbucket_token, $forgejo_token, $azure_devops_token
• Warn explicitly not to default to GitHub when another provider is selected
• Clarify that for Forgejo instances, the agent should use the configured host/base domain and Forgejo APIs (not GitHub endpoints)

Files changed

• openhands/resolver/prompts/resolve/basic-conversation-instructions.jinja
• openhands/resolver/prompts/resolve/basic-with-tests-conversation-instructions.jinja
• openhands/resolver/prompts/resolve/basic-followup-conversation-instructions.jinja

Rationale

• Addresses reports where PR creation “thinks” there is no Forgejo token unless the user explicitly tells it
• Makes the intent unambiguous for provider choice and token env vars during agent reasoning/execution

Testing

• Validate that PR creation on Forgejo repos no longer defaults to GitHub
• Confirm that environment variable exposure includes $forgejo_token when configured and that agent instructions align with it

Co-authored-by: openhands openhands@all-hands.dev