feat: persist integration API keys in a private local store - #6398
Merged
Conversation
atomantic
force-pushed
the
cos/task-mtq1nmeb/agent-38f67f37
branch
from
September 6, 2026 17:13
7812051 to
18b07eb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Artificial Analysis sync now saves an authenticated key and reuses it on later syncs. Settings > Credentials can save, rotate, and clear Artificial Analysis, Hugging Face, CivitAI, fal.ai, and reactor.inc keys without exposing their values.
Keys persist in the permission-protected, machine-local
data/private/api-keys.jsonstore. Existing integration settings readers and editors remain compatible, with environment/CLI fallbacks retained. Migration 357 moves existing settings keys without replacing newer private-store values; the store is excluded from HTTP asset serving and Data Manager cleanup. Storage and backup behavior are documented.Test plan
Complete server suite passed: 2,005 suites, 39,974 tests (25 skipped).
Focused persistence, restart reuse, rejected-key, corruption, migration retry, route validation/redaction, static-file privacy, and catalog checks passed.
Credentials and model comparison UI tests passed (17 tests).
Client lint and production build passed.
Post-rebase Antigravity local review: APPROVED, NO FINDINGS.