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 #4519] fix(browser): keep Termux Chromium profiles on a writable temp directory #6281

New issue
Open
opened 2026-10-31 01:13:16 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:13:16 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4519
Author: @JoaoPHS
Created: 10/16/2026
Status: 🔄 Open

Base: main ← Head: fix/termux-chromium-temp

📝 Commits (10+)

  • 2a3514e fix(browser): keep Termux Chromium profiles on a writable temp directory
  • cb6761b fix(browser): place Playwright's Termux artifact directory on the writable temp path
  • 8000377 merge: resolve conflicts with main
  • 88a97ce fix(browser): keep overlapping Termux launches on their own temp directories
  • 701ecb3 fix(browser): keep the launched browser type outside the temp-directory callback
  • bb32ec5 fix(browser): isolate Termux temp lookups so a stuck launch cannot block the next
  • 63a5ee9 fix(browser): let Playwright load on Termux before Chromium starts
  • cfac433 fix(browser): keep a selected Android browser unless it is Termux Chromium
  • de00779 merge: resolve conflicts with main
  • 67fcb13 test(browser): give the Termux Android launch test a writable PREFIX

📊 Changes

10 files changed (+670 additions, -63 deletions)

View changed files

📝 src/browser/PlaywrightScenarioBrowser.test.ts (+472 -7)
📝 src/browser/PlaywrightScenarioBrowser.ts (+180 -40)
📝 src/native/AppleDispatchCoverage.ts (+4 -2)
📝 src/native/android/AndroidJniLibrary.ts (+1 -1)
📝 src/setupEnvironment.test.ts (+5 -5)
📝 tests/boundary/android/androidJniLibraries.test.ts (+1 -1)
📝 tests/boundary/filesystem/clientConfigurationDialects.test.ts (+4 -2)
📝 tests/boundary/filesystem/setupLauncherAlias.test.ts (+1 -1)
📝 tests/support/analysis-efficiency/android-jni.mjs (+1 -2)
📝 tests/support/analysis-efficiency/packet-entry.mjs (+1 -2)

📄 Description

Summary

Termux Chromium scenario launches created the browser profile under Node's default temp directory. On Android that is /tmp, which the Termux app user cannot write, and Chromium also tried to use /dev/shm, which Android does not provide. The profile and Playwright's host playwright-artifacts-* directory now stay on a writable temp directory, and shared-memory files are disabled.

Problem and expected behavior

On process.platform === "android", os.tmpdir() is /tmp when TMPDIR, TMP, and TEMP are unset. /tmp is owned by the Android shell user, so the Termux app cannot mkdtemp a Chromium profile there. Android also has no usable /dev/shm, so Chromium's default shared-memory path fails the launch.

A caller-selected temp directory must still win: TMPDIR, then TMP, then TEMP. Empty values are absent. When none is set, the writable location is $PREFIX/tmp. Playwright 1.58.2 also creates playwright-artifacts-* with the host os.tmpdir() after an await, before Chromium starts. That lookup is process-wide, so two overlapping launches must not share one directory, and one launch that never finishes must not block the next.

Change and scope

openPlaywrightScenarioBrowser creates the profile under the caller temp directory, or $PREFIX/tmp when that is the only writable default. The Chromium child receives that directory as TMPDIR when the caller did not select one. The host process does not rewrite TMPDIR, TMP, or TEMP. Playwright's os.tmpdir() call is scoped to the launch that is creating the artifact directory, so two Android launches can use different directories at the same time. Before Playwright is imported, a launch on Android publishes PLAYWRIGHT_BROWSERS_PATH under that writable directory so the 1.58.2 registry can load. If the caller selected Termux's $PREFIX/bin/chromium-browser wrapper and $PREFIX/lib/chromium/chrome exists, that binary is launched instead so Chromium can see icudtl.dat. Android launch args are --no-sandbox, --disable-dev-shm-usage, and --single-process. Existing Termux LD_PRELOAD / TERMUX_EXEC__PROC_SELF_EXE behavior is unchanged.

Follow the contribution scope.
This is an ordinary fix inside the existing browser scenario launcher. No new provider, target execution, injection, mutation, or protection-recovery capability. Maintainer scope decision: not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Playwright scenario browser launch owns the profile directory and Chromium environment. The change is at profile creation and the host temp lookup, before the browser process starts.
  • Contribution scope fit and linked maintainer decision: ordinary fix within the existing browser launcher. Not applicable.
  • CLI and MCP/tool-catalog contract: none. Scenario tool inputs and result shapes are unchanged.
  • Provider, bridge, target-format, or platform compatibility: Android/Termux Chromium launch only. Other platforms keep the previous profile parent (os.tmpdir()) and do not gain the Android args.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): the profile directory is still removed with the existing cleanup owner. A caller-selected TMPDIR is preserved. $PREFIX/tmp is created only when it is the fallback parent.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): none.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

The checked launch effect is the existing scenario Chromium process. This change only chooses its profile directory and the Android Chromium flags already used elsewhere.

Evidence and regression coverage

  • Tests added or updated: src/browser/PlaywrightScenarioBrowser.test.ts covers $PREFIX/tmp, caller-selected TMPDIR, TMP, TEMP, empty values, and TMPDIR precedence. It expects --disable-dev-shm-usage alongside the existing Termux args and environment. One case calls the production Playwright launcher and expects playwright-artifacts-* under the Termux temp directory. Overlapping launches each get an artifact directory in their own prefix. A launch that stays inside launchPersistentContext does not block a later launch, and each launch still sees its own temp directory. An Android launch with an empty PLAYWRIGHT_BROWSERS_PATH publishes $PREFIX/tmp/ms-playwright. A Termux wrapper at $PREFIX/bin/chromium-browser is rewritten to $PREFIX/lib/chromium/chrome when that file exists. These cases set process.platform to android. They do not boot Android.
  • Base reproduction or other evidence: Node documents os.tmpdir() as /tmp when the temp variables are unset, and Android's /tmp is the shell temp directory. The device section below records what happened when the production launch function ran under Termux on an emulator.
  • User-visible CLI/MCP output (if applicable): none. Failure before this change is the existing browser launch error when profile creation or Chromium startup fails.
  • Remaining proof gaps: see the device section. A page was not loaded.

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.

Device run

Observed on 2026-10-20. The bundled production function is openPlaywrightScenarioBrowser from commit 63a5ee998.

Host and image:

  • AVD Pixel_7_API_35, adb device emulator-5554, ro.build.version.release 15, ABI x86_64, product sdk_phone64_x86_64. This image has no Play Store. adb root was used to install and run Termux.
  • Termux v0.118.3 github-debug x86_64 (com.termux).
  • After apt-get upgrade with the maintainer config kept: Node v26.4.0, process.platform android. Chromium 155.0.8059.79 from the Termux x11 repository, command $PREFIX/bin/chromium-browser.

The scenario was headless, with start_url https://example.com, PREFIX=/data/data/com.termux/files/usr, and TMPDIR, TMP, and TEMP unset.

  1. Before this commit, import("playwright-core") from playwright-core@1.58.2 threw Unsupported platform: android at lib/server/registry/index.js:486. Chromium was not started.
  2. After this commit, with TMPDIR, TMP, TEMP, and PLAYWRIGHT_BROWSERS_PATH unset, the same function published PLAYWRIGHT_BROWSERS_PATH=/data/data/com.termux/files/usr/tmp/ms-playwright and imported Playwright. It launched $PREFIX/lib/chromium/chrome with --user-data-dir=/data/data/com.termux/files/usr/tmp/rea-browser-scenario-zx3dv8 and --no-sandbox, --disable-dev-shm-usage, --single-process. Chromium still logged Invalid file descriptor to ICU data received. and exited with SIGTRAP. No page title was read. The failed launch removed the profile. /tmp remained empty.

chromium-browser --version printed Chromium 155.0.8059.79 before the scenario launch.

Validation performed

  • npm run test:focused -- src/browser/PlaywrightScenarioBrowser.test.ts — passed, 28 tests, on Windows (Node from this checkout). The Android cases stub process.platform. The host-artifact case executes Playwright's directory allocation on Windows. It does not start Chromium on Android.
  • Device commands above, on the Pixel 7 API 35 emulator. The production function was the bundled openPlaywrightScenarioBrowser from this commit. PLAYWRIGHT_BROWSERS_PATH was not set by the caller.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Callers that set TMPDIR, TMP, or TEMP keep that directory. Callers that set none on Android move from /tmp to $PREFIX/tmp.
  • Real Hopper/Ghidra, browser, or OS coverage: one headless Chromium process was spawned on the emulator described above and exited during startup. A document was not loaded.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the profile remains mode 0700 and is still removed by the existing cleanup owner. No new network, injection, or target-mutation authority.

Author readiness

Human owner: @JoaoPHS

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • 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/4519 **Author:** [@JoaoPHS](https://github.com/JoaoPHS) **Created:** 10/16/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/termux-chromium-temp` --- ### 📝 Commits (10+) - [`2a3514e`](https://github.com/morluto/rea/commit/2a3514ea4c54f75bedb93b71606fec8aeac2f58e) fix(browser): keep Termux Chromium profiles on a writable temp directory - [`cb6761b`](https://github.com/morluto/rea/commit/cb6761b1319c78f7bc7f4fbe88654171f662aabe) fix(browser): place Playwright's Termux artifact directory on the writable temp path - [`8000377`](https://github.com/morluto/rea/commit/80003772de39fa5a12e4409b4f451c522a610922) merge: resolve conflicts with main - [`88a97ce`](https://github.com/morluto/rea/commit/88a97cebffed3b1eb3a99deabca08491d0e29de5) fix(browser): keep overlapping Termux launches on their own temp directories - [`701ecb3`](https://github.com/morluto/rea/commit/701ecb318747825e10cf4ccfba4c3f3e8de7dcaf) fix(browser): keep the launched browser type outside the temp-directory callback - [`bb32ec5`](https://github.com/morluto/rea/commit/bb32ec5fed8f4d080667a64e5124ea4faa48de88) fix(browser): isolate Termux temp lookups so a stuck launch cannot block the next - [`63a5ee9`](https://github.com/morluto/rea/commit/63a5ee998a19181a092c23742428664642d2ab72) fix(browser): let Playwright load on Termux before Chromium starts - [`cfac433`](https://github.com/morluto/rea/commit/cfac4333cdee2287b24a3a1c9be769f370945a04) fix(browser): keep a selected Android browser unless it is Termux Chromium - [`de00779`](https://github.com/morluto/rea/commit/de00779422af46590348939cbc6677c914bf7c4e) merge: resolve conflicts with main - [`67fcb13`](https://github.com/morluto/rea/commit/67fcb13d26dd1da046d63bea43e26a3486b97f30) test(browser): give the Termux Android launch test a writable PREFIX ### 📊 Changes **10 files changed** (+670 additions, -63 deletions) <details> <summary>View changed files</summary> 📝 `src/browser/PlaywrightScenarioBrowser.test.ts` (+472 -7) 📝 `src/browser/PlaywrightScenarioBrowser.ts` (+180 -40) 📝 `src/native/AppleDispatchCoverage.ts` (+4 -2) 📝 `src/native/android/AndroidJniLibrary.ts` (+1 -1) 📝 `src/setupEnvironment.test.ts` (+5 -5) 📝 `tests/boundary/android/androidJniLibraries.test.ts` (+1 -1) 📝 `tests/boundary/filesystem/clientConfigurationDialects.test.ts` (+4 -2) 📝 `tests/boundary/filesystem/setupLauncherAlias.test.ts` (+1 -1) 📝 `tests/support/analysis-efficiency/android-jni.mjs` (+1 -2) 📝 `tests/support/analysis-efficiency/packet-entry.mjs` (+1 -2) </details> ### 📄 Description ## Summary Termux Chromium scenario launches created the browser profile under Node's default temp directory. On Android that is `/tmp`, which the Termux app user cannot write, and Chromium also tried to use `/dev/shm`, which Android does not provide. The profile and Playwright's host `playwright-artifacts-*` directory now stay on a writable temp directory, and shared-memory files are disabled. ## Problem and expected behavior On `process.platform === "android"`, `os.tmpdir()` is `/tmp` when `TMPDIR`, `TMP`, and `TEMP` are unset. `/tmp` is owned by the Android shell user, so the Termux app cannot `mkdtemp` a Chromium profile there. Android also has no usable `/dev/shm`, so Chromium's default shared-memory path fails the launch. A caller-selected temp directory must still win: `TMPDIR`, then `TMP`, then `TEMP`. Empty values are absent. When none is set, the writable location is `$PREFIX/tmp`. Playwright 1.58.2 also creates `playwright-artifacts-*` with the host `os.tmpdir()` after an await, before Chromium starts. That lookup is process-wide, so two overlapping launches must not share one directory, and one launch that never finishes must not block the next. ## Change and scope `openPlaywrightScenarioBrowser` creates the profile under the caller temp directory, or `$PREFIX/tmp` when that is the only writable default. The Chromium child receives that directory as `TMPDIR` when the caller did not select one. The host process does not rewrite `TMPDIR`, `TMP`, or `TEMP`. Playwright's `os.tmpdir()` call is scoped to the launch that is creating the artifact directory, so two Android launches can use different directories at the same time. Before Playwright is imported, a launch on Android publishes `PLAYWRIGHT_BROWSERS_PATH` under that writable directory so the 1.58.2 registry can load. If the caller selected Termux's `$PREFIX/bin/chromium-browser` wrapper and `$PREFIX/lib/chromium/chrome` exists, that binary is launched instead so Chromium can see `icudtl.dat`. Android launch args are `--no-sandbox`, `--disable-dev-shm-usage`, and `--single-process`. Existing Termux `LD_PRELOAD` / `TERMUX_EXEC__PROC_SELF_EXE` behavior is unchanged. Follow the contribution scope. This is an ordinary fix inside the existing browser scenario launcher. No new provider, target execution, injection, mutation, or protection-recovery capability. Maintainer scope decision: not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: Playwright scenario browser launch owns the profile directory and Chromium environment. The change is at profile creation and the host temp lookup, before the browser process starts. - Contribution scope fit and linked maintainer decision: ordinary fix within the existing browser launcher. Not applicable. - CLI and MCP/tool-catalog contract: none. Scenario tool inputs and result shapes are unchanged. - Provider, bridge, target-format, or platform compatibility: Android/Termux Chromium launch only. Other platforms keep the previous profile parent (`os.tmpdir()`) and do not gain the Android args. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): the profile directory is still removed with the existing cleanup owner. A caller-selected `TMPDIR` is preserved. `$PREFIX/tmp` is created only when it is the fallback parent. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. The checked launch effect is the existing scenario Chromium process. This change only chooses its profile directory and the Android Chromium flags already used elsewhere. ## Evidence and regression coverage - Tests added or updated: `src/browser/PlaywrightScenarioBrowser.test.ts` covers `$PREFIX/tmp`, caller-selected `TMPDIR`, `TMP`, `TEMP`, empty values, and `TMPDIR` precedence. It expects `--disable-dev-shm-usage` alongside the existing Termux args and environment. One case calls the production Playwright launcher and expects `playwright-artifacts-*` under the Termux temp directory. Overlapping launches each get an artifact directory in their own prefix. A launch that stays inside `launchPersistentContext` does not block a later launch, and each launch still sees its own temp directory. An Android launch with an empty `PLAYWRIGHT_BROWSERS_PATH` publishes `$PREFIX/tmp/ms-playwright`. A Termux wrapper at `$PREFIX/bin/chromium-browser` is rewritten to `$PREFIX/lib/chromium/chrome` when that file exists. These cases set `process.platform` to `android`. They do not boot Android. - Base reproduction or other evidence: Node documents `os.tmpdir()` as `/tmp` when the temp variables are unset, and Android's `/tmp` is the shell temp directory. The device section below records what happened when the production launch function ran under Termux on an emulator. - User-visible CLI/MCP output (if applicable): none. Failure before this change is the existing browser launch error when profile creation or Chromium startup fails. - Remaining proof gaps: see the device section. A page was not loaded. 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. ## Device run Observed on 2026-10-20. The bundled production function is `openPlaywrightScenarioBrowser` from commit `63a5ee998`. Host and image: - AVD `Pixel_7_API_35`, `adb` device `emulator-5554`, `ro.build.version.release` `15`, ABI `x86_64`, product `sdk_phone64_x86_64`. This image has no Play Store. `adb root` was used to install and run Termux. - Termux `v0.118.3` github-debug `x86_64` (`com.termux`). - After `apt-get upgrade` with the maintainer config kept: Node `v26.4.0`, `process.platform` `android`. Chromium `155.0.8059.79` from the Termux x11 repository, command `$PREFIX/bin/chromium-browser`. The scenario was headless, with `start_url` `https://example.com`, `PREFIX=/data/data/com.termux/files/usr`, and `TMPDIR`, `TMP`, and `TEMP` unset. 1. Before this commit, `import("playwright-core")` from `playwright-core@1.58.2` threw `Unsupported platform: android` at `lib/server/registry/index.js:486`. Chromium was not started. 2. After this commit, with `TMPDIR`, `TMP`, `TEMP`, and `PLAYWRIGHT_BROWSERS_PATH` unset, the same function published `PLAYWRIGHT_BROWSERS_PATH=/data/data/com.termux/files/usr/tmp/ms-playwright` and imported Playwright. It launched `$PREFIX/lib/chromium/chrome` with `--user-data-dir=/data/data/com.termux/files/usr/tmp/rea-browser-scenario-zx3dv8` and `--no-sandbox`, `--disable-dev-shm-usage`, `--single-process`. Chromium still logged `Invalid file descriptor to ICU data received.` and exited with `SIGTRAP`. No page title was read. The failed launch removed the profile. `/tmp` remained empty. `chromium-browser --version` printed `Chromium 155.0.8059.79` before the scenario launch. ## Validation performed - `npm run test:focused -- src/browser/PlaywrightScenarioBrowser.test.ts` — passed, 28 tests, on Windows (Node from this checkout). The Android cases stub `process.platform`. The host-artifact case executes Playwright's directory allocation on Windows. It does not start Chromium on Android. - Device commands above, on the Pixel 7 API 35 emulator. The production function was the bundled `openPlaywrightScenarioBrowser` from this commit. `PLAYWRIGHT_BROWSERS_PATH` was not set by the caller. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Callers that set `TMPDIR`, `TMP`, or `TEMP` keep that directory. Callers that set none on Android move from `/tmp` to `$PREFIX/tmp`. - Real Hopper/Ghidra, browser, or OS coverage: one headless Chromium process was spawned on the emulator described above and exited during startup. A document was not loaded. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the profile remains mode `0700` and is still removed by the existing cleanup owner. No new network, injection, or target-mutation authority. ## Author readiness Human owner: @JoaoPHS - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#6281
No description provided.