{"owner":"manaflow-ai","repo":"cmux","hasSkills":true,"totalSkillsCount":5,"totalTokensCount":5262,"categories":["claude-rule","root-instruction","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"cmux":{"command":"npx","args":["-y","@modelcontextprotocol/server-cmux"]}}},"found":["CLAUDE.md","AGENTS.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"CLAUDE.md":"# cmux agent notes\n\nKeep repo-wide decisions here; procedures belong in [CONTRIBUTING.md](CONTRIBUTING.md),\n[area instructions](#area-instructions) and [task skills](skills/README.md).\nRead the matching skill before changing an area, then only the references needed.\n\n**Manaflow AI team members and their agents:** read the private [cmuxterm-hq CLAUDE.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/CLAUDE.md) and [AGENTS.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/AGENTS.md) before fleet or CI work. They are the entry point for fleet builds, CI routing, agent coordination, and landing rules. Start fleet work at [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md). External contributors can ignore this block; those links return 404 for them.\n\n## Verification and isolation\n\n- Before committing, setup or a native build, [choose scoped verification](skills/cmux-testing/references/local-vs-ci-validation.md).\n  Start with `python3 scripts/verify-local.py`; docs and portable tooling need no app build.\n  Run repository commands only in a [trusted checkout](docs/contributor-verification.md#trust-boundary),\n  including `verify-local.py --help`, `--list` and `--repo`. Push does not run checks for you.\n- Use [CONTRIBUTING.md](CONTRIBUTING.md#getting-started) for setup. Outside cmuxterm-hq-created\n  checkouts, set `CMUX_DEV_BACKEND_MODE=local` for dev builds. Follow [tagged builds](skills/cmux-dev-workflow/references/tagged-builds.md)\n  for commands and cache reuse; team fleet tasks start at\n  [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md).\n  Never use bare `xcodebuild` or an untagged `cmux DEV.app`. Clean up only your own tags.\n- A same-repo app PR gets a fleet dogfood build and link comment only while it has the\n  `dev-build` label. Add it when someone will dogfood the PR, not by default; under load\n  the fleet builds the newest push, and the comment says how to build a skipped commit.\n- Never quit, kill, relaunch, replace or launch-profile the user's running cmux\n  (`/Applications/cmux.app`, `com.cmuxterm.app`), including through a Release build or\n  another bundle with that ID. Never set `CMUX_ALLOW_REPLACING_RUNNING_CMUX`; only the\n  user may. Reproduce in a tagged build and attach profiling to its PID.\n- Dogfood through `CMUX_TAG=<tag> scripts/cmux-debug-cli.sh`, never `/tmp/cmux-cli`.\n  Never report raw `.app` paths or `file://` URLs.\n- App-linked code (`Sources/`, `CLI/`, `TunnelExtension/` and their packages) must\n  remain [Swift 6.0 compatible](skills/cmux-architecture/references/swift-6-0-compatibility.md).\n\n## Area instructions\n\nRead these before working in their scope; nested files may not load automatically:\n\n- `ios/` or `Packages/iOS/`: [ios/AGENTS.md](ios/AGENTS.md).\n- `web/` or any cmux Cloud database work: [web/AGENTS.md](web/AGENTS.md).\n- `cmux-tui/`: [cmux-tui/AGENTS.md](cmux-tui/AGENTS.md).\n\n## Contributions and publication\n\nBefore fixing a bug or adding a feature, search open upstream PRs by symptom or\nissue number. Prefer landing an outside contributor's existing PR; push fixups\nonly when maintainer edits are allowed, and explain the changes. If using their\napproach in your own PR, credit them in every such commit with `Co-authored-by`\nusing their commit email, link your PR from theirs and thank them. Let a human\nclose it; never close an outside PR without a human-written explanation.\n\nThe server directories listed in [LICENSE](LICENSE) (`web/`, `workers/ci-artifacts/`,\n`workers/iroh-v2/`, `workers/presence/`, `services/iroh-relay-minter/`,\n`cmux-tui/relays/cloudflare-do/`) use the Business Source License, which needs\nevery outside author's CLA grant. Do not merge a PR that changes those\ndirectories while CLA Assistant is red, and do not copy an outside\ncontributor's work there under a `Co-authored-by` trailer unless that person\nhas signed the CLA. Keep code that ships in the macOS or iOS app out of those\ndirectories.\n\nRead [STYLE.md](STYLE.md) before drafting or revising issues, PR descriptions,\nRFCs or progress updates. Fill the PR's `## Changelog` section with one\n`Added`/`Changed`/`Fixed`/`Removed` line for user-visible changes, otherwise `none`.\nDo not edit `CHANGELOG.md` in feature PRs; release tooling owns it.\n\n## CI, review and merge\n\n- Commit the failing behavioral regression before its fix; record the same\n  focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)).\n  A bug-fix PR body names that command, its failure on the base and its pass on the head,\n  then an `### Observed / Not run` section: what you ran and saw, then what you only read\n  or didn't run. `gh-merge-green` warns when a fix PR lacks it; it does not block.\n- Check executed tests on the current SHA; green skipped jobs do not establish coverage.\n  Add `full-ci` only for a user-requested or agreed broad validation plan,\n  naming the extra lanes and why ([CI coverage](skills/cmux-testing/references/pr-ci-coverage.md)).\n- Keep branches current locally with `scripts/merge-main.sh`; follow\n  [the merge-main guide](docs/ci/merge-main.md) and never force-push over its merge.\n- `gh pr merge` saying \"base branch policy prohibits the merge\" means the token lacks the `workflow`\n  scope or GitHub timed out, not a rule: run `gh auth refresh -h github.com -s workflow`, or merge with\n  `gh api -X PUT repos/OWNER/REPO/pulls/N/merge -f merge_method=squash -f sha=SHA`, which names the cause. Never `--admin`.\n- A first implementation pass ends with passed scoped verification and an open PR;\n  do not watch CI or run speculative reviews by default.\n- Before opening a PR and before merging, check it against [REVIEW.md](REVIEW.md) (draft),\n  the mistakes our review history keeps catching.\n- Before merging, use a [review subagent](skills/cmux-review/SKILL.md), correctness\n  first; a second model is not a review gate. Disclose skipped verification on the PR.\n  `main` is nightly: fix forward, do not revert.\n- A PR merges when an independent review subagent passes it and it causes no red of its own;\n  base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky\n  user-visible behavior behind a setting or Debug toggle and fix a bad default in the next\n  nightly. Merge with `gh-merge-green`; [merge freezes](docs/ci/merge-freeze.md) still hold.\n  `gh-merge-green` still waits for the checks it requires; never get around it with\n  `--override` or the API merge path.\n  Follow [dogfood and merge receipts](skills/cmux-review/SKILL.md#dogfood-and-merge).\n  Notify with `cmux notify` when a socket is available.\n- A red base (`main` doesn't compile, or CI is red on every PR) is priority zero. Fix it\n  directly in its own PR; don't note it and leave it for an owner.\n\n## Implementation rules by task\n\nUse these existing owners instead of duplicating their checklists here:\n\n| Touching | Read before editing |\n| --- | --- |\n| Typing paths, SwiftUI list/store boundaries, rendering, find layering, UTTypes or OS-specific bugs | [cmux-debugging](skills/cmux-debugging/SKILL.md) |\n| Packages, workspace groups, lockfiles or feature flags | [cmux-architecture](skills/cmux-architecture/SKILL.md) |\n| Submodules or GhosttyKit | [cmux-ghostty](skills/cmux-ghostty/SKILL.md) |\n| User-facing strings, docs or help | [cmux-localization](skills/cmux-localization/SKILL.md); report the localization audit |\n| New cmux shortcuts | [cmux-keyboard-shortcuts](skills/cmux-keyboard-shortcuts/SKILL.md) |\n| Tests or target wiring | [cmux-testing](skills/cmux-testing/SKILL.md); run `scripts/sync-test-wiring` after adding, renaming or deleting a `cmuxTests/` file |\n| Multiple entrypoints or a bug that tests previously missed | [cmux-shared-behavior](skills/cmux-shared-behavior/SKILL.md); share action/mutation paths, verify every entrypoint, and cover the missed repro |\n\n## Remote CLI relay\n\nFor v2 socket methods and remote CLI changes, read [relay authorization](skills/cmux-socket-policy/references/remote-relay-authorization.md).\n`RemoteRelayCommandPolicy` defaults to deny. Allowlist only for a needed remote\nflow, scoped to the session's objects; command-bearing params stay denied on\nevery method. The PR must analyze local command/content\nexecution, access to unowned objects and local-state exposure, and include the\nrequired policy tests and ID scoping. Unsafe local effects must be redesigned.\nNever allowlist terminal spawn/respawn without live verification that it executes\non the remote host. An allowlist addition without this analysis blocks review.\n","AGENTS.md":"# cmux agent notes\n\nKeep repo-wide decisions here; procedures belong in [CONTRIBUTING.md](CONTRIBUTING.md),\n[area instructions](#area-instructions) and [task skills](skills/README.md).\nRead the matching skill before changing an area, then only the references needed.\n\n**Manaflow AI team members and their agents:** read the private [cmuxterm-hq CLAUDE.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/CLAUDE.md) and [AGENTS.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/AGENTS.md) before fleet or CI work. They are the entry point for fleet builds, CI routing, agent coordination, and landing rules. Start fleet work at [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md). External contributors can ignore this block; those links return 404 for them.\n\n## Verification and isolation\n\n- Before committing, setup or a native build, [choose scoped verification](skills/cmux-testing/references/local-vs-ci-validation.md).\n  Start with `python3 scripts/verify-local.py`; docs and portable tooling need no app build.\n  Run repository commands only in a [trusted checkout](docs/contributor-verification.md#trust-boundary),\n  including `verify-local.py --help`, `--list` and `--repo`. Push does not run checks for you.\n- Use [CONTRIBUTING.md](CONTRIBUTING.md#getting-started) for setup. Outside cmuxterm-hq-created\n  checkouts, set `CMUX_DEV_BACKEND_MODE=local` for dev builds. Follow [tagged builds](skills/cmux-dev-workflow/references/tagged-builds.md)\n  for commands and cache reuse; team fleet tasks start at\n  [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md).\n  Never use bare `xcodebuild` or an untagged `cmux DEV.app`. Clean up only your own tags.\n- A same-repo app PR gets a fleet dogfood build and link comment only while it has the\n  `dev-build` label. Add it when someone will dogfood the PR, not by default; under load\n  the fleet builds the newest push, and the comment says how to build a skipped commit.\n- Never quit, kill, relaunch, replace or launch-profile the user's running cmux\n  (`/Applications/cmux.app`, `com.cmuxterm.app`), including through a Release build or\n  another bundle with that ID. Never set `CMUX_ALLOW_REPLACING_RUNNING_CMUX`; only the\n  user may. Reproduce in a tagged build and attach profiling to its PID.\n- Dogfood through `CMUX_TAG=<tag> scripts/cmux-debug-cli.sh`, never `/tmp/cmux-cli`.\n  Never report raw `.app` paths or `file://` URLs.\n- App-linked code (`Sources/`, `CLI/`, `TunnelExtension/` and their packages) must\n  remain [Swift 6.0 compatible](skills/cmux-architecture/references/swift-6-0-compatibility.md).\n\n## Area instructions\n\nRead these before working in their scope; nested files may not load automatically:\n\n- `ios/` or `Packages/iOS/`: [ios/AGENTS.md](ios/AGENTS.md).\n- `web/` or any cmux Cloud database work: [web/AGENTS.md](web/AGENTS.md).\n- `cmux-tui/`: [cmux-tui/AGENTS.md](cmux-tui/AGENTS.md).\n\n## Contributions and publication\n\nBefore fixing a bug or adding a feature, search open upstream PRs by symptom or\nissue number. Prefer landing an outside contributor's existing PR; push fixups\nonly when maintainer edits are allowed, and explain the changes. If using their\napproach in your own PR, credit them in every such commit with `Co-authored-by`\nusing their commit email, link your PR from theirs and thank them. Let a human\nclose it; never close an outside PR without a human-written explanation.\n\nThe server directories listed in [LICENSE](LICENSE) (`web/`, `workers/ci-artifacts/`,\n`workers/iroh-v2/`, `workers/presence/`, `services/iroh-relay-minter/`,\n`cmux-tui/relays/cloudflare-do/`) use the Business Source License, which needs\nevery outside author's CLA grant. Do not merge a PR that changes those\ndirectories while CLA Assistant is red, and do not copy an outside\ncontributor's work there under a `Co-authored-by` trailer unless that person\nhas signed the CLA. Keep code that ships in the macOS or iOS app out of those\ndirectories.\n\nRead [STYLE.md](STYLE.md) before drafting or revising issues, PR descriptions,\nRFCs or progress updates. Fill the PR's `## Changelog` section with one\n`Added`/`Changed`/`Fixed`/`Removed` line for user-visible changes, otherwise `none`.\nDo not edit `CHANGELOG.md` in feature PRs; release tooling owns it.\n\n## CI, review and merge\n\n- Commit the failing behavioral regression before its fix; record the same\n  focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)).\n  A bug-fix PR body names that command, its failure on the base and its pass on the head,\n  then an `### Observed / Not run` section: what you ran and saw, then what you only read\n  or didn't run. `gh-merge-green` warns when a fix PR lacks it; it does not block.\n- Check executed tests on the current SHA; green skipped jobs do not establish coverage.\n  Add `full-ci` only for a user-requested or agreed broad validation plan,\n  naming the extra lanes and why ([CI coverage](skills/cmux-testing/references/pr-ci-coverage.md)).\n- Keep branches current locally with `scripts/merge-main.sh`; follow\n  [the merge-main guide](docs/ci/merge-main.md) and never force-push over its merge.\n- `gh pr merge` saying \"base branch policy prohibits the merge\" means the token lacks the `workflow`\n  scope or GitHub timed out, not a rule: run `gh auth refresh -h github.com -s workflow`, or merge with\n  `gh api -X PUT repos/OWNER/REPO/pulls/N/merge -f merge_method=squash -f sha=SHA`, which names the cause. Never `--admin`.\n- A first implementation pass ends with passed scoped verification and an open PR;\n  do not watch CI or run speculative reviews by default.\n- Before opening a PR and before merging, check it against [REVIEW.md](REVIEW.md) (draft),\n  the mistakes our review history keeps catching.\n- Before merging, use a [review subagent](skills/cmux-review/SKILL.md), correctness\n  first; a second model is not a review gate. Disclose skipped verification on the PR.\n  `main` is nightly: fix forward, do not revert.\n- A PR merges when an independent review subagent passes it and it causes no red of its own;\n  base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky\n  user-visible behavior behind a setting or Debug toggle and fix a bad default in the next\n  nightly. Merge with `gh-merge-green`; [merge freezes](docs/ci/merge-freeze.md) still hold.\n  `gh-merge-green` still waits for the checks it requires; never get around it with\n  `--override` or the API merge path.\n  Follow [dogfood and merge receipts](skills/cmux-review/SKILL.md#dogfood-and-merge).\n  Notify with `cmux notify` when a socket is available.\n- A red base (`main` doesn't compile, or CI is red on every PR) is priority zero. Fix it\n  directly in its own PR; don't note it and leave it for an owner.\n\n## Implementation rules by task\n\nUse these existing owners instead of duplicating their checklists here:\n\n| Touching | Read before editing |\n| --- | --- |\n| Typing paths, SwiftUI list/store boundaries, rendering, find layering, UTTypes or OS-specific bugs | [cmux-debugging](skills/cmux-debugging/SKILL.md) |\n| Packages, workspace groups, lockfiles or feature flags | [cmux-architecture](skills/cmux-architecture/SKILL.md) |\n| Submodules or GhosttyKit | [cmux-ghostty](skills/cmux-ghostty/SKILL.md) |\n| User-facing strings, docs or help | [cmux-localization](skills/cmux-localization/SKILL.md); report the localization audit |\n| New cmux shortcuts | [cmux-keyboard-shortcuts](skills/cmux-keyboard-shortcuts/SKILL.md) |\n| Tests or target wiring | [cmux-testing](skills/cmux-testing/SKILL.md); run `scripts/sync-test-wiring` after adding, renaming or deleting a `cmuxTests/` file |\n| Multiple entrypoints or a bug that tests previously missed | [cmux-shared-behavior](skills/cmux-shared-behavior/SKILL.md); share action/mutation paths, verify every entrypoint, and cover the missed repro |\n\n## Remote CLI relay\n\nFor v2 socket methods and remote CLI changes, read [relay authorization](skills/cmux-socket-policy/references/remote-relay-authorization.md).\n`RemoteRelayCommandPolicy` defaults to deny. Allowlist only for a needed remote\nflow, scoped to the session's objects; command-bearing params stay denied on\nevery method. The PR must analyze local command/content\nexecution, access to unowned objects and local-state exposure, and include the\nrequired policy tests and ID scoping. Unsafe local effects must be redesigned.\nNever allowlist terminal spawn/respawn without live verification that it executes\non the remote host. An allowlist addition without this analysis blocks review.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/plugin.json)"},"files":{"CLAUDE.md":"# cmux agent notes\n\nKeep repo-wide decisions here; procedures belong in [CONTRIBUTING.md](CONTRIBUTING.md),\n[area instructions](#area-instructions) and [task skills](skills/README.md).\nRead the matching skill before changing an area, then only the references needed.\n\n**Manaflow AI team members and their agents:** read the private [cmuxterm-hq CLAUDE.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/CLAUDE.md) and [AGENTS.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/AGENTS.md) before fleet or CI work. They are the entry point for fleet builds, CI routing, agent coordination, and landing rules. Start fleet work at [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md). External contributors can ignore this block; those links return 404 for them.\n\n## Verification and isolation\n\n- Before committing, setup or a native build, [choose scoped verification](skills/cmux-testing/references/local-vs-ci-validation.md).\n  Start with `python3 scripts/verify-local.py`; docs and portable tooling need no app build.\n  Run repository commands only in a [trusted checkout](docs/contributor-verification.md#trust-boundary),\n  including `verify-local.py --help`, `--list` and `--repo`. Push does not run checks for you.\n- Use [CONTRIBUTING.md](CONTRIBUTING.md#getting-started) for setup. Outside cmuxterm-hq-created\n  checkouts, set `CMUX_DEV_BACKEND_MODE=local` for dev builds. Follow [tagged builds](skills/cmux-dev-workflow/references/tagged-builds.md)\n  for commands and cache reuse; team fleet tasks start at\n  [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md).\n  Never use bare `xcodebuild` or an untagged `cmux DEV.app`. Clean up only your own tags.\n- A same-repo app PR gets a fleet dogfood build and link comment only while it has the\n  `dev-build` label. Add it when someone will dogfood the PR, not by default; under load\n  the fleet builds the newest push, and the comment says how to build a skipped commit.\n- Never quit, kill, relaunch, replace or launch-profile the user's running cmux\n  (`/Applications/cmux.app`, `com.cmuxterm.app`), including through a Release build or\n  another bundle with that ID. Never set `CMUX_ALLOW_REPLACING_RUNNING_CMUX`; only the\n  user may. Reproduce in a tagged build and attach profiling to its PID.\n- Dogfood through `CMUX_TAG=<tag> scripts/cmux-debug-cli.sh`, never `/tmp/cmux-cli`.\n  Never report raw `.app` paths or `file://` URLs.\n- App-linked code (`Sources/`, `CLI/`, `TunnelExtension/` and their packages) must\n  remain [Swift 6.0 compatible](skills/cmux-architecture/references/swift-6-0-compatibility.md).\n\n## Area instructions\n\nRead these before working in their scope; nested files may not load automatically:\n\n- `ios/` or `Packages/iOS/`: [ios/AGENTS.md](ios/AGENTS.md).\n- `web/` or any cmux Cloud database work: [web/AGENTS.md](web/AGENTS.md).\n- `cmux-tui/`: [cmux-tui/AGENTS.md](cmux-tui/AGENTS.md).\n\n## Contributions and publication\n\nBefore fixing a bug or adding a feature, search open upstream PRs by symptom or\nissue number. Prefer landing an outside contributor's existing PR; push fixups\nonly when maintainer edits are allowed, and explain the changes. If using their\napproach in your own PR, credit them in every such commit with `Co-authored-by`\nusing their commit email, link your PR from theirs and thank them. Let a human\nclose it; never close an outside PR without a human-written explanation.\n\nThe server directories listed in [LICENSE](LICENSE) (`web/`, `workers/ci-artifacts/`,\n`workers/iroh-v2/`, `workers/presence/`, `services/iroh-relay-minter/`,\n`cmux-tui/relays/cloudflare-do/`) use the Business Source License, which needs\nevery outside author's CLA grant. Do not merge a PR that changes those\ndirectories while CLA Assistant is red, and do not copy an outside\ncontributor's work there under a `Co-authored-by` trailer unless that person\nhas signed the CLA. Keep code that ships in the macOS or iOS app out of those\ndirectories.\n\nRead [STYLE.md](STYLE.md) before drafting or revising issues, PR descriptions,\nRFCs or progress updates. Fill the PR's `## Changelog` section with one\n`Added`/`Changed`/`Fixed`/`Removed` line for user-visible changes, otherwise `none`.\nDo not edit `CHANGELOG.md` in feature PRs; release tooling owns it.\n\n## CI, review and merge\n\n- Commit the failing behavioral regression before its fix; record the same\n  focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)).\n  A bug-fix PR body names that command, its failure on the base and its pass on the head,\n  then an `### Observed / Not run` section: what you ran and saw, then what you only read\n  or didn't run. `gh-merge-green` warns when a fix PR lacks it; it does not block.\n- Check executed tests on the current SHA; green skipped jobs do not establish coverage.\n  Add `full-ci` only for a user-requested or agreed broad validation plan,\n  naming the extra lanes and why ([CI coverage](skills/cmux-testing/references/pr-ci-coverage.md)).\n- Keep branches current locally with `scripts/merge-main.sh`; follow\n  [the merge-main guide](docs/ci/merge-main.md) and never force-push over its merge.\n- `gh pr merge` saying \"base branch policy prohibits the merge\" means the token lacks the `workflow`\n  scope or GitHub timed out, not a rule: run `gh auth refresh -h github.com -s workflow`, or merge with\n  `gh api -X PUT repos/OWNER/REPO/pulls/N/merge -f merge_method=squash -f sha=SHA`, which names the cause. Never `--admin`.\n- A first implementation pass ends with passed scoped verification and an open PR;\n  do not watch CI or run speculative reviews by default.\n- Before opening a PR and before merging, check it against [REVIEW.md](REVIEW.md) (draft),\n  the mistakes our review history keeps catching.\n- Before merging, use a [review subagent](skills/cmux-review/SKILL.md), correctness\n  first; a second model is not a review gate. Disclose skipped verification on the PR.\n  `main` is nightly: fix forward, do not revert.\n- A PR merges when an independent review subagent passes it and it causes no red of its own;\n  base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky\n  user-visible behavior behind a setting or Debug toggle and fix a bad default in the next\n  nightly. Merge with `gh-merge-green`; [merge freezes](docs/ci/merge-freeze.md) still hold.\n  `gh-merge-green` still waits for the checks it requires; never get around it with\n  `--override` or the API merge path.\n  Follow [dogfood and merge receipts](skills/cmux-review/SKILL.md#dogfood-and-merge).\n  Notify with `cmux notify` when a socket is available.\n- A red base (`main` doesn't compile, or CI is red on every PR) is priority zero. Fix it\n  directly in its own PR; don't note it and leave it for an owner.\n\n## Implementation rules by task\n\nUse these existing owners instead of duplicating their checklists here:\n\n| Touching | Read before editing |\n| --- | --- |\n| Typing paths, SwiftUI list/store boundaries, rendering, find layering, UTTypes or OS-specific bugs | [cmux-debugging](skills/cmux-debugging/SKILL.md) |\n| Packages, workspace groups, lockfiles or feature flags | [cmux-architecture](skills/cmux-architecture/SKILL.md) |\n| Submodules or GhosttyKit | [cmux-ghostty](skills/cmux-ghostty/SKILL.md) |\n| User-facing strings, docs or help | [cmux-localization](skills/cmux-localization/SKILL.md); report the localization audit |\n| New cmux shortcuts | [cmux-keyboard-shortcuts](skills/cmux-keyboard-shortcuts/SKILL.md) |\n| Tests or target wiring | [cmux-testing](skills/cmux-testing/SKILL.md); run `scripts/sync-test-wiring` after adding, renaming or deleting a `cmuxTests/` file |\n| Multiple entrypoints or a bug that tests previously missed | [cmux-shared-behavior](skills/cmux-shared-behavior/SKILL.md); share action/mutation paths, verify every entrypoint, and cover the missed repro |\n\n## Remote CLI relay\n\nFor v2 socket methods and remote CLI changes, read [relay authorization](skills/cmux-socket-policy/references/remote-relay-authorization.md).\n`RemoteRelayCommandPolicy` defaults to deny. Allowlist only for a needed remote\nflow, scoped to the session's objects; command-bearing params stay denied on\nevery method. The PR must analyze local command/content\nexecution, access to unowned objects and local-state exposure, and include the\nrequired policy tests and ID scoping. Unsafe local effects must be redesigned.\nNever allowlist terminal spawn/respawn without live verification that it executes\non the remote host. An allowlist addition without this analysis blocks review.\n","AGENTS.md":"# cmux agent notes\n\nKeep repo-wide decisions here; procedures belong in [CONTRIBUTING.md](CONTRIBUTING.md),\n[area instructions](#area-instructions) and [task skills](skills/README.md).\nRead the matching skill before changing an area, then only the references needed.\n\n**Manaflow AI team members and their agents:** read the private [cmuxterm-hq CLAUDE.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/CLAUDE.md) and [AGENTS.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/AGENTS.md) before fleet or CI work. They are the entry point for fleet builds, CI routing, agent coordination, and landing rules. Start fleet work at [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md). External contributors can ignore this block; those links return 404 for them.\n\n## Verification and isolation\n\n- Before committing, setup or a native build, [choose scoped verification](skills/cmux-testing/references/local-vs-ci-validation.md).\n  Start with `python3 scripts/verify-local.py`; docs and portable tooling need no app build.\n  Run repository commands only in a [trusted checkout](docs/contributor-verification.md#trust-boundary),\n  including `verify-local.py --help`, `--list` and `--repo`. Push does not run checks for you.\n- Use [CONTRIBUTING.md](CONTRIBUTING.md#getting-started) for setup. Outside cmuxterm-hq-created\n  checkouts, set `CMUX_DEV_BACKEND_MODE=local` for dev builds. Follow [tagged builds](skills/cmux-dev-workflow/references/tagged-builds.md)\n  for commands and cache reuse; team fleet tasks start at\n  [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md).\n  Never use bare `xcodebuild` or an untagged `cmux DEV.app`. Clean up only your own tags.\n- A same-repo app PR gets a fleet dogfood build and link comment only while it has the\n  `dev-build` label. Add it when someone will dogfood the PR, not by default; under load\n  the fleet builds the newest push, and the comment says how to build a skipped commit.\n- Never quit, kill, relaunch, replace or launch-profile the user's running cmux\n  (`/Applications/cmux.app`, `com.cmuxterm.app`), including through a Release build or\n  another bundle with that ID. Never set `CMUX_ALLOW_REPLACING_RUNNING_CMUX`; only the\n  user may. Reproduce in a tagged build and attach profiling to its PID.\n- Dogfood through `CMUX_TAG=<tag> scripts/cmux-debug-cli.sh`, never `/tmp/cmux-cli`.\n  Never report raw `.app` paths or `file://` URLs.\n- App-linked code (`Sources/`, `CLI/`, `TunnelExtension/` and their packages) must\n  remain [Swift 6.0 compatible](skills/cmux-architecture/references/swift-6-0-compatibility.md).\n\n## Area instructions\n\nRead these before working in their scope; nested files may not load automatically:\n\n- `ios/` or `Packages/iOS/`: [ios/AGENTS.md](ios/AGENTS.md).\n- `web/` or any cmux Cloud database work: [web/AGENTS.md](web/AGENTS.md).\n- `cmux-tui/`: [cmux-tui/AGENTS.md](cmux-tui/AGENTS.md).\n\n## Contributions and publication\n\nBefore fixing a bug or adding a feature, search open upstream PRs by symptom or\nissue number. Prefer landing an outside contributor's existing PR; push fixups\nonly when maintainer edits are allowed, and explain the changes. If using their\napproach in your own PR, credit them in every such commit with `Co-authored-by`\nusing their commit email, link your PR from theirs and thank them. Let a human\nclose it; never close an outside PR without a human-written explanation.\n\nThe server directories listed in [LICENSE](LICENSE) (`web/`, `workers/ci-artifacts/`,\n`workers/iroh-v2/`, `workers/presence/`, `services/iroh-relay-minter/`,\n`cmux-tui/relays/cloudflare-do/`) use the Business Source License, which needs\nevery outside author's CLA grant. Do not merge a PR that changes those\ndirectories while CLA Assistant is red, and do not copy an outside\ncontributor's work there under a `Co-authored-by` trailer unless that person\nhas signed the CLA. Keep code that ships in the macOS or iOS app out of those\ndirectories.\n\nRead [STYLE.md](STYLE.md) before drafting or revising issues, PR descriptions,\nRFCs or progress updates. Fill the PR's `## Changelog` section with one\n`Added`/`Changed`/`Fixed`/`Removed` line for user-visible changes, otherwise `none`.\nDo not edit `CHANGELOG.md` in feature PRs; release tooling owns it.\n\n## CI, review and merge\n\n- Commit the failing behavioral regression before its fix; record the same\n  focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)).\n  A bug-fix PR body names that command, its failure on the base and its pass on the head,\n  then an `### Observed / Not run` section: what you ran and saw, then what you only read\n  or didn't run. `gh-merge-green` warns when a fix PR lacks it; it does not block.\n- Check executed tests on the current SHA; green skipped jobs do not establish coverage.\n  Add `full-ci` only for a user-requested or agreed broad validation plan,\n  naming the extra lanes and why ([CI coverage](skills/cmux-testing/references/pr-ci-coverage.md)).\n- Keep branches current locally with `scripts/merge-main.sh`; follow\n  [the merge-main guide](docs/ci/merge-main.md) and never force-push over its merge.\n- `gh pr merge` saying \"base branch policy prohibits the merge\" means the token lacks the `workflow`\n  scope or GitHub timed out, not a rule: run `gh auth refresh -h github.com -s workflow`, or merge with\n  `gh api -X PUT repos/OWNER/REPO/pulls/N/merge -f merge_method=squash -f sha=SHA`, which names the cause. Never `--admin`.\n- A first implementation pass ends with passed scoped verification and an open PR;\n  do not watch CI or run speculative reviews by default.\n- Before opening a PR and before merging, check it against [REVIEW.md](REVIEW.md) (draft),\n  the mistakes our review history keeps catching.\n- Before merging, use a [review subagent](skills/cmux-review/SKILL.md), correctness\n  first; a second model is not a review gate. Disclose skipped verification on the PR.\n  `main` is nightly: fix forward, do not revert.\n- A PR merges when an independent review subagent passes it and it causes no red of its own;\n  base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky\n  user-visible behavior behind a setting or Debug toggle and fix a bad default in the next\n  nightly. Merge with `gh-merge-green`; [merge freezes](docs/ci/merge-freeze.md) still hold.\n  `gh-merge-green` still waits for the checks it requires; never get around it with\n  `--override` or the API merge path.\n  Follow [dogfood and merge receipts](skills/cmux-review/SKILL.md#dogfood-and-merge).\n  Notify with `cmux notify` when a socket is available.\n- A red base (`main` doesn't compile, or CI is red on every PR) is priority zero. Fix it\n  directly in its own PR; don't note it and leave it for an owner.\n\n## Implementation rules by task\n\nUse these existing owners instead of duplicating their checklists here:\n\n| Touching | Read before editing |\n| --- | --- |\n| Typing paths, SwiftUI list/store boundaries, rendering, find layering, UTTypes or OS-specific bugs | [cmux-debugging](skills/cmux-debugging/SKILL.md) |\n| Packages, workspace groups, lockfiles or feature flags | [cmux-architecture](skills/cmux-architecture/SKILL.md) |\n| Submodules or GhosttyKit | [cmux-ghostty](skills/cmux-ghostty/SKILL.md) |\n| User-facing strings, docs or help | [cmux-localization](skills/cmux-localization/SKILL.md); report the localization audit |\n| New cmux shortcuts | [cmux-keyboard-shortcuts](skills/cmux-keyboard-shortcuts/SKILL.md) |\n| Tests or target wiring | [cmux-testing](skills/cmux-testing/SKILL.md); run `scripts/sync-test-wiring` after adding, renaming or deleting a `cmuxTests/` file |\n| Multiple entrypoints or a bug that tests previously missed | [cmux-shared-behavior](skills/cmux-shared-behavior/SKILL.md); share action/mutation paths, verify every entrypoint, and cover the missed repro |\n\n## Remote CLI relay\n\nFor v2 socket methods and remote CLI changes, read [relay authorization](skills/cmux-socket-policy/references/remote-relay-authorization.md).\n`RemoteRelayCommandPolicy` defaults to deny. Allowlist only for a needed remote\nflow, scoped to the session's objects; command-bearing params stay denied on\nevery method. The PR must analyze local command/content\nexecution, access to unowned objects and local-state exposure, and include the\nrequired policy tests and ID scoping. Unsafe local effects must be redesigned.\nNever allowlist terminal spawn/respawn without live verification that it executes\non the remote host. An allowlist addition without this analysis blocks review.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# cmux agent notes\n\nKeep repo-wide decisions here; procedures belong in [CONTRIBUTING.md](CONTRIBUTING.md),\n[area instructions](#area-instructions) and [task skills](skills/README.md).\nRead the matching skill before changing an area, then only the references needed.\n\n**Manaflow AI team members and their agents:** read the private [cmuxterm-hq CLAUDE.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/CLAUDE.md) and [AGENTS.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/AGENTS.md) before fleet or CI work. They are the entry point for fleet builds, CI routing, agent coordination, and landing rules. Start fleet work at [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md). External contributors can ignore this block; those links return 404 for them.\n\n## Verification and isolation\n\n- Before committing, setup or a native build, [choose scoped verification](skills/cmux-testing/references/local-vs-ci-validation.md).\n  Start with `python3 scripts/verify-local.py`; docs and portable tooling need no app build.\n  Run repository commands only in a [trusted checkout](docs/contributor-verification.md#trust-boundary),\n  including `verify-local.py --help`, `--list` and `--repo`. Push does not run checks for you.\n- Use [CONTRIBUTING.md](CONTRIBUTING.md#getting-started) for setup. Outside cmuxterm-hq-created\n  checkouts, set `CMUX_DEV_BACKEND_MODE=local` for dev builds. Follow [tagged builds](skills/cmux-dev-workflow/references/tagged-builds.md)\n  for commands and cache reuse; team fleet tasks start at\n  [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md).\n  Never use bare `xcodebuild` or an untagged `cmux DEV.app`. Clean up only your own tags.\n- A same-repo app PR gets a fleet dogfood build and link comment only while it has the\n  `dev-build` label. Add it when someone will dogfood the PR, not by default; under load\n  the fleet builds the newest push, and the comment says how to build a skipped commit.\n- Never quit, kill, relaunch, replace or launch-profile the user's running cmux\n  (`/Applications/cmux.app`, `com.cmuxterm.app`), including through a Release build or\n  another bundle with that ID. Never set `CMUX_ALLOW_REPLACING_RUNNING_CMUX`; only the\n  user may. Reproduce in a tagged build and attach profiling to its PID.\n- Dogfood through `CMUX_TAG=<tag> scripts/cmux-debug-cli.sh`, never `/tmp/cmux-cli`.\n  Never report raw `.app` paths or `file://` URLs.\n- App-linked code (`Sources/`, `CLI/`, `TunnelExtension/` and their packages) must\n  remain [Swift 6.0 compatible](skills/cmux-architecture/references/swift-6-0-compatibility.md).\n\n## Area instructions\n\nRead these before working in their scope; nested files may not load automatically:\n\n- `ios/` or `Packages/iOS/`: [ios/AGENTS.md](ios/AGENTS.md).\n- `web/` or any cmux Cloud database work: [web/AGENTS.md](web/AGENTS.md).\n- `cmux-tui/`: [cmux-tui/AGENTS.md](cmux-tui/AGENTS.md).\n\n## Contributions and publication\n\nBefore fixing a bug or adding a feature, search open upstream PRs by symptom or\nissue number. Prefer landing an outside contributor's existing PR; push fixups\nonly when maintainer edits are allowed, and explain the changes. If using their\napproach in your own PR, credit them in every such commit with `Co-authored-by`\nusing their commit email, link your PR from theirs and thank them. Let a human\nclose it; never close an outside PR without a human-written explanation.\n\nThe server directories listed in [LICENSE](LICENSE) (`web/`, `workers/ci-artifacts/`,\n`workers/iroh-v2/`, `workers/presence/`, `services/iroh-relay-minter/`,\n`cmux-tui/relays/cloudflare-do/`) use the Business Source License, which needs\nevery outside author's CLA grant. Do not merge a PR that changes those\ndirectories while CLA Assistant is red, and do not copy an outside\ncontributor's work there under a `Co-authored-by` trailer unless that person\nhas signed the CLA. Keep code that ships in the macOS or iOS app out of those\ndirectories.\n\nRead [STYLE.md](STYLE.md) before drafting or revising issues, PR descriptions,\nRFCs or progress updates. Fill the PR's `## Changelog` section with one\n`Added`/`Changed`/`Fixed`/`Removed` line for user-visible changes, otherwise `none`.\nDo not edit `CHANGELOG.md` in feature PRs; release tooling owns it.\n\n## CI, review and merge\n\n- Commit the failing behavioral regression before its fix; record the same\n  focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)).\n  A bug-fix PR body names that command, its failure on the base and its pass on the head,\n  then an `### Observed / Not run` section: what you ran and saw, then what you only read\n  or didn't run. `gh-merge-green` warns when a fix PR lacks it; it does not block.\n- Check executed tests on the current SHA; green skipped jobs do not establish coverage.\n  Add `full-ci` only for a user-requested or agreed broad validation plan,\n  naming the extra lanes and why ([CI coverage](skills/cmux-testing/references/pr-ci-coverage.md)).\n- Keep branches current locally with `scripts/merge-main.sh`; follow\n  [the merge-main guide](docs/ci/merge-main.md) and never force-push over its merge.\n- `gh pr merge` saying \"base branch policy prohibits the merge\" means the token lacks the `workflow`\n  scope or GitHub timed out, not a rule: run `gh auth refresh -h github.com -s workflow`, or merge with\n  `gh api -X PUT repos/OWNER/REPO/pulls/N/merge -f merge_method=squash -f sha=SHA`, which names the cause. Never `--admin`.\n- A first implementation pass ends with passed scoped verification and an open PR;\n  do not watch CI or run speculative reviews by default.\n- Before opening a PR and before merging, check it against [REVIEW.md](REVIEW.md) (draft),\n  the mistakes our review history keeps catching.\n- Before merging, use a [review subagent](skills/cmux-review/SKILL.md), correctness\n  first; a second model is not a review gate. Disclose skipped verification on the PR.\n  `main` is nightly: fix forward, do not revert.\n- A PR merges when an independent review subagent passes it and it causes no red of its own;\n  base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky\n  user-visible behavior behind a setting or Debug toggle and fix a bad default in the next\n  nightly. Merge with `gh-merge-green`; [merge freezes](docs/ci/merge-freeze.md) still hold.\n  `gh-merge-green` still waits for the checks it requires; never get around it with\n  `--override` or the API merge path.\n  Follow [dogfood and merge receipts](skills/cmux-review/SKILL.md#dogfood-and-merge).\n  Notify with `cmux notify` when a socket is available.\n- A red base (`main` doesn't compile, or CI is red on every PR) is priority zero. Fix it\n  directly in its own PR; don't note it and leave it for an owner.\n\n## Implementation rules by task\n\nUse these existing owners instead of duplicating their checklists here:\n\n| Touching | Read before editing |\n| --- | --- |\n| Typing paths, SwiftUI list/store boundaries, rendering, find layering, UTTypes or OS-specific bugs | [cmux-debugging](skills/cmux-debugging/SKILL.md) |\n| Packages, workspace groups, lockfiles or feature flags | [cmux-architecture](skills/cmux-architecture/SKILL.md) |\n| Submodules or GhosttyKit | [cmux-ghostty](skills/cmux-ghostty/SKILL.md) |\n| User-facing strings, docs or help | [cmux-localization](skills/cmux-localization/SKILL.md); report the localization audit |\n| New cmux shortcuts | [cmux-keyboard-shortcuts](skills/cmux-keyboard-shortcuts/SKILL.md) |\n| Tests or target wiring | [cmux-testing](skills/cmux-testing/SKILL.md); run `scripts/sync-test-wiring` after adding, renaming or deleting a `cmuxTests/` file |\n| Multiple entrypoints or a bug that tests previously missed | [cmux-shared-behavior](skills/cmux-shared-behavior/SKILL.md); share action/mutation paths, verify every entrypoint, and cover the missed repro |\n\n## Remote CLI relay\n\nFor v2 socket methods and remote CLI changes, read [relay authorization](skills/cmux-socket-policy/references/remote-relay-authorization.md).\n`RemoteRelayCommandPolicy` defaults to deny. Allowlist only for a needed remote\nflow, scoped to the session's objects; command-bearing params stay denied on\nevery method. The PR must analyze local command/content\nexecution, access to unowned objects and local-state exposure, and include the\nrequired policy tests and ID scoping. Unsafe local effects must be redesigned.\nNever allowlist terminal spawn/respawn without live verification that it executes\non the remote host. An allowlist addition without this analysis blocks review.\n","isInternal":false,"tokens":2181,"sizeBytes":8640},{"name":"CLAUDE.md","path":"CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/CLAUDE.md","title":"Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","content":"# cmux agent notes\n\nKeep repo-wide decisions here; procedures belong in [CONTRIBUTING.md](CONTRIBUTING.md),\n[area instructions](#area-instructions) and [task skills](skills/README.md).\nRead the matching skill before changing an area, then only the references needed.\n\n**Manaflow AI team members and their agents:** read the private [cmuxterm-hq CLAUDE.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/CLAUDE.md) and [AGENTS.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/AGENTS.md) before fleet or CI work. They are the entry point for fleet builds, CI routing, agent coordination, and landing rules. Start fleet work at [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md). External contributors can ignore this block; those links return 404 for them.\n\n## Verification and isolation\n\n- Before committing, setup or a native build, [choose scoped verification](skills/cmux-testing/references/local-vs-ci-validation.md).\n  Start with `python3 scripts/verify-local.py`; docs and portable tooling need no app build.\n  Run repository commands only in a [trusted checkout](docs/contributor-verification.md#trust-boundary),\n  including `verify-local.py --help`, `--list` and `--repo`. Push does not run checks for you.\n- Use [CONTRIBUTING.md](CONTRIBUTING.md#getting-started) for setup. Outside cmuxterm-hq-created\n  checkouts, set `CMUX_DEV_BACKEND_MODE=local` for dev builds. Follow [tagged builds](skills/cmux-dev-workflow/references/tagged-builds.md)\n  for commands and cache reuse; team fleet tasks start at\n  [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md).\n  Never use bare `xcodebuild` or an untagged `cmux DEV.app`. Clean up only your own tags.\n- A same-repo app PR gets a fleet dogfood build and link comment only while it has the\n  `dev-build` label. Add it when someone will dogfood the PR, not by default; under load\n  the fleet builds the newest push, and the comment says how to build a skipped commit.\n- Never quit, kill, relaunch, replace or launch-profile the user's running cmux\n  (`/Applications/cmux.app`, `com.cmuxterm.app`), including through a Release build or\n  another bundle with that ID. Never set `CMUX_ALLOW_REPLACING_RUNNING_CMUX`; only the\n  user may. Reproduce in a tagged build and attach profiling to its PID.\n- Dogfood through `CMUX_TAG=<tag> scripts/cmux-debug-cli.sh`, never `/tmp/cmux-cli`.\n  Never report raw `.app` paths or `file://` URLs.\n- App-linked code (`Sources/`, `CLI/`, `TunnelExtension/` and their packages) must\n  remain [Swift 6.0 compatible](skills/cmux-architecture/references/swift-6-0-compatibility.md).\n\n## Area instructions\n\nRead these before working in their scope; nested files may not load automatically:\n\n- `ios/` or `Packages/iOS/`: [ios/AGENTS.md](ios/AGENTS.md).\n- `web/` or any cmux Cloud database work: [web/AGENTS.md](web/AGENTS.md).\n- `cmux-tui/`: [cmux-tui/AGENTS.md](cmux-tui/AGENTS.md).\n\n## Contributions and publication\n\nBefore fixing a bug or adding a feature, search open upstream PRs by symptom or\nissue number. Prefer landing an outside contributor's existing PR; push fixups\nonly when maintainer edits are allowed, and explain the changes. If using their\napproach in your own PR, credit them in every such commit with `Co-authored-by`\nusing their commit email, link your PR from theirs and thank them. Let a human\nclose it; never close an outside PR without a human-written explanation.\n\nThe server directories listed in [LICENSE](LICENSE) (`web/`, `workers/ci-artifacts/`,\n`workers/iroh-v2/`, `workers/presence/`, `services/iroh-relay-minter/`,\n`cmux-tui/relays/cloudflare-do/`) use the Business Source License, which needs\nevery outside author's CLA grant. Do not merge a PR that changes those\ndirectories while CLA Assistant is red, and do not copy an outside\ncontributor's work there under a `Co-authored-by` trailer unless that person\nhas signed the CLA. Keep code that ships in the macOS or iOS app out of those\ndirectories.\n\nRead [STYLE.md](STYLE.md) before drafting or revising issues, PR descriptions,\nRFCs or progress updates. Fill the PR's `## Changelog` section with one\n`Added`/`Changed`/`Fixed`/`Removed` line for user-visible changes, otherwise `none`.\nDo not edit `CHANGELOG.md` in feature PRs; release tooling owns it.\n\n## CI, review and merge\n\n- Commit the failing behavioral regression before its fix; record the same\n  focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)).\n  A bug-fix PR body names that command, its failure on the base and its pass on the head,\n  then an `### Observed / Not run` section: what you ran and saw, then what you only read\n  or didn't run. `gh-merge-green` warns when a fix PR lacks it; it does not block.\n- Check executed tests on the current SHA; green skipped jobs do not establish coverage.\n  Add `full-ci` only for a user-requested or agreed broad validation plan,\n  naming the extra lanes and why ([CI coverage](skills/cmux-testing/references/pr-ci-coverage.md)).\n- Keep branches current locally with `scripts/merge-main.sh`; follow\n  [the merge-main guide](docs/ci/merge-main.md) and never force-push over its merge.\n- `gh pr merge` saying \"base branch policy prohibits the merge\" means the token lacks the `workflow`\n  scope or GitHub timed out, not a rule: run `gh auth refresh -h github.com -s workflow`, or merge with\n  `gh api -X PUT repos/OWNER/REPO/pulls/N/merge -f merge_method=squash -f sha=SHA`, which names the cause. Never `--admin`.\n- A first implementation pass ends with passed scoped verification and an open PR;\n  do not watch CI or run speculative reviews by default.\n- Before opening a PR and before merging, check it against [REVIEW.md](REVIEW.md) (draft),\n  the mistakes our review history keeps catching.\n- Before merging, use a [review subagent](skills/cmux-review/SKILL.md), correctness\n  first; a second model is not a review gate. Disclose skipped verification on the PR.\n  `main` is nightly: fix forward, do not revert.\n- A PR merges when an independent review subagent passes it and it causes no red of its own;\n  base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky\n  user-visible behavior behind a setting or Debug toggle and fix a bad default in the next\n  nightly. Merge with `gh-merge-green`; [merge freezes](docs/ci/merge-freeze.md) still hold.\n  `gh-merge-green` still waits for the checks it requires; never get around it with\n  `--override` or the API merge path.\n  Follow [dogfood and merge receipts](skills/cmux-review/SKILL.md#dogfood-and-merge).\n  Notify with `cmux notify` when a socket is available.\n- A red base (`main` doesn't compile, or CI is red on every PR) is priority zero. Fix it\n  directly in its own PR; don't note it and leave it for an owner.\n\n## Implementation rules by task\n\nUse these existing owners instead of duplicating their checklists here:\n\n| Touching | Read before editing |\n| --- | --- |\n| Typing paths, SwiftUI list/store boundaries, rendering, find layering, UTTypes or OS-specific bugs | [cmux-debugging](skills/cmux-debugging/SKILL.md) |\n| Packages, workspace groups, lockfiles or feature flags | [cmux-architecture](skills/cmux-architecture/SKILL.md) |\n| Submodules or GhosttyKit | [cmux-ghostty](skills/cmux-ghostty/SKILL.md) |\n| User-facing strings, docs or help | [cmux-localization](skills/cmux-localization/SKILL.md); report the localization audit |\n| New cmux shortcuts | [cmux-keyboard-shortcuts](skills/cmux-keyboard-shortcuts/SKILL.md) |\n| Tests or target wiring | [cmux-testing](skills/cmux-testing/SKILL.md); run `scripts/sync-test-wiring` after adding, renaming or deleting a `cmuxTests/` file |\n| Multiple entrypoints or a bug that tests previously missed | [cmux-shared-behavior](skills/cmux-shared-behavior/SKILL.md); share action/mutation paths, verify every entrypoint, and cover the missed repro |\n\n## Remote CLI relay\n\nFor v2 socket methods and remote CLI changes, read [relay authorization](skills/cmux-socket-policy/references/remote-relay-authorization.md).\n`RemoteRelayCommandPolicy` defaults to deny. Allowlist only for a needed remote\nflow, scoped to the session's objects; command-bearing params stay denied on\nevery method. The PR must analyze local command/content\nexecution, access to unowned objects and local-state exposure, and include the\nrequired policy tests and ID scoping. Unsafe local effects must be redesigned.\nNever allowlist terminal spawn/respawn without live verification that it executes\non the remote host. An allowlist addition without this analysis blocks review.\n","isInternal":false,"tokens":2181,"sizeBytes":8640},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":195},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":181},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":174}],"systemPromptSnippet":"<yakaai_skills repo=\"manaflow-ai/cmux\">\n<!-- File: AGENTS.md (Tokens: ~2181 | Category: root-instruction) -->\n# cmux agent notes\n\nKeep repo-wide decisions here; procedures belong in [CONTRIBUTING.md](CONTRIBUTING.md),\n[area instructions](#area-instructions) and [task skills](skills/README.md).\nRead the matching skill before changing an area, then only the references needed.\n\n**Manaflow AI team members and their agents:** read the private [cmuxterm-hq CLAUDE.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/CLAUDE.md) and [AGENTS.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/AGENTS.md) before fleet or CI work. They are the entry point for fleet builds, CI routing, agent coordination, and landing rules. Start fleet work at [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md). External contributors can ignore this block; those links return 404 for them.\n\n## Verification and isolation\n\n- Before committing, setup or a native build, [choose scoped verification](skills/cmux-testing/references/local-vs-ci-validation.md).\n  Start with `python3 scripts/verify-local.py`; docs and portable tooling need no app build.\n  Run repository commands only in a [trusted checkout](docs/contributor-verification.md#trust-boundary),\n  including `verify-local.py --help`, `--list` and `--repo`. Push does not run checks for you.\n- Use [CONTRIBUTING.md](CONTRIBUTING.md#getting-started) for setup. Outside cmuxterm-hq-created\n  checkouts, set `CMUX_DEV_BACKEND_MODE=local` for dev builds. Follow [tagged builds](skills/cmux-dev-workflow/references/tagged-builds.md)\n  for commands and cache reuse; team fleet tasks start at\n  [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md).\n  Never use bare `xcodebuild` or an untagged `cmux DEV.app`. Clean up only your own tags.\n- A same-repo app PR gets a fleet dogfood build and link comment only while it has the\n  `dev-build` label. Add it when someone will dogfood the PR, not by default; under load\n  the fleet builds the newest push, and the comment says how to build a skipped commit.\n- Never quit, kill, relaunch, replace or launch-profile the user's running cmux\n  (`/Applications/cmux.app`, `com.cmuxterm.app`), including through a Release build or\n  another bundle with that ID. Never set `CMUX_ALLOW_REPLACING_RUNNING_CMUX`; only the\n  user may. Reproduce in a tagged build and attach profiling to its PID.\n- Dogfood through `CMUX_TAG=<tag> scripts/cmux-debug-cli.sh`, never `/tmp/cmux-cli`.\n  Never report raw `.app` paths or `file://` URLs.\n- App-linked code (`Sources/`, `CLI/`, `TunnelExtension/` and their packages) must\n  remain [Swift 6.0 compatible](skills/cmux-architecture/references/swift-6-0-compatibility.md).\n\n## Area instructions\n\nRead these before working in their scope; nested files may not load automatically:\n\n- `ios/` or `Packages/iOS/`: [ios/AGENTS.md](ios/AGENTS.md).\n- `web/` or any cmux Cloud database work: [web/AGENTS.md](web/AGENTS.md).\n- `cmux-tui/`: [cmux-tui/AGENTS.md](cmux-tui/AGENTS.md).\n\n## Contributions and publication\n\nBefore fixing a bug or adding a feature, search open upstream PRs by symptom or\nissue number. Prefer landing an outside contributor's existing PR; push fixups\nonly when maintainer edits are allowed, and explain the changes. If using their\napproach in your own PR, credit them in every such commit with `Co-authored-by`\nusing their commit email, link your PR from theirs and thank them. Let a human\nclose it; never close an outside PR without a human-written explanation.\n\nThe server directories listed in [LICENSE](LICENSE) (`web/`, `workers/ci-artifacts/`,\n`workers/iroh-v2/`, `workers/presence/`, `services/iroh-relay-minter/`,\n`cmux-tui/relays/cloudflare-do/`) use the Business Source License, which needs\nevery outside author's CLA grant. Do not merge a PR that changes those\ndirectories while CLA Assistant is red, and do not copy an outside\ncontributor's work there under a `Co-authored-by` trailer unless that person\nhas signed the CLA. Keep code that ships in the macOS or iOS app out of those\ndirectories.\n\nRead [STYLE.md](STYLE.md) before drafting or revising issues, PR descriptions,\nRFCs or progress updates. Fill the PR's `## Changelog` section with one\n`Added`/`Changed`/`Fixed`/`Removed` line for user-visible changes, otherwise `none`.\nDo not edit `CHANGELOG.md` in feature PRs; release tooling owns it.\n\n## CI, review and merge\n\n- Commit the failing behavioral regression before its fix; record the same\n  focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)).\n  A bug-fix PR body names that command, its failure on the base and its pass on the head,\n  then an `### Observed / Not run` section: what you ran and saw, then what you only read\n  or didn't run. `gh-merge-green` warns when a fix PR lacks it; it does not block.\n- Check executed tests on the current SHA; green skipped jobs do not establish coverage.\n  Add `full-ci` only for a user-requested or agreed broad validation plan,\n  naming the extra lanes and why ([CI coverage](skills/cmux-testing/references/pr-ci-coverage.md)).\n- Keep branches current locally with `scripts/merge-main.sh`; follow\n  [the merge-main guide](docs/ci/merge-main.md) and never force-push over its merge.\n- `gh pr merge` saying \"base branch policy prohibits the merge\" means the token lacks the `workflow`\n  scope or GitHub timed out, not a rule: run `gh auth refresh -h github.com -s workflow`, or merge with\n  `gh api -X PUT repos/OWNER/REPO/pulls/N/merge -f merge_method=squash -f sha=SHA`, which names the cause. Never `--admin`.\n- A first implementation pass ends with passed scoped verification and an open PR;\n  do not watch CI or run speculative reviews by default.\n- Before opening a PR and before merging, check it against [REVIEW.md](REVIEW.md) (draft),\n  the mistakes our review history keeps catching.\n- Before merging, use a [review subagent](skills/cmux-review/SKILL.md), correctness\n  first; a second model is not a review gate. Disclose skipped verification on the PR.\n  `main` is nightly: fix forward, do not revert.\n- A PR merges when an independent review subagent passes it and it causes no red of its own;\n  base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky\n  user-visible behavior behind a setting or Debug toggle and fix a bad default in the next\n  nightly. Merge with `gh-merge-green`; [merge freezes](docs/ci/merge-freeze.md) still hold.\n  `gh-merge-green` still waits for the checks it requires; never get around it with\n  `--override` or the API merge path.\n  Follow [dogfood and merge receipts](skills/cmux-review/SKILL.md#dogfood-and-merge).\n  Notify with `cmux notify` when a socket is available.\n- A red base (`main` doesn't compile, or CI is red on every PR) is priority zero. Fix it\n  directly in its own PR; don't note it and leave it for an owner.\n\n## Implementation rules by task\n\nUse these existing owners instead of duplicating their checklists here:\n\n| Touching | Read before editing |\n| --- | --- |\n| Typing paths, SwiftUI list/store boundaries, rendering, find layering, UTTypes or OS-specific bugs | [cmux-debugging](skills/cmux-debugging/SKILL.md) |\n| Packages, workspace groups, lockfiles or feature flags | [cmux-architecture](skills/cmux-architecture/SKILL.md) |\n| Submodules or GhosttyKit | [cmux-ghostty](skills/cmux-ghostty/SKILL.md) |\n| User-facing strings, docs or help | [cmux-localization](skills/cmux-localization/SKILL.md); report the localization audit |\n| New cmux shortcuts | [cmux-keyboard-shortcuts](skills/cmux-keyboard-shortcuts/SKILL.md) |\n| Tests or target wiring | [cmux-testing](skills/cmux-testing/SKILL.md); run `scripts/sync-test-wiring` after adding, renaming or deleting a `cmuxTests/` file |\n| Multiple entrypoints or a bug that tests previously missed | [cmux-shared-behavior](skills/cmux-shared-behavior/SKILL.md); share action/mutation paths, verify every entrypoint, and cover the missed repro |\n\n## Remote CLI relay\n\nFor v2 socket methods and remote CLI changes, read [relay authorization](skills/cmux-socket-policy/references/remote-relay-authorization.md).\n`RemoteRelayCommandPolicy` defaults to deny. Allowlist only for a needed remote\nflow, scoped to the session's objects; command-bearing params stay denied on\nevery method. The PR must analyze local command/content\nexecution, access to unowned objects and local-state exposure, and include the\nrequired policy tests and ID scoping. Unsafe local effects must be redesigned.\nNever allowlist terminal spawn/respawn without live verification that it executes\non the remote host. An allowlist addition without this analysis blocks review.\n\n<!-- File: CLAUDE.md (Tokens: ~2181 | Category: claude-rule) -->\n# cmux agent notes\n\nKeep repo-wide decisions here; procedures belong in [CONTRIBUTING.md](CONTRIBUTING.md),\n[area instructions](#area-instructions) and [task skills](skills/README.md).\nRead the matching skill before changing an area, then only the references needed.\n\n**Manaflow AI team members and their agents:** read the private [cmuxterm-hq CLAUDE.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/CLAUDE.md) and [AGENTS.md](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/AGENTS.md) before fleet or CI work. They are the entry point for fleet builds, CI routing, agent coordination, and landing rules. Start fleet work at [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md). External contributors can ignore this block; those links return 404 for them.\n\n## Verification and isolation\n\n- Before committing, setup or a native build, [choose scoped verification](skills/cmux-testing/references/local-vs-ci-validation.md).\n  Start with `python3 scripts/verify-local.py`; docs and portable tooling need no app build.\n  Run repository commands only in a [trusted checkout](docs/contributor-verification.md#trust-boundary),\n  including `verify-local.py --help`, `--list` and `--repo`. Push does not run checks for you.\n- Use [CONTRIBUTING.md](CONTRIBUTING.md#getting-started) for setup. Outside cmuxterm-hq-created\n  checkouts, set `CMUX_DEV_BACKEND_MODE=local` for dev builds. Follow [tagged builds](skills/cmux-dev-workflow/references/tagged-builds.md)\n  for commands and cache reuse; team fleet tasks start at\n  [Fleet and CI: start here](https://github.com/manaflow-ai/cmuxterm-hq/blob/main/build-fleet/FLEET-AND-CI.md).\n  Never use bare `xcodebuild` or an untagged `cmux DEV.app`. Clean up only your own tags.\n- A same-repo app PR gets a fleet dogfood build and link comment only while it has the\n  `dev-build` label. Add it when someone will dogfood the PR, not by default; under load\n  the fleet builds the newest push, and the comment says how to build a skipped commit.\n- Never quit, kill, relaunch, replace or launch-profile the user's running cmux\n  (`/Applications/cmux.app`, `com.cmuxterm.app`), including through a Release build or\n  another bundle with that ID. Never set `CMUX_ALLOW_REPLACING_RUNNING_CMUX`; only the\n  user may. Reproduce in a tagged build and attach profiling to its PID.\n- Dogfood through `CMUX_TAG=<tag> scripts/cmux-debug-cli.sh`, never `/tmp/cmux-cli`.\n  Never report raw `.app` paths or `file://` URLs.\n- App-linked code (`Sources/`, `CLI/`, `TunnelExtension/` and their packages) must\n  remain [Swift 6.0 compatible](skills/cmux-architecture/references/swift-6-0-compatibility.md).\n\n## Area instructions\n\nRead these before working in their scope; nested files may not load automatically:\n\n- `ios/` or `Packages/iOS/`: [ios/AGENTS.md](ios/AGENTS.md).\n- `web/` or any cmux Cloud database work: [web/AGENTS.md](web/AGENTS.md).\n- `cmux-tui/`: [cmux-tui/AGENTS.md](cmux-tui/AGENTS.md).\n\n## Contributions and publication\n\nBefore fixing a bug or adding a feature, search open upstream PRs by symptom or\nissue number. Prefer landing an outside contributor's existing PR; push fixups\nonly when maintainer edits are allowed, and explain the changes. If using their\napproach in your own PR, credit them in every such commit with `Co-authored-by`\nusing their commit email, link your PR from theirs and thank them. Let a human\nclose it; never close an outside PR without a human-written explanation.\n\nThe server directories listed in [LICENSE](LICENSE) (`web/`, `workers/ci-artifacts/`,\n`workers/iroh-v2/`, `workers/presence/`, `services/iroh-relay-minter/`,\n`cmux-tui/relays/cloudflare-do/`) use the Business Source License, which needs\nevery outside author's CLA grant. Do not merge a PR that changes those\ndirectories while CLA Assistant is red, and do not copy an outside\ncontributor's work there under a `Co-authored-by` trailer unless that person\nhas signed the CLA. Keep code that ships in the macOS or iOS app out of those\ndirectories.\n\nRead [STYLE.md](STYLE.md) before drafting or revising issues, PR descriptions,\nRFCs or progress updates. Fill the PR's `## Changelog` section with one\n`Added`/`Changed`/`Fixed`/`Removed` line for user-visible changes, otherwise `none`.\nDo not edit `CHANGELOG.md` in feature PRs; release tooling owns it.\n\n## CI, review and merge\n\n- Commit the failing behavioral regression before its fix; record the same\n  focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)).\n  A bug-fix PR body names that command, its failure on the base and its pass on the head,\n  then an `### Observed / Not run` section: what you ran and saw, then what you only read\n  or didn't run. `gh-merge-green` warns when a fix PR lacks it; it does not block.\n- Check executed tests on the current SHA; green skipped jobs do not establish coverage.\n  Add `full-ci` only for a user-requested or agreed broad validation plan,\n  naming the extra lanes and why ([CI coverage](skills/cmux-testing/references/pr-ci-coverage.md)).\n- Keep branches current locally with `scripts/merge-main.sh`; follow\n  [the merge-main guide](docs/ci/merge-main.md) and never force-push over its merge.\n- `gh pr merge` saying \"base branch policy prohibits the merge\" means the token lacks the `workflow`\n  scope or GitHub timed out, not a rule: run `gh auth refresh -h github.com -s workflow`, or merge with\n  `gh api -X PUT repos/OWNER/REPO/pulls/N/merge -f merge_method=squash -f sha=SHA`, which names the cause. Never `--admin`.\n- A first implementation pass ends with passed scoped verification and an open PR;\n  do not watch CI or run speculative reviews by default.\n- Before opening a PR and before merging, check it against [REVIEW.md](REVIEW.md) (draft),\n  the mistakes our review history keeps catching.\n- Before merging, use a [review subagent](skills/cmux-review/SKILL.md), correctness\n  first; a second model is not a review gate. Disclose skipped verification on the PR.\n  `main` is nightly: fix forward, do not revert.\n- A PR merges when an independent review subagent passes it and it causes no red of its own;\n  base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky\n  user-visible behavior behind a setting or Debug toggle and fix a bad default in the next\n  nightly. Merge with `gh-merge-green`; [merge freezes](docs/ci/merge-freeze.md) still hold.\n  `gh-merge-green` still waits for the checks it requires; never get around it with\n  `--override` or the API merge path.\n  Follow [dogfood and merge receipts](skills/cmux-review/SKILL.md#dogfood-and-merge).\n  Notify with `cmux notify` when a socket is available.\n- A red base (`main` doesn't compile, or CI is red on every PR) is priority zero. Fix it\n  directly in its own PR; don't note it and leave it for an owner.\n\n## Implementation rules by task\n\nUse these existing owners instead of duplicating their checklists here:\n\n| Touching | Read before editing |\n| --- | --- |\n| Typing paths, SwiftUI list/store boundaries, rendering, find layering, UTTypes or OS-specific bugs | [cmux-debugging](skills/cmux-debugging/SKILL.md) |\n| Packages, workspace groups, lockfiles or feature flags | [cmux-architecture](skills/cmux-architecture/SKILL.md) |\n| Submodules or GhosttyKit | [cmux-ghostty](skills/cmux-ghostty/SKILL.md) |\n| User-facing strings, docs or help | [cmux-localization](skills/cmux-localization/SKILL.md); report the localization audit |\n| New cmux shortcuts | [cmux-keyboard-shortcuts](skills/cmux-keyboard-shortcuts/SKILL.md) |\n| Tests or target wiring | [cmux-testing](skills/cmux-testing/SKILL.md); run `scripts/sync-test-wiring` after adding, renaming or deleting a `cmuxTests/` file |\n| Multiple entrypoints or a bug that tests previously missed | [cmux-shared-behavior](skills/cmux-shared-behavior/SKILL.md); share action/mutation paths, verify every entrypoint, and cover the missed repro |\n\n## Remote CLI relay\n\nFor v2 socket methods and remote CLI changes, read [relay authorization](skills/cmux-socket-policy/references/remote-relay-authorization.md).\n`RemoteRelayCommandPolicy` defaults to deny. Allowlist only for a needed remote\nflow, scoped to the session's objects; command-bearing params stay denied on\nevery method. The PR must analyze local command/content\nexecution, access to unowned objects and local-state exposure, and include the\nrequired policy tests and ID scoping. Unsafe local effects must be redesigned.\nNever allowlist terminal spawn/respawn without live verification that it executes\non the remote host. An allowlist addition without this analysis blocks review.\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/manaflow-ai/cmux/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}