Summary
Please consider supporting credential reuse for GitHub Copilot between OpenClaw and OpenSpace.
The main issue is not just "support GitHub Copilot" in general, but specifically:
- OpenClaw can already work with GitHub Copilot credentials / login state
- OpenSpace currently does not seem to reuse that existing authentication
- users end up needing separate provider credentials or extra configuration
Problem
For users already authenticated in OpenClaw with GitHub Copilot, moving to OpenSpace is not seamless.
The current experience appears to be:
- OpenClaw has a working GitHub Copilot auth path
- OpenSpace has its own provider configuration path
- the GitHub Copilot credentials/session from OpenClaw are not reused automatically or consistently
This creates duplicate setup work and makes the OpenClaw -> OpenSpace workflow less smooth than it should be.
Expected behavior
Ideally, if a user already has valid GitHub Copilot credentials available through OpenClaw, OpenSpace should be able to reuse them directly or through a compatible resolver path.
Examples:
- detect an existing OpenClaw GitHub Copilot auth/session state
- reuse the same credentials in OpenSpace without requiring a second login
- provide a documented config flag or env-based path for this reuse
- fail clearly when credentials exist but are incompatible or expired
Why this matters
This would make the OpenClaw -> OpenSpace transition much better for existing users.
Benefits:
- avoids duplicate authentication/configuration
- reduces friction for GitHub Copilot users
- improves consistency across related tools in the ecosystem
Suggested implementation direction
Possible approaches:
- add an OpenClaw-aware credential resolver in OpenSpace
- support importing or reading the same GitHub Copilot credential source used by OpenClaw
- define a shared auth abstraction for GitHub Copilot across both projects
- document refresh / expiry behavior and any platform-specific limitations
Example scenario
A user is already logged into GitHub Copilot through OpenClaw and can use it there successfully.
When launching OpenSpace, the user expects that same GitHub Copilot credential context to be reusable instead of having to configure a different LLM provider or re-authenticate separately.
If helpful, I can provide a concrete reproduction flow for the current OpenClaw -> OpenSpace mismatch.
Summary
Please consider supporting credential reuse for GitHub Copilot between OpenClaw and OpenSpace.
The main issue is not just "support GitHub Copilot" in general, but specifically:
Problem
For users already authenticated in OpenClaw with GitHub Copilot, moving to OpenSpace is not seamless.
The current experience appears to be:
This creates duplicate setup work and makes the OpenClaw -> OpenSpace workflow less smooth than it should be.
Expected behavior
Ideally, if a user already has valid GitHub Copilot credentials available through OpenClaw, OpenSpace should be able to reuse them directly or through a compatible resolver path.
Examples:
Why this matters
This would make the OpenClaw -> OpenSpace transition much better for existing users.
Benefits:
Suggested implementation direction
Possible approaches:
Example scenario
A user is already logged into GitHub Copilot through OpenClaw and can use it there successfully.
When launching OpenSpace, the user expects that same GitHub Copilot credential context to be reusable instead of having to configure a different LLM provider or re-authenticate separately.
If helpful, I can provide a concrete reproduction flow for the current OpenClaw -> OpenSpace mismatch.