Hmbown / Hmbown/Codewhale

Meta-subscription device-code login (codewhale auth muse-device)

Open
#5,845 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
41k
Forks
3.6k
Avg merge
13h 59m
Merged PRs (30d)
299

Description

No login path covers a Meta/Muse subscription today: chatgpt_oauth.rs and xai_oauth.rs serve only their own issuers, oauth.rs loads OpenAI/Codex only. Interop research (local machine): the Muse CLI performs RFC 8628 device flow against https://auth.meta.com (/oidc/device/authorization/, /oidc/device/token/), client_id 1031625952748946 (env-overridable via MUSE_AUTH_URL/MUSE_CLIENT_ID), access_token used as Bearer against https://api.meta.ai/v1; the subscription token itself lives in the OS keychain, so file-consent reuse is a dead end. Implement codewhale auth muse-device mirroring xai_oauth.rs device_code_login + owned-generation activation, then wire the Meta provider to the stored Bearer.

Contributor guide

Open the contributing guide

Research direction

Start by reading xai_oauth.rs for the existing device_code_login and owned-generation activation flow, then inspect oauth.rs and chatgpt_oauth.rs to understand provider wiring. Use the documented Meta device authorization and token endpoints, with the stated environment overrides, and verify that codewhale auth muse-device stores and uses the subscription Bearer for api.meta.ai/v1.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api, authentication, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.