morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #1804] [CLOSED] feat(setup): register Kimi Code client with compact schema profile #4826

New issue
Closed
opened 2026-10-31 00:55:29 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 00:55:29 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1804
Author: @yadnuses
Created: 10/11/2026
Status: ❌ Closed

Base: main ← Head: feat/kimi-code-client

📝 Commits (10+)

  • 20abd98 feat(clients): register Kimi Code during setup
  • 6edbcda test(clients): cover Kimi Code registration lifecycle
  • ac955f5 docs(installation): document the Kimi Code client
  • 0e4636b docs(installation): cite Kimi Code /mcp-config scopes for .mcp.json
  • 7106326 Merge remote-tracking branch 'origin/main' into feat/kimi-code-client
  • 018a9da fix: reconcile latest main for PR #1804
  • 5f0a116 fix(clients): treat profile-less Kimi registrations as stale
  • 3c6fd0e fix(clients): honor Windows environment-key identity in Kimi profile policy
  • 37dbe80 fix(setup): reconcile Kimi client branch with current main
  • 667758c fix(setup): preserve newer Kimi environment identity changes

📊 Changes

17 files changed (+951 additions, -312 deletions)

View changed files

📝 docs/client-configuration.md (+27 -0)
📝 docs/installation.md (+6 -4)
📝 src/application/ClientConfigurationFiles.ts (+7 -1)
📝 src/application/ClientRegistrationEnvironment.ts (+33 -3)
📝 src/application/ClientRegistrationIdentity.ts (+9 -8)
📝 src/application/ClientRegistrationStatus.ts (+17 -0)
📝 src/application/SetupClientConfiguration.ts (+14 -0)
📝 src/application/SetupPlan.ts (+6 -2)
📝 src/application/SupportedClients.ts (+8 -0)
📝 src/cli/setupCommands.ts (+11 -4)
➕ src/config/environmentKey.ts (+20 -0)
📝 src/process/snapshotEnvironment.ts (+3 -1)
➕ tests/acceptance/setup/kimiClientSetup.test.ts (+98 -0)
📝 tests/boundary/filesystem/clientLifecycle.test.ts (+1 -0)
📝 tests/boundary/filesystem/kimiClientConfiguration.test.ts (+157 -289)
➕ tests/boundary/filesystem/kimiClientCurrentRegistration.test.ts (+384 -0)
➕ tests/boundary/filesystem/kimiClientEnvironmentIdentity.test.ts (+150 -0)

📄 Description

Summary

Kimi Code (kimi-cli, Moonshot's coding agent) is the one major local MCP client with no rea setup integration, so its users hand-write mcpServers.rea into ~/.kimi-code/mcp.json (the exact path #1484's reproduction uses). That leaves setup detection, doctor, and uninstall blind to the registration, rea update never re-pins it, and a naive entry reproduces the Moonshot per-schema 400s of #1484 on current releases. This PR registers Kimi Code as a supported client and seeds the compact schema presentation into its entry so the first prompt after setup works. Fixes #1791.

Problem and expected behavior

  • Use case: A Kimi Code user runs npx rea-agents setup and gets a Kimi Code checkbox the way OMP (#1257 → #1301) and Qwen Code (#1409) did, then loads both the MCP server and the reverse-engineer-anything workflow with no manual file edits.
  • Observable outcome: rea setup --client kimi_code writes a pinned mcpServers.rea entry to user-level ~/.kimi-code/mcp.json with "env": { "REA_MCP_INPUT_SCHEMA_PROFILE": "compact" }; doctor --client kimi_code reports the registration; uninstall --client kimi_code removes it. No #1484-style 400 cascade on the first prompt.

Change and scope

  • SupportedClients.ts — kimi_code definition (configPath mcp.json under the Kimi home, markerPath the same directory, format: "json"). The existing JSON dialect writes exactly the mcpServers.<name> → {command, args, env} shape Kimi Code loads; no new dialect.
  • Home resolution honors KIMI_CODE_HOME with codex-style semantics (non-empty override used as-is, empty falls back to ~/.kimi-code, no tilde expansion) — matched to Kimi's own resolution and pinned by tests.
  • ClientRegistrationEnvironment.ts — the existing environment-retention merge gains a lowest-precedence defaults layer ({...defaults, ...existing, ...overrides}), so seeded values never clobber explicitly configured ones (preserves the "explicitly configured server settings" invariant).
  • SetupClientConfiguration.ts — clientRegistrationDefaults(client) returns the compact profile seed for kimi_code (empty map otherwise) at the single clientConfigurationDesired convergence point, so register/inspect/aligned/update all seed it and stay idempotent.
  • SetupSkill.ts — unchanged: Kimi Code discovers the shared ~/.agents/skills, the existing fallback destination; no client skill family needed (simpler than #1409's Qwen case).
  • Tests + docs/installation.md (table row, Kimi Code section, restart note).
  • Intentionally not included: a verify:kimi-client script, project-level config writes, tool-contract changes, Windows Kimi verification.

Contract and boundary impact

  • Semantic owner and earliest changed stage: setup client registration (application layer: SetupClientConfiguration / ClientRegistrationEnvironment).
  • CLI and MCP/tool-catalog contract: none — REA_MCP_INPUT_SCHEMA_PROFILE is presentation-only advertising; canonical schemas and server-side validation are untouched (catalog still 170 tools).
  • Provider, bridge, target-format, or platform compatibility: none — no provider changes. Windows Kimi Code path behavior untested (same code shape as codex/qwen).
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Process execution, authorization, cleanup, or containment impact: setup writes only user-level client config through the existing reviewed plan/backup/atomic-replacement transaction; no process execution added.
  • Generated metadata, package, or installation impact: setup_clients client metadata derives from SUPPORTED_CLIENT_DEFINITIONS (CI-generated; nothing committed); npm pack --dry-run and verify:package pass; docs/installation.md updated.

Evidence and regression coverage

  • Tests added or updated: tests/boundary/filesystem/kimiClientConfiguration.test.ts (9 tests: path resolution on linux/darwin, KIMI_CODE_HOME semantics incl. empty/~//relative cases, register → preserve-unrelated → aligned-read → idempotent-reconfigure → uninstall round trip, compact seed + explicit full precedence + provider-key stacking); tests/acceptance/setup/kimiClientSetup.test.ts (CLI dry-run plan → --yes apply → .rea.backup → compact env → doctor --skill → idempotent re-run → uninstall, under KIMI_CODE_HOME); clientLifecycle.test.ts detection-order list; clientEnvironment.ts fixture.
  • Base reproduction or other evidence: on the base revision no kimi_code client exists in SUPPORTED_CLIENT_DEFINITIONS (setup multi-select and --client have no Kimi Code option); #1484 documents the schema-cap failure mode. Schema-size table in #1791 (2026-10-11, rea-agents@6.4.0): full profile 5 inputSchemas over ~14 KB (largest 61,876 B); compact profile 0 over (largest 12,090 B).
  • User-visible CLI/MCP output: dry-run plan lists the Kimi Code registration action; doctor --client kimi_code covers it like other clients; docs section shows the written entry shape.
  • Remaining proof gaps: no live Kimi Code session round trip against the MCP server (no verify:kimi-client lane here); Moonshot cap behavior measured previously, not re-triggered from this host; Windows unverified; full test:acceptance/test:integration and docs:build not run; dev toolchain is Node 24.14.0 vs .nvmrc 24.18.0 (nvm unavailable on the host).

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm ci — pass
  • npm run test:focused -- tests/boundary/filesystem/kimiClientConfiguration.test.ts tests/acceptance/setup/kimiClientSetup.test.ts (plus clientLifecycle, qwen, clientConfigurationEnvironment, productCatalog) — 6 files / 90 tests pass
  • npm run check:fast — pass (typecheck + lint incl. module boundaries)
  • npm run verify:test-discovery — pass (821 test files, each discovered once)
  • npm run verify:package — pass (setup planned→idempotent, backupReadback, skill, mcpTools=170)
  • npm pack --dry-run — pass (1162 files, no artifacts written)
  • npm run docs:check — pass
  • npm run test:fast — 4298 passed / 7 skipped
  • npm run test:boundary — 27 failed / 3039 passed; the failing set is identical on the main baseline of this host (missing ibtool, hdiutil behavior, Ghidra MCP fixture, JS inspector fixture); one additional 30 s timeout flake passes standalone 8/8. Unrelated to this change; no assertion weakened.
  • Real Hopper/Ghidra, browser, or OS coverage: not run — registration-only change; no provider lanes on this host.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Fresh kimi_code registrations seed the compact profile; explicitly configured REA_MCP_INPUT_SCHEMA_PROFILE values keep precedence over the seed. Existing manual entries are only touched if the user runs setup for kimi_code (standard reviewed transaction).
  • Real Hopper/Ghidra, browser, or OS coverage: unavailable on this host (see above).
  • Package or release metadata impact: adds one client to derived setup metadata; release via the usual Release Please flow.
  • Security, privacy, process, or containment review: writes one user-level config file via the existing backup/atomic transaction; no credentials, no new process execution; the env seed is a presentation hint, not a capability change.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked (Fixes #1791).
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/1804 **Author:** [@yadnuses](https://github.com/yadnuses) **Created:** 10/11/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feat/kimi-code-client` --- ### 📝 Commits (10+) - [`20abd98`](https://github.com/morluto/rea/commit/20abd989284817754bd3f64ebf037c6807f8afd5) feat(clients): register Kimi Code during setup - [`6edbcda`](https://github.com/morluto/rea/commit/6edbcda1fcfddf3fae1a9841a84b8a377bc911d7) test(clients): cover Kimi Code registration lifecycle - [`ac955f5`](https://github.com/morluto/rea/commit/ac955f58ff0afd77f2d6c8a77bc8015fec3abcca) docs(installation): document the Kimi Code client - [`0e4636b`](https://github.com/morluto/rea/commit/0e4636bb37928b05ef09c52458374b95dc337939) docs(installation): cite Kimi Code /mcp-config scopes for .mcp.json - [`7106326`](https://github.com/morluto/rea/commit/71063263de52ff4149994d4353212cd46ed8d804) Merge remote-tracking branch 'origin/main' into feat/kimi-code-client - [`018a9da`](https://github.com/morluto/rea/commit/018a9da6e4398b185ac223131c1b6561d7d8e53b) fix: reconcile latest main for PR #1804 - [`5f0a116`](https://github.com/morluto/rea/commit/5f0a11687a83639b0738a7586acd91546399f0e6) fix(clients): treat profile-less Kimi registrations as stale - [`3c6fd0e`](https://github.com/morluto/rea/commit/3c6fd0efa2e7378928fd84194dd2f869879eb193) fix(clients): honor Windows environment-key identity in Kimi profile policy - [`37dbe80`](https://github.com/morluto/rea/commit/37dbe80ef2c00daf13f71a067d1d6473e0275101) fix(setup): reconcile Kimi client branch with current main - [`667758c`](https://github.com/morluto/rea/commit/667758c201531472e364f74b3dc975387ca0f071) fix(setup): preserve newer Kimi environment identity changes ### 📊 Changes **17 files changed** (+951 additions, -312 deletions) <details> <summary>View changed files</summary> 📝 `docs/client-configuration.md` (+27 -0) 📝 `docs/installation.md` (+6 -4) 📝 `src/application/ClientConfigurationFiles.ts` (+7 -1) 📝 `src/application/ClientRegistrationEnvironment.ts` (+33 -3) 📝 `src/application/ClientRegistrationIdentity.ts` (+9 -8) 📝 `src/application/ClientRegistrationStatus.ts` (+17 -0) 📝 `src/application/SetupClientConfiguration.ts` (+14 -0) 📝 `src/application/SetupPlan.ts` (+6 -2) 📝 `src/application/SupportedClients.ts` (+8 -0) 📝 `src/cli/setupCommands.ts` (+11 -4) ➕ `src/config/environmentKey.ts` (+20 -0) 📝 `src/process/snapshotEnvironment.ts` (+3 -1) ➕ `tests/acceptance/setup/kimiClientSetup.test.ts` (+98 -0) 📝 `tests/boundary/filesystem/clientLifecycle.test.ts` (+1 -0) 📝 `tests/boundary/filesystem/kimiClientConfiguration.test.ts` (+157 -289) ➕ `tests/boundary/filesystem/kimiClientCurrentRegistration.test.ts` (+384 -0) ➕ `tests/boundary/filesystem/kimiClientEnvironmentIdentity.test.ts` (+150 -0) </details> ### 📄 Description <!-- PR title: type(optional-scope): imperative outcome --> <!-- Title: feat(setup): register Kimi Code client with compact schema profile --> ## Summary Kimi Code (kimi-cli, Moonshot's coding agent) is the one major local MCP client with no `rea setup` integration, so its users hand-write `mcpServers.rea` into `~/.kimi-code/mcp.json` (the exact path #1484's reproduction uses). That leaves setup detection, `doctor`, and `uninstall` blind to the registration, `rea update` never re-pins it, and a naive entry reproduces the Moonshot per-schema 400s of #1484 on current releases. This PR registers Kimi Code as a supported client and seeds the compact schema presentation into its entry so the first prompt after setup works. Fixes #1791. ## Problem and expected behavior - **Use case**: A Kimi Code user runs `npx rea-agents setup` and gets a Kimi Code checkbox the way OMP (#1257 → #1301) and Qwen Code (#1409) did, then loads both the MCP server and the `reverse-engineer-anything` workflow with no manual file edits. - **Observable outcome**: `rea setup --client kimi_code` writes a pinned `mcpServers.rea` entry to user-level `~/.kimi-code/mcp.json` with `"env": { "REA_MCP_INPUT_SCHEMA_PROFILE": "compact" }`; `doctor --client kimi_code` reports the registration; `uninstall --client kimi_code` removes it. No #1484-style 400 cascade on the first prompt. ## Change and scope - `SupportedClients.ts` — `kimi_code` definition (`configPath` `mcp.json` under the Kimi home, `markerPath` the same directory, `format: "json"`). The existing JSON dialect writes exactly the `mcpServers.<name>` → `{command, args, env}` shape Kimi Code loads; no new dialect. - Home resolution honors `KIMI_CODE_HOME` with codex-style semantics (non-empty override used as-is, empty falls back to `~/.kimi-code`, no tilde expansion) — matched to Kimi's own resolution and pinned by tests. - `ClientRegistrationEnvironment.ts` — the existing environment-retention merge gains a lowest-precedence `defaults` layer (`{...defaults, ...existing, ...overrides}`), so seeded values never clobber explicitly configured ones (preserves the "explicitly configured server settings" invariant). - `SetupClientConfiguration.ts` — `clientRegistrationDefaults(client)` returns the compact profile seed for `kimi_code` (empty map otherwise) at the single `clientConfigurationDesired` convergence point, so register/inspect/aligned/update all seed it and stay idempotent. - `SetupSkill.ts` — unchanged: Kimi Code discovers the shared `~/.agents/skills`, the existing fallback destination; no client skill family needed (simpler than #1409's Qwen case). - Tests + `docs/installation.md` (table row, Kimi Code section, restart note). - Intentionally not included: a `verify:kimi-client` script, project-level config writes, tool-contract changes, Windows Kimi verification. ## Contract and boundary impact - Semantic owner and earliest changed stage: setup client registration (application layer: `SetupClientConfiguration` / `ClientRegistrationEnvironment`). - CLI and MCP/tool-catalog contract: none — `REA_MCP_INPUT_SCHEMA_PROFILE` is presentation-only advertising; canonical schemas and server-side validation are untouched (catalog still 170 tools). - Provider, bridge, target-format, or platform compatibility: none — no provider changes. Windows Kimi Code path behavior untested (same code shape as codex/qwen). - Evidence, artifact, provenance, or reconstruction contract: none. - Process execution, authorization, cleanup, or containment impact: setup writes only user-level client config through the existing reviewed plan/backup/atomic-replacement transaction; no process execution added. - Generated metadata, package, or installation impact: `setup_clients` client metadata derives from `SUPPORTED_CLIENT_DEFINITIONS` (CI-generated; nothing committed); `npm pack --dry-run` and `verify:package` pass; `docs/installation.md` updated. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/filesystem/kimiClientConfiguration.test.ts` (9 tests: path resolution on linux/darwin, `KIMI_CODE_HOME` semantics incl. empty/`~/`/relative cases, register → preserve-unrelated → aligned-read → idempotent-reconfigure → uninstall round trip, compact seed + explicit `full` precedence + provider-key stacking); `tests/acceptance/setup/kimiClientSetup.test.ts` (CLI dry-run plan → `--yes` apply → `.rea.backup` → compact env → `doctor --skill` → idempotent re-run → uninstall, under `KIMI_CODE_HOME`); `clientLifecycle.test.ts` detection-order list; `clientEnvironment.ts` fixture. - Base reproduction or other evidence: on the base revision no `kimi_code` client exists in `SUPPORTED_CLIENT_DEFINITIONS` (setup multi-select and `--client` have no Kimi Code option); #1484 documents the schema-cap failure mode. Schema-size table in #1791 (2026-10-11, `rea-agents@6.4.0`): full profile 5 `inputSchema`s over ~14 KB (largest 61,876 B); compact profile 0 over (largest 12,090 B). - User-visible CLI/MCP output: dry-run plan lists the Kimi Code registration action; `doctor --client kimi_code` covers it like other clients; docs section shows the written entry shape. - Remaining proof gaps: no live Kimi Code session round trip against the MCP server (no `verify:kimi-client` lane here); Moonshot cap behavior measured previously, not re-triggered from this host; Windows unverified; full `test:acceptance`/`test:integration` and `docs:build` not run; dev toolchain is Node 24.14.0 vs `.nvmrc` 24.18.0 (nvm unavailable on the host). For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm ci` — pass - `npm run test:focused -- tests/boundary/filesystem/kimiClientConfiguration.test.ts tests/acceptance/setup/kimiClientSetup.test.ts` (plus clientLifecycle, qwen, clientConfigurationEnvironment, productCatalog) — 6 files / 90 tests pass - `npm run check:fast` — pass (typecheck + lint incl. module boundaries) - `npm run verify:test-discovery` — pass (821 test files, each discovered once) - `npm run verify:package` — pass (setup planned→idempotent, backupReadback, skill, mcpTools=170) - `npm pack --dry-run` — pass (1162 files, no artifacts written) - `npm run docs:check` — pass - `npm run test:fast` — 4298 passed / 7 skipped - `npm run test:boundary` — 27 failed / 3039 passed; the failing set is identical on the `main` baseline of this host (missing `ibtool`, `hdiutil` behavior, Ghidra MCP fixture, JS inspector fixture); one additional 30 s timeout flake passes standalone 8/8. Unrelated to this change; no assertion weakened. - Real Hopper/Ghidra, browser, or OS coverage: not run — registration-only change; no provider lanes on this host. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Fresh `kimi_code` registrations seed the compact profile; explicitly configured `REA_MCP_INPUT_SCHEMA_PROFILE` values keep precedence over the seed. Existing manual entries are only touched if the user runs setup for `kimi_code` (standard reviewed transaction). - Real Hopper/Ghidra, browser, or OS coverage: unavailable on this host (see above). - Package or release metadata impact: adds one client to derived setup metadata; release via the usual Release Please flow. - Security, privacy, process, or containment review: writes one user-level config file via the existing backup/atomic transaction; no credentials, no new process execution; the env seed is a presentation hint, not a capability change. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked (`Fixes #1791`). - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 00:55:29 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#4826
No description provided.