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 #7046] fix(capture): run without a PTY where the native preload cannot fork #7604

New issue
Open
opened 2026-11-03 13:39:03 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:39:03 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7046
Author: @innotelinc
Created: 10/24/2026
Status: 🔄 Open

Base: main ← Head: fix/capture-no-pty-musl

📝 Commits (3)

  • fa3117f fix(capture): run without a PTY where the native preload cannot fork
  • 84c239d test(capture): prove the pipe backend never imports node-pty on musl
  • 935d82b fix(capture): own the pipe child, its stdin errors, and cancellation

📊 Changes

6 files changed (+556 additions, -8 deletions)

View changed files

📝 src/process/capture/ProcessCaptureCapability.ts (+11 -0)
📝 src/process/capture/ProcessCaptureLifecycle.ts (+17 -0)
📝 src/process/capture/ProcessHarness.ts (+23 -8)
➕ src/process/capture/ProcessTerminalBackend.test.ts (+222 -0)
➕ src/process/capture/ProcessTerminalBackend.ts (+239 -0)
➕ src/process/capture/ProcessTerminalCancellation.test.ts (+44 -0)

📄 Description

Summary

A captured command crashes the MCP server on a musl host. @lydell/node-pty's
Linux prebuild is linked against glibc; under Alpine a gcompat shim lets the
addon load, and then forkpty faults the process that called it — which is
rea --mcp itself, so one capture_process_scenario took the server down and
every tool after it failed.

This picks the terminal backend before the native module is imported: node-pty
where the runtime reports glibc, ordinary pipes where it does not. A capture on
a musl host now completes, and the result says the terminal was not observed
instead of claiming one.

Problem and expected behavior

Smallest trigger, on Alpine (musl), with rea --mcp serving tools:

  1. tools/call → capture_process_scenario with a minimal command.
  2. The server process dies with SIGSEGV, leaving a core dump; the MCP client
    reports MCP server "rea" exited (SIGSEGV).

Invariant violated: observing a target must not kill the observer. Pipe capture
still records output, exit, process samples and filesystem effects; what it
cannot observe is a TTY, which the evidence now reports as a limitation and a
terminal unknown.

Change and scope

  • src/process/capture/ProcessTerminalBackend.ts (new): backend choice
    (nativePtyUsable() reads process.report's glibcVersionRuntime, Linux
    only), a PipeTerminal implementing the subset of IPty the harness uses
    (data, exit, write, resize, kill, pause/resume, flow control), and
    spawnProcessTerminal() which imports node-pty only on the native path.
  • ProcessHarness.ts: spawns through spawnProcessTerminal() and records the
    backend it got.
  • ProcessCaptureLifecycle.ts / ProcessCaptureCapability.ts: carry the
    backend and the "terminal not observed" limitation into the capture result.
  • ProcessTerminalBackend.test.ts: pipe output/exit, scripted stdin, signal
    reporting, backend choice on a report with no glibc, and a guard that the
    native module is never imported on that path.

Not included: a PTY emulation for musl (a pure-JS terminal would still not be a
kernel TTY), and any change to the node-pty path on glibc/macOS/Windows, which
is unchanged.

Contract and boundary impact

  • Semantic owner and earliest changed stage: process capture adapter; the
    spawn stage inside ProcessHarness.
  • Contribution scope fit and linked maintainer decision: ordinary fix inside
    existing capture boundaries; not applicable.
  • CLI and MCP/tool-catalog contract: no new tools and no argument changes.
    capture_process_scenario output gains the limitation and a terminal unknown
    on hosts without a usable PTY.
  • Provider, bridge, target-format, or platform compatibility: adds musl Linux
    support where the capture previously crashed. glibc Linux, macOS and Windows
    keep the node-pty backend.
  • Evidence, artifact, provenance, or reconstruction contract: the capture
    records which backend ran and marks the terminal as not observed rather than
    inferring one.
  • Target selection, authority, upstream behavior, and cleanup details:
    unchanged; the captured command runs with the same cwd, environment and
    arguments, and is killed the same way.
  • Generated metadata (docs/public/product-catalog.json), package, or
    installation impact: none; no generated catalogs change.

Expected effects (known effects):

  • Launch or attach to a process.
  • Read existing files or captured data.
  • 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.

Evidence and regression coverage

  • Tests added or updated: ProcessTerminalBackend.test.ts — five tests,
    including "runs on pipes where the runtime reports no glibc, without
    importing node-pty", which makes @lydell/node-pty unimportable and runs a
    command through the default backend with a report that carries no glibc.

  • Base reproduction or other evidence: on Alpine, rea --mcp died with
    SIGSEGV on the first capture_process_scenario call, leaving core.<pid> in
    the server's working directory; the same call under the pipe backend returns
    output and exit status. Reverting the backend choice to unconditional makes
    the new test fail (observed).

  • User-visible CLI/MCP output (if applicable): the capture result reports the
    backend and a terminal unknown instead of terminal observations.

  • Remaining proof gaps: the full npm run typecheck could not be completed on
    the 2 GB machine used for this work (the compiler is OOM-killed); a scoped
    tsc over the changed files reported no errors in them. No real Hopper,
    Ghidra, browser or OS coverage was run — the change is in process spawning.

  • 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

  • npx vitest run src/process/capture/ProcessTerminalBackend.test.ts — 5 tests
    passed.
  • npx vitest run src/process/capture — 18 files, 189 passed, 11 skipped.
  • Regression check with nativePtyUsable() forced to true — 2 tests failed,
    as intended; source restored.
  • npm run typecheck — not completed: the process was OOM-killed on a 2 GB host.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. A musl host that previously
    crashed now runs with pipes and says the terminal was not observed; callers
    that require terminal observations see the limitation rather than a silent
    change.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable to a spawn-path
    change; not run.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the pipe backend spawns
    with the same arguments, cwd and environment through node:child_process, and
    keeps the existing kill and flow-control behavior. No new privileges or
    network paths.

Author readiness

Human owner: @innotelinc

  • 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/7046 **Author:** [@innotelinc](https://github.com/innotelinc) **Created:** 10/24/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/capture-no-pty-musl` --- ### 📝 Commits (3) - [`fa3117f`](https://github.com/morluto/rea/commit/fa3117fb270983c50d410b3a5bb1018f7f172bca) fix(capture): run without a PTY where the native preload cannot fork - [`84c239d`](https://github.com/morluto/rea/commit/84c239d3f66cbed929e2ace50666e331e49adf28) test(capture): prove the pipe backend never imports node-pty on musl - [`935d82b`](https://github.com/morluto/rea/commit/935d82b3653bc06c403107f3d4b5d732386782ed) fix(capture): own the pipe child, its stdin errors, and cancellation ### 📊 Changes **6 files changed** (+556 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `src/process/capture/ProcessCaptureCapability.ts` (+11 -0) 📝 `src/process/capture/ProcessCaptureLifecycle.ts` (+17 -0) 📝 `src/process/capture/ProcessHarness.ts` (+23 -8) ➕ `src/process/capture/ProcessTerminalBackend.test.ts` (+222 -0) ➕ `src/process/capture/ProcessTerminalBackend.ts` (+239 -0) ➕ `src/process/capture/ProcessTerminalCancellation.test.ts` (+44 -0) </details> ### 📄 Description ## Summary A captured command crashes the MCP server on a musl host. `@lydell/node-pty`'s Linux prebuild is linked against glibc; under Alpine a gcompat shim lets the addon load, and then `forkpty` faults the process that called it — which is `rea --mcp` itself, so one `capture_process_scenario` took the server down and every tool after it failed. This picks the terminal backend before the native module is imported: node-pty where the runtime reports glibc, ordinary pipes where it does not. A capture on a musl host now completes, and the result says the terminal was not observed instead of claiming one. ## Problem and expected behavior Smallest trigger, on Alpine (musl), with `rea --mcp` serving tools: 1. `tools/call` → `capture_process_scenario` with a minimal command. 2. The server process dies with SIGSEGV, leaving a core dump; the MCP client reports `MCP server "rea" exited (SIGSEGV)`. Invariant violated: observing a target must not kill the observer. Pipe capture still records output, exit, process samples and filesystem effects; what it cannot observe is a TTY, which the evidence now reports as a limitation and a terminal unknown. ## Change and scope - `src/process/capture/ProcessTerminalBackend.ts` (new): backend choice (`nativePtyUsable()` reads `process.report`'s `glibcVersionRuntime`, Linux only), a `PipeTerminal` implementing the subset of `IPty` the harness uses (data, exit, write, resize, kill, pause/resume, flow control), and `spawnProcessTerminal()` which imports node-pty only on the native path. - `ProcessHarness.ts`: spawns through `spawnProcessTerminal()` and records the backend it got. - `ProcessCaptureLifecycle.ts` / `ProcessCaptureCapability.ts`: carry the backend and the "terminal not observed" limitation into the capture result. - `ProcessTerminalBackend.test.ts`: pipe output/exit, scripted stdin, signal reporting, backend choice on a report with no glibc, and a guard that the native module is never imported on that path. Not included: a PTY emulation for musl (a pure-JS terminal would still not be a kernel TTY), and any change to the node-pty path on glibc/macOS/Windows, which is unchanged. ## Contract and boundary impact - Semantic owner and earliest changed stage: process capture adapter; the spawn stage inside `ProcessHarness`. - Contribution scope fit and linked maintainer decision: ordinary fix inside existing capture boundaries; not applicable. - CLI and MCP/tool-catalog contract: no new tools and no argument changes. `capture_process_scenario` output gains the limitation and a terminal unknown on hosts without a usable PTY. - Provider, bridge, target-format, or platform compatibility: adds musl Linux support where the capture previously crashed. glibc Linux, macOS and Windows keep the node-pty backend. - Evidence, artifact, provenance, or reconstruction contract: the capture records which backend ran and marks the terminal as not observed rather than inferring one. - Target selection, authority, upstream behavior, and cleanup details: unchanged; the captured command runs with the same cwd, environment and arguments, and is killed the same way. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none; no generated catalogs change. Expected effects (known effects): - [x] Launch or attach to a process. - [ ] Read existing files or captured data. - [ ] 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. ## Evidence and regression coverage - Tests added or updated: `ProcessTerminalBackend.test.ts` — five tests, including "runs on pipes where the runtime reports no glibc, without importing node-pty", which makes `@lydell/node-pty` unimportable and runs a command through the default backend with a report that carries no glibc. - Base reproduction or other evidence: on Alpine, `rea --mcp` died with SIGSEGV on the first `capture_process_scenario` call, leaving `core.<pid>` in the server's working directory; the same call under the pipe backend returns output and exit status. Reverting the backend choice to unconditional makes the new test fail (observed). - User-visible CLI/MCP output (if applicable): the capture result reports the backend and a terminal unknown instead of terminal observations. - Remaining proof gaps: the full `npm run typecheck` could not be completed on the 2 GB machine used for this work (the compiler is OOM-killed); a scoped `tsc` over the changed files reported no errors in them. No real Hopper, Ghidra, browser or OS coverage was run — the change is in process spawning. - [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 - `npx vitest run src/process/capture/ProcessTerminalBackend.test.ts` — 5 tests passed. - `npx vitest run src/process/capture` — 18 files, 189 passed, 11 skipped. - Regression check with `nativePtyUsable()` forced to `true` — 2 tests failed, as intended; source restored. - `npm run typecheck` — not completed: the process was OOM-killed on a 2 GB host. ## Compatibility, safety, and release - Breaking changes or migration steps: none. A musl host that previously crashed now runs with pipes and says the terminal was not observed; callers that require terminal observations see the limitation rather than a silent change. - Real Hopper/Ghidra, browser, or OS coverage: not applicable to a spawn-path change; not run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the pipe backend spawns with the same arguments, cwd and environment through `node:child_process`, and keeps the existing kill and flow-control behavior. No new privileges or network paths. ## Author readiness Human owner: @innotelinc - [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#7604
No description provided.