Repository navigation
feat(sync): sync assistant settings such as custom providers and API keys - #3
Merged
Merged
Conversation
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.
Adds a new item kind,
setting: one item per assistant holding the settings people edit by hand, custom providers, base URLs and API keys included. Values are synced as they are; the pouch is end-to-end encrypted.Supported: OpenCode (1 and 2, providers translated between them), Claude Code, Codex, Gemini CLI (
settings.jsonand.env), Qwen Code, Copilot, Crush and Factory. Each assistant has an allowlist insp-harness; MCP servers, hooks, plugins, credentials and machine-specific paths stay out.<file>:<path>), last writer wins, backups before writes.skillpouch settings list | exclude | include.skillpouch select --off settings/--off <assistant>.Companion web PR: skillpouch/skillpouch (feat/harness-settings-sync).
Testing
cargo fmt --check,clippy -D warnings,cargo test --workspacescripts/e2e-settings.sh: three Docker computers with every assistant installed, the real API and web app, and a mock provider that checks each CLI accepts the synced provider and key. All scenarios pass for all eight assistants (arrive, cli, edit, delete, include, folder, reinstall, late install, select, OpenCode 1↔2, daemon, web).