[codex] Support local hardware profile overlays - #3
Merged
GuideboardLabs merged 1 commit intoMay 15, 2026
Merged
Conversation
GuideboardLabs
marked this pull request as ready for review
May 15, 2026 12:33
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
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
Adds a local hardware profile overlay layer. Oathweaver can now load host-specific profile definitions from
SourceCode/configs/hardware_profiles.local.jsonand merge them over the shared hardware profile config at startup.This preserves the project’s shared runtime defaults while giving operators a documented path for local capacity tuning that does not require editing tracked config files.
Why
The active hardware profile layer introduced in PR #2 makes runtime capacity explicit through shared config. That is useful for portable defaults, but individual deployments still need a place for machine-specific profile values, local defaults, and temporary tuning.
This PR adds that local-only layer so future users can describe deployment-specific capacity without carrying dirty changes in
SourceCode/configs/hardware_profiles.jsonor proposing machine-specific profiles upstream.Changes
SourceCode/configs/hardware_profiles.local.json.default_profilefor a deployment.SourceCode/configs/*.local.jsonso local profile overlays stay out of source control.--no-restart-ollamareuses the configured Ollama endpoint instead of starting anotherollama serveprocess.Example Profile Shape
{ "default_profile": "local_8gb_vram_48gb_ram_cuda", "profiles": { "local_8gb_vram_48gb_ram_cuda": { "name": "local_8gb_vram_48gb_ram_cuda", "display_name": "Local: 48GB RAM / 8GB CUDA", "hardware": { "system_ram_gb": 48, "gpu_backend": "cuda", "gpu_vram_gb": 8, "unified_memory": false }, "scheduler": { "max_context_tokens": 12288, "warning_context_tokens": 8192, "max_stage_context_tokens": 2400, "max_parallel_models": 1, "max_active_model_calls": 1, "on_deck_depth": 1, "warm_depth": 0, "allow_neural_prefetch": false } } } }Validation
PYTHONPATH=SourceCode python3 -m unittest tests.test_hardware_profiles tests.test_inference_router_compat tests.test_model_routing_tier_resolution tests.test_ollama_wait_for_availablePYTHONPATH=SourceCode .venv/bin/python -m unittest tests.test_hardware_profilespython3 -m json.tool SourceCode/configs/hardware_profiles.json >/dev/nullpython3 -m json.tool SourceCode/configs/hardware_profiles.local.json >/dev/nullbash -n start_oathweaver_web.shgit diff --check