Skip to content

fix(cli+dashboard): restore API-key auth flow#52

Open
Jungley8 wants to merge 6 commits intoRightNow-AI:mainfrom
Jungley8:fix/cli-stop-auth-401
Open

fix(cli+dashboard): restore API-key auth flow#52
Jungley8 wants to merge 6 commits intoRightNow-AI:mainfrom
Jungley8:fix/cli-stop-auth-401

Conversation

@Jungley8
Copy link

@Jungley8 Jungley8 commented Feb 27, 2026

Summary

close #51

Included fixes

  • CLI test scope fix for parse_api_key_from_config_toml.
  • Dashboard auth fix for API-key-protected mode:
    • Network/Budget panel requests now use OpenFangAPI (injects Bearer header).
    • Auth token bootstrap from URL query (?token= / ?api_key=) into session storage.
  • Remove generated desktop schema artifact from VCS and ignore generated desktop dir.

Problem addressed

With api_key enabled, dashboard had partial 401 behavior because some panel calls used raw fetch('/api/...') without auth header. This patch normalizes those calls through the shared API client.

Validation

  • Targeted Rust tests for config TOML API-key parser pass.
  • Static dashboard code scan confirms API calls are routed through OpenFangAPI wrapper.

Notes

A previous PR from the same branch was closed; this is a fresh reopen request with current branch state.

@Jungley8 Jungley8 force-pushed the fix/cli-stop-auth-401 branch from 270e646 to fc16156 Compare February 27, 2026 17:54
@Jungley8 Jungley8 changed the title fix(cli+dashboard): restore API-key auth flow and remove generated artifact fix(cli+dashboard): restore API-key auth flow Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

API key auth regression: stop action 401 + dashboard endpoints 401

1 participant