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 #4507] [MERGED] fix(cutter): read the active document from core configuration #6276

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4507
Author: @N0zoM1z0
Created: 10/16/2026
Status: ✅ Merged
Merged: 10/16/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/cutter-document-identity-4497

📝 Commits (1)

  • 93382aa fix(cutter): read the active document from core configuration

📊 Changes

2 files changed (+62 additions, -3 deletions)

View changed files

📝 bridge/cutter/rea_bridge.py (+2 -2)
📝 tests/fixtures/cutter_bridge_protocol_test.py (+60 -1)

📄 Description

Summary

Fixes #4497. Cutter discovery and command Evidence now report the active core's file path instead of null when an ELF is loaded. Document generation can consequently observe path changes and reject commands against an earlier generation.

Problem and expected behavior

The bridge calls currentlyOpenFile() and swallows the failure. That member is a string, and native probing plus Cutter source show it is a debugging backup rather than the ordinary current-file getter. The file loaded in the real GUI appears in getConfig("file.path") and ij.core.file while the backup member remains empty.

Change and scope

Read the existing scalar CutterCore.getConfig("file.path") at the producer boundary. Preserve the exact nonempty string; absent, malformed or unreadable values remain unknown. CLI/MCP consume the existing bridge facts without another interpretation. No cache: this is live document state, refreshed by the existing GUI-thread dispatcher.

Ordinary metadata correction within existing authority; no new provider, execution, injection, mutation or protection recovery. Separate scope approval is not applicable.

Contract and boundary impact

  • Semantic owner/earliest stage: Python dispatcher reads the current core configuration before status/command admission and after commands.
  • CLI/MCP/tool catalog: existing fields and schemas; current_file becomes populated when observed. Same instance UUID and generation protocol.
  • Provider/format/platform compatibility: official Linux Cutter 2.5.0 Qt5 verified; other hosts unverified. Missing API/value remains unknown.
  • Evidence/provenance: current path and observed generation propagate through the existing command Evidence; identity remains partial, including the documented same-path reload/tab limitation.
  • Authority/cleanup: scalar configuration read only; no document changes, GUI closure or new process ownership. Existing command authority is unchanged.
  • Generated/package/install impact: none; no artifacts or binaries committed.

Expected effects:

  • 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 existing bridge exchanges remain authenticated loopback requests. Verification launches a fixture-owned GUI; the change does not launch one.

Evidence and regression coverage

  • The production-boundary Python regression fails against an immutable snapshot of clean main a6c6a76d37c729e17cccf2dd20fe8e8177d98b14: a known configured path is returned as None. It passes with the corrected owner API. Tests cover exact Unicode/#? paths, initialization/status, unchanged/changed generations, stale-command rejection before dispatch, valid dispatch, and unknown/malformed/unreadable configuration.

  • Actual official Cutter Qt5 on clean main and final head: two CLI/three stdio MCP calls on a controlled ELF with a Unicode/#? filename. Base discovery returns null although ij identifies the loaded ELF; final CLI/MCP discovery and both Evidence observations preserve the exact path. The ELF bytes stay unchanged, MCP disconnect preserves Cutter, and fixture-owned cleanup leaves verified empty process lineage.

  • Real GUI document switching and same-path reload identity were not tested; the generation-transition test runs the actual Python producer against a controlled host configuration. Host-version provenance remains separately tracked in #4498. Qt6 plugin loading remains upstream rizinorg/cutter#3659.

  • 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

Final source 93382aa6869e092d8e6c14e75ac10f4c29e1b98e, based on latest main a6c6a76d37c729e17cccf2dd20fe8e8177d98b14:

  • python3 tests/fixtures/cutter_bridge_protocol_test.py — 11 passed; final regression on the immutable base fails as expected.
  • npm run test:focused -- 10 relevant Cutter CLI/MCP/provider and mutation-config/workflow files — 66 passed, including the Python producer boundary.
  • npm run check:ci and npm run docs:check — passed.
  • Actual official Cutter 2.5.0 Qt5 public CLI/stdio MCP workflow — passed on final committed source, without the separate diagnostic plugin.

One completed healthy native task/revision, two CPU cores: base → fix wall 9.00 → 9.60 s, CPU 10.88 → 12.02 s, sampled family peak 1.059 → 1.011 GiB. Shared host and uncontrolled caches/load: these single observations establish neither speedup nor a stable performance regression. Fresh GUI/profile, CLI and MCP processes were used; cold OS cache was not established. Per-call first/subsequent timings are retained locally.

Whole wire+CLI o200k_base serialization proxy 835,254 → 835,472, including identical 829,341-token full catalogs. Named two-tool definitions+calls+CLI proxy 8,561 → 8,779. Existing provenance fields now carry paths; no extra calls or fields are added. These are serialization estimates, not model input/billing; run-specific paths/identities contribute. The production getter reads one scalar without parsing a full command response or retaining a stale cache.

Local evidence: /tmp/rea-4497-cutter-document-20261016/. Essential claims are inline; local paths are not portable CI artifacts. The failed property-only experiment and private read-only probe are retained separately from the final unmodified-plugin workflow.

Compatibility, safety, and release

  • No public schema, dependency, migration or packaging change.
  • Linux actual Cutter Qt5 covered; other OS and real GUI document switching remain unverified. identity_status stays partial.
  • No target execution or mutation added. Selected paths remain exact; unavailable values are not formatted into invented identities.

Author readiness

Human owner: @N0zoM1z0

Recorded at the human owner's explicit session instruction to complete readiness declarations and request review. The assistant performed the diff review and checks above; no independent manual human review is claimed.

  • 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/4507 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/16/2026 **Status:** ✅ Merged **Merged:** 10/16/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/cutter-document-identity-4497` --- ### 📝 Commits (1) - [`93382aa`](https://github.com/morluto/rea/commit/93382aa6869e092d8e6c14e75ac10f4c29e1b98e) fix(cutter): read the active document from core configuration ### 📊 Changes **2 files changed** (+62 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `bridge/cutter/rea_bridge.py` (+2 -2) 📝 `tests/fixtures/cutter_bridge_protocol_test.py` (+60 -1) </details> ### 📄 Description ## Summary Fixes #4497. Cutter discovery and command Evidence now report the active core's file path instead of `null` when an ELF is loaded. Document generation can consequently observe path changes and reject commands against an earlier generation. ## Problem and expected behavior The bridge calls `currentlyOpenFile()` and swallows the failure. That member is a string, and native probing plus Cutter source show it is a debugging backup rather than the ordinary current-file getter. The file loaded in the real GUI appears in `getConfig("file.path")` and `ij.core.file` while the backup member remains empty. ## Change and scope Read the existing scalar `CutterCore.getConfig("file.path")` at the producer boundary. Preserve the exact nonempty string; absent, malformed or unreadable values remain unknown. CLI/MCP consume the existing bridge facts without another interpretation. No cache: this is live document state, refreshed by the existing GUI-thread dispatcher. Ordinary metadata correction within existing authority; no new provider, execution, injection, mutation or protection recovery. Separate scope approval is not applicable. ## Contract and boundary impact - Semantic owner/earliest stage: Python dispatcher reads the current core configuration before status/command admission and after commands. - CLI/MCP/tool catalog: existing fields and schemas; `current_file` becomes populated when observed. Same instance UUID and generation protocol. - Provider/format/platform compatibility: official Linux Cutter 2.5.0 Qt5 verified; other hosts unverified. Missing API/value remains unknown. - Evidence/provenance: current path and observed generation propagate through the existing command Evidence; identity remains `partial`, including the documented same-path reload/tab limitation. - Authority/cleanup: scalar configuration read only; no document changes, GUI closure or new process ownership. Existing command authority is unchanged. - Generated/package/install impact: none; no artifacts or binaries committed. Expected effects: - [x] 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. - [x] 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 existing bridge exchanges remain authenticated loopback requests. Verification launches a fixture-owned GUI; the change does not launch one. ## Evidence and regression coverage - The production-boundary Python regression fails against an immutable snapshot of clean main `a6c6a76d37c729e17cccf2dd20fe8e8177d98b14`: a known configured path is returned as `None`. It passes with the corrected owner API. Tests cover exact Unicode/`#?` paths, initialization/status, unchanged/changed generations, stale-command rejection before dispatch, valid dispatch, and unknown/malformed/unreadable configuration. - Actual official Cutter Qt5 on clean main and final head: two CLI/three stdio MCP calls on a controlled ELF with a Unicode/`#?` filename. Base discovery returns `null` although `ij` identifies the loaded ELF; final CLI/MCP discovery and both Evidence observations preserve the exact path. The ELF bytes stay unchanged, MCP disconnect preserves Cutter, and fixture-owned cleanup leaves verified empty process lineage. - Real GUI document switching and same-path reload identity were not tested; the generation-transition test runs the actual Python producer against a controlled host configuration. Host-version provenance remains separately tracked in #4498. Qt6 plugin loading remains upstream rizinorg/cutter#3659. - [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 Final source `93382aa6869e092d8e6c14e75ac10f4c29e1b98e`, based on latest main `a6c6a76d37c729e17cccf2dd20fe8e8177d98b14`: - `python3 tests/fixtures/cutter_bridge_protocol_test.py` — **11 passed**; final regression on the immutable base fails as expected. - `npm run test:focused --` 10 relevant Cutter CLI/MCP/provider and mutation-config/workflow files — **66 passed**, including the Python producer boundary. - `npm run check:ci` and `npm run docs:check` — passed. - Actual official Cutter 2.5.0 Qt5 public CLI/stdio MCP workflow — passed on final committed source, without the separate diagnostic plugin. One completed healthy native task/revision, two CPU cores: base → fix wall **9.00 → 9.60 s**, CPU **10.88 → 12.02 s**, sampled family peak **1.059 → 1.011 GiB**. Shared host and uncontrolled caches/load: these single observations establish neither speedup nor a stable performance regression. Fresh GUI/profile, CLI and MCP processes were used; cold OS cache was not established. Per-call first/subsequent timings are retained locally. Whole wire+CLI `o200k_base` serialization proxy **835,254 → 835,472**, including identical **829,341**-token full catalogs. Named two-tool definitions+calls+CLI proxy **8,561 → 8,779**. Existing provenance fields now carry paths; no extra calls or fields are added. These are serialization estimates, not model input/billing; run-specific paths/identities contribute. The production getter reads one scalar without parsing a full command response or retaining a stale cache. Local evidence: `/tmp/rea-4497-cutter-document-20261016/`. Essential claims are inline; local paths are not portable CI artifacts. The failed property-only experiment and private read-only probe are retained separately from the final unmodified-plugin workflow. ## Compatibility, safety, and release - No public schema, dependency, migration or packaging change. - Linux actual Cutter Qt5 covered; other OS and real GUI document switching remain unverified. `identity_status` stays partial. - No target execution or mutation added. Selected paths remain exact; unavailable values are not formatted into invented identities. ## Author readiness Human owner: @N0zoM1z0 Recorded at the human owner's explicit session instruction to complete readiness declarations and request review. The assistant performed the diff review and checks above; no independent manual human review is claimed. - [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 - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [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 01:13:14 +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#6276
No description provided.