Conversation
…profile switching - Implement RFC 8628 device flow for Moonshot AI Kimi Code (client id 17e5f671-d194-4dfb-9706-5516cb48c098) - Add KimiOAuthManager and KimiOAuthService to manage accounts and sync to native ~/.kimi-code - Extend AuthService and cc-switch auth commands with --provider kimi_oauth - Add cc-switch config kimi profile management to snapshot and switch native Kimi Code profiles atomically Signed-off-by: Ferris <ferris@mail.build>
Owner
|
Please give me some time to review, thank you for your contribution |
…or authorization_pending Signed-off-by: Ferris <ferris@mail.build>
…tatus Signed-off-by: Ferris <ferris@mail.build>
…status Signed-off-by: Ferris <ferris@mail.build>
…uota inspection - Resolve and display account nicknames in Kimi profile lists and status views - Add '-q/--quota' to 'config kimi profile list' for parallel 5-hour quota and reset countdown inspection across all profiles - Support 'config kimi status <profile>' and 'config kimi status --all' for inspecting profile statuses without switching - Automatically refresh expired access tokens when querying saved profile quotas Signed-off-by: Ferris <ferris@mail.build>
bytemain
force-pushed
the
feat/kimi-oauth-config-switch
branch
from
September 17, 2026 15:57
aecabb4 to
ca3a5f3
Compare
- Prevent test runners from overwriting user's active native credentials - Guard default account sync during test runs - Provide safe isolated fallback path for get_kimi_config_dir during testing Signed-off-by: Ferris <ferris@mail.build>
…tokens in quota list Signed-off-by: Ferris <ferris@mail.build>
Signed-off-by: Ferris <ferris@mail.build>
- Add AppType::Kimi alongside Claude, Codex, Gemini, OpenCode, Hermes, OpenClaw, Pi - Implement TOML provider, model, and MCP editing for ~/.kimi-code/config.toml - Support additive provider management and model aliases for Kimi Code - Wire AppType::Kimi across TUI, CLI commands, settings, and services - Add comprehensive unit and integration tests for Kimi provider configuration Signed-off-by: Ferris <ferris@mail.build>
set_current_provider and set_default_model acquired kimi_write_lock and then invoked write_prepared_config, which re-acquired the same non-reentrant mutex. Replace with direct write_file_atomic while holding the lock, eliminating the self-deadlock. Signed-off-by: Ferris <ferris@mail.build>
Signed-off-by: Ferris <ferris@mail.build>
- Remove redundant RFC 8628 OAuth device flow implementation and service layer - Strip custom 'config kimi profile' directory snapshot mechanism and quota crawler - Simplify kimi_config.rs to thin adapter managing config.toml and mcp.json - Align with Pi/Hermes additive application model and preserve clean concurrency locks Signed-off-by: Ferris <ferris@mail.build>
bytemain
changed the title
Contributor
Author
|
Hi @SaladDay, just following up on this PR! We recently refactored and streamlined the implementation into a clean, minimal thin adapter (commit
The branch is fully up to date with |
Owner
|
I'd like to know if implementing it through your solution can maintain consistency with the upstream cc-switch database, because we have synchronization requirements. |
Signed-off-by: Ferris <ferris@mail.build>
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
2 participants
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.
Add Kimi Code to the existing additive provider workflow. The adapter manages native
config.tomlproviders/models andmcp.json; the Kimi CLI continues to own OAuth. Provider switching uses the common provider flow instead of a separate profile snapshot mechanism, and native writes avoid recursive locking.Imported providers retain native provider attributes and model metadata, including the distinction between a local alias and the actual upstream model ID. Cross-provider alias collisions and invalid model selections are rejected before writes. CLI/TUI edits preserve unrelated metadata while removing superseded connection credentials from saved provider data. Native config/MCP writes use private permissions, and malformed MCP files are not overwritten.
Database compatibility has an explicit boundary: no tables, columns, or schema version changes are added. Provider JSON and shared MCP/skill definitions use existing database synchronization. Kimi enable flags are reconstructed from local native files/directories and do not automatically transfer to another machine. Original upstream
farion1231/cc-switchat36d950411e622129f285635f43c17e5f35462413is schema 19 while this CLI is schema 18; returning an upgraded database is rejected by the CLI. This pre-existing fork-wide gap remains and requires coordinated schema alignment. Seedocs/kimi-sync-compatibility.md; this PR does not claim end-to-end latest-original/WebDAV compatibility.Validation on the follow-up: 16 Kimi-filtered unit tests covering native and SQL round trips, reload/disable persistence, alias isolation (including quoted native aliases), malformed native model rejection, private permissions, malformed MCP preservation, and native-only/no-op/explicit-clear form edits; 2 existing future-schema rejection tests. Tests used isolated directories. Independent review completed. Modified Rust files and whitespace checks pass. Full
cargo fmt --checkstill reports 14 unchanged files from the previous PR head; this follow-up does not reformat them.Signed-off-by: Ferris ferris@mail.build