openclaw sync: partner-controllable primary-model + custom config dir (env)#93
Closed
rjckkkkk wants to merge 1 commit into
Closed
openclaw sync: partner-controllable primary-model + custom config dir (env)#93rjckkkkk wants to merge 1 commit into
rjckkkkk wants to merge 1 commit into
Conversation
… (env) Two product-level controls so a partner integrating AIMA owns OpenClaw behavior without code changes on their side (both honor CLI sync AND the serve auto-sync loop): - AIMA_OPENCLAW_SET_DEFAULT=false — register the AIMA provider + models but do NOT set OpenClaw's primary/default chat model (leave the user's current primary alone). Unset = previous behavior (AIMA sets it). Threaded as Deps.SetDefaultModel *bool → SyncResult.SkipDefaultModel → mergeChatModelDefault early-returns (preserving prior ownership record so toggling back on works). - AIMA_OPENCLAW_CONFIG=<path>/openclaw.json — write to a custom config dir (e.g. a partner using .byClaw instead of .openclaw). Skills, extensions and managed-state all follow filepath.Dir(ConfigPath), so the whole set relocates. This is purely AIMA-side and independent of the OpenClaw/byClaw product's own layout. Verified on the Strix Halo rig: SET_DEFAULT=false → provider written, primary empty; default → primary set; custom config dir → config+skills land under .byClaw. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Collaborator
Author
|
Superseded by the consolidated baiying-integration-2026-06 PR (whole 2026-06 stack). |
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.
What
Two product-level env controls so a partner integrating AIMA owns OpenClaw behavior without code changes on their side. Both honor CLI
aima openclaw syncAND the serve auto-sync loop; defaults preserve previous behavior.AIMA_OPENCLAW_SET_DEFAULT=false— register the AIMA provider + models but do NOT set OpenClaw's primary/default chat model (leave the user's current primary untouched). Unset = previous behavior. ThreadedDeps.SetDefaultModel *bool→SyncResult.SkipDefaultModel→mergeChatModelDefaultearly-returns, preserving prior ownership record.AIMA_OPENCLAW_CONFIG=<path>/openclaw.json— write the config to a custom dir (e.g. a partner using.byClaw). Skills, extensions and managed-state all followfilepath.Dir(ConfigPath), so the whole set relocates. Purely AIMA-side, independent of the OpenClaw/byClaw product's own layout.Test
TestMergeSkipDefaultModel(provider still registered, primary left untouched);go vetclean.SET_DEFAULT=false→ provider written, primary empty; default → primary set;AIMA_OPENCLAW_CONFIG=...\.byClaw\openclaw.json→ config + skills land under.byClaw.🤖 Generated with Claude Code