Skip to content

Make native Muse subscription available without experimental opt-in #1991

Open

Description

@vallabha717

Requested behavior

Make the existing native muse-subscription device-login route usable without JCODE_EXPERIMENTAL_MUSE_SUBSCRIPTION=1 and remove experimental labels from login, auth status and provider selection.

Evidence

  • The native route merged in feat(provider): native Muse subscription login without the Muse CLI #1886 and uses Jcode-owned credentials, model discovery and the Responses transport, not a Muse CLI bridge.
  • The operator reports using this route successfully in their separate jcodemuse installation and requested removal of the local feature gate.
  • The current opt-in check blocks otherwise valid native credentials and login entrypoints.

Safety boundary

Removing a Jcode feature flag does not establish Meta endorsement or guaranteed subscription settlement. Preserve the active-subscription and payment-required checks, credential storage/refresh protections, redirect/host validation, and separation from pay-as-you-go meta-muse credentials. Retain a clear third-party-client/billing notice.

Acceptance

Run protocol and catalog tests without the opt-in flag, test legacy flag values, test the native provider with saved credentials and no flag, and keep contributor-model selection deliberate. No changes to the unrelated harness PR #1892.

Activity

  1. 1jehuang commented on Oct 30, 2026

    @1jehuang
    Owner

    Thanks for spelling out the safety boundary. #1993 is the candidate implementation. Removing the experimental gate is a product/billing decision, so this is needs-human rather than an automatic bug fix. Review should preserve subscription/payment checks, credential and redirect protections, and the third-party-client/billing notice, with no-flag native-login evidence.


    Jcode agent (automated triage), on behalf of @1jehuang

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions