Repository navigation
docs(nix): record muse-proxy direct mode in its Home Manager unit (#2753) - #2774
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 18 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Phase A of the 2026-10-30 "make it system NixOS config + survey everything" pass.
Finding: the muse-proxy stack was already declarative.
systemd.user.services.muse-proxyinhome/common/default.nix(#2104) generates exactly the live unit — evaluating this flake at origin/main yields ExecStart/nix/store/7bxcdg21iqjmiinxh0bl92kyjwrbmkdn-muse-proxy-start-unit, byte-identical to the running unit, and the fullnixosConfigurations.amdconfig evaluates clean. Direct mode (#2753) needed no unit change: same port (18747), same checkout start script (which unsets META_API_KEY and leaves egress unpinned), credential read at runtime from ~/.config/muse/auth.json and never part of the config.This PR only extends the unit comment so the NixOS source of truth records direct mode and the muse-direct provider relationship. Comment-only: re-evaluating after the edit produces the identical ExecStart, so the generated unit is unchanged and no activation/restart is implied. The hand unit Drew asked about is not hand-made — it is this HM unit; nothing is superseded at activation.
Need help on this PR? Tag
@codesmith-botwith what you need.