protable config via .nixmac/settings.json#230
Closed
cooper (czxtm) wants to merge 2 commits into
Closed
Conversation
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…settings.json) EvolutionLimits (max iterations, max build attempts) now persists in <config_dir>/.nixmac/settings.json instead of the OS app data directory. Because the config dir is the user's nix-darwin repo and already syncs via git, these settings ride along across machines without an explicit backup/restore step. Per-device settings (developerMode, pinnedVersion, updateChannel, model cache, prompt history) stay in the OS app data dir where they belong. How it works: - New storage::configurable_scope module exposes repo_store_path(app), which returns the absolute path to .nixmac/settings.json and lazily creates the directory plus a short README.md the first time it's called. - configurable-derive learns #[config(store_path_fn = <path>)]: instead of a hard-coded string, the generated load() method calls a resolver function each time. Keeps the derive decoupled from nixmac — any consumer can plug in their own path resolver. - EvolutionLimits opts into the new mode via store_path_fn. - store::get_max_iterations / set_max_iterations and the max_build_attempts pair now read/write the repo store, with a best-effort migration from the legacy local store on first read so existing users don't see their values reset to defaults. Falls back to defaults if config_dir isn't set yet (during onboarding). - Tuning UI section copy clarifies that values sync via the repo. The Backup & Restore section copy clarifies that repo-scoped values are versioned by git, not included in the local export. Also includes the user's separate rename of "vLLM / LiteLLM" → "OpenAI Compatible" in ai-models-tab.tsx and api-keys-tab.tsx. Closes: nixmac-gr3 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2 tasks
Member
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced May 28, 2026
Closed
Closed
Contributor
📋 PR Overview
🔬 Coverage
|
Member
Author
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
Test Plan
Docs