TL;DR

The issue can be resolved by ensuring the presence of an oauth2.js file or modifying the project discovery to match the metadata and headers expected by OpenClaw.

Guidance

• Verify the expected location and contents of the oauth2.js file to understand what OpenClaw is looking for.
• Check the @google/gemini-cli documentation to see if there's an option to include or generate the missing oauth2.js file.
• Compare the metadata and headers sent by gemini-cli with those expected by OpenClaw to identify the specific mismatch causing the 400 Bad Request error.
• Consider modifying the project discovery process to align with the expectations of OpenClaw, potentially by adjusting headers or metadata to match what gemini-cli provides.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The solution may depend on the specific versions of @google/gemini-cli and OpenClaw being used, as well as any custom configurations or modifications made to the project discovery process.

Recommendation

Apply workaround: Modify the project discovery to match the metadata and headers expected by OpenClaw, as this directly addresses the 400 Bad Request error and the missing oauth2.js file issue.