Skip to content

fix: align provider routing across app and API - #590

Open
AndrewDongminYoo wants to merge 5 commits into
nashsu:mainfrom
AndrewDongminYoo:fix/provider-routing-and-export-safety
Open

fix: align provider routing across app and API#590
AndrewDongminYoo wants to merge 5 commits into
nashsu:mainfrom
AndrewDongminYoo:fix/provider-routing-and-export-safety

Conversation

@AndrewDongminYoo

@AndrewDongminYoo AndrewDongminYoo commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Keep task routing, project overrides, and API chat on the same current provider configuration without persisting API keys in task routing.
  • Stop saved task routes from bypassing the global provider-disabled state, including clip ingestion and API chat.
  • Migrate legacy chat routes that predate persisted credential-free profiles so native API and MCP callers use the intended provider after startup.

Scope

Archive export containment has been removed from this PR and is being submitted separately.

Validation

  • npm run test:mocks (119 files, 1752 tests passed)
  • npm run typecheck
  • npm run build
  • cargo test --manifest-path src-tauri/Cargo.toml --lib --quiet (353 passed, 1 ignored)

@AndrewDongminYoo
AndrewDongminYoo marked this pull request as ready for review July 16, 2026 13:01
@AndrewDongminYoo AndrewDongminYoo changed the title fix: align provider routing and archive export safety fix: align provider routing across app and API Jul 31, 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.

1 participant