Skip to content

Adding alternate authentication for roo code cloud #7723

@mojomast

Description

@mojomast

What specific problem does this solve?

When trying to authenticate to roo code cloud using Firebase Studio there is no way to pass the auth to roocode within firebase because theres no firebase studio button. If there was an option to paste the token provided in the url from the auth page it would be possible to not rely on the links and to get around other issues related to this type of authentication flow.

Additional context (optional)

No response

Roo Code Task Links (Optional)

No response

Request checklist

  • I've searched existing Issues and Discussions for duplicates
  • This describes a specific problem with clear impact and context

Interested in implementing this?

  • Yes, I'd like to help implement this feature

Implementation requirements

  • I understand this needs approval before implementation begins

How should this be solved? (REQUIRED if contributing, optional otherwise)

an option to paste the token from the login page.

How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)

Given I want to authenticate to roo code cloud from within firebase studio
When I try to authenticate
Then I have to use the roo cloud authentication page
And there are buttons to return to VS code and other IDEs
But theres no path to authenticate to firebase studio.

Technical considerations (REQUIRED if contributing, optional otherwise)

I will modify the roo cloud provider configuration to allow pasting of the key that is sent to the IDE when clicking the link from the login page.

Trade-offs and risks (REQUIRED if contributing, optional otherwise)

i dont have access at all to cloud it's closed so this is the best i can do
I don't see how this would cause issues to UX outside of people using roocode on platforms that are not officially tested. In order for me to be able to test firebase studio to see if theres issues using roo code with it I want to use the roo cloud provider/

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Issue [Unassigned]

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions