Both agents now get the MCP server without a separate launcher: home-manager owns one config file per agent next to each agent's own mutable state file (~/.codex/config.toml and ~/.claude.json stay untouched), and zsh aliases make the layered profile / --mcp-config call the default. Drop pkgs.chromium and --executable-path: the browsers bundled with playwright-mcp work on their own, so this removes a redundant chromium closure. --browser chrome would have looked for a branded Chrome under /opt/google. Add --output-dir so page snapshots stop landing in whatever repository the agent runs in, and give each agent its own profile so both can drive a browser in parallel. Verified on tnix: codex --profile playwright mcp list shows the server, and claude reports browser_navigate as available (NO in a control directory). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01543pvEuBqu1G4rimyXq3YA |
||
|---|---|---|
| .. | ||
| aerc.nix | ||
| alacritty.nix | ||
| bat.nix | ||
| default.nix | ||
| git.nix | ||
| keepassxc.nix | ||
| kitty.nix | ||
| msmtp.nix | ||
| nixvim.nix | ||
| packages-stable.nix | ||
| packages.nix | ||
| playwright-mcp.nix | ||
| qutebrowser.nix | ||
| sway.nix | ||
| tmux.nix | ||
| udiskie.nix | ||
| yazi.nix | ||
| zathura.nix | ||
| zsh.nix | ||