+5

2configs/omnigent.nix

View file Reviewed

··· 28 28 acp_agent: 29 29 name: Oh My Pi 30 30 command: omp acp 31 31 + # See tools/covibe/flake-module.nix: omp fails session/new outright 32 32 + # when omnigent's MCP relay cannot start, and the relay's 33 33 + # `python -I -m omnigent…` child cannot import omnigent under a 34 34 + # nixpkgs-wrapped interpreter. 35 35 + omnigent_mcp: false 31 36 32 37 os_env: 33 38 type: caller_process

+11

tools/covibe/flake-module.nix

View file Reviewed

··· 23 23 # 404. sandbox none because omp needs its own ~/.omp credential store and 24 24 # unrestricted egress to the model APIs; confinement, if we want it, has 25 25 # to happen a layer down (a separate uid, or nspawn), not here. 26 26 + # 27 27 + # omnigent_mcp: false is load-bearing. With it on, omnigent hands omp an 28 28 + # `mcpServers` entry in `session/new` whose command is 29 29 + # `sys.executable -I -m omnigent.claude_native_bridge serve-mcp`; `-I` 30 30 + # (isolated) makes that child ignore PYTHONPATH, so under a nixpkgs 31 31 + # console-script wrapping it cannot import omnigent. omp starts every 32 32 + # declared MCP server eagerly and fails the whole session when one dies — 33 33 + # `ACP session/new failed: Internal error`. The relay only bridges 34 34 + # *omnigent's* builtin tools into the agent, and omp brings its own, so 35 35 + # turning it off costs nothing here. 26 36 spec = pkgs.writeText "omp-agent.yaml" '' 27 37 name: omp 28 38 prompt: You are omp (Oh My Pi), a concise coding assistant. ··· 32 42 acp_agent: 33 43 name: Oh My Pi 34 44 command: ${omp}/bin/omp acp 45 45 + omnigent_mcp: false 35 46 36 47 os_env: 37 48 type: caller_process