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

[GH-ISSUE #97] Support MCP Tasks for long-running analysis operations #63

New issue
Closed
opened 2026-10-15 18:20:40 +00:00 by bsakaguchi · 3 comments
bsakaguchi commented 2026-10-15 18:20:40 +00:00
Owner
Copy link

Originally created by @morluto on GitHub (Jul 13, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/97

Summary

Add a provider-neutral asynchronous job model and expose eligible long-running REA operations through capability-negotiated MCP Tasks. Preserve synchronous tool calls for clients that do not support Tasks.

MCP Tasks are experimental. REA's core execution model must not depend directly on unstable SDK APIs; the MCP Tasks adapter should sit over an internal operation abstraction with explicit ownership, status, cancellation, retention, and result identity.

Current state in REA 1.3.0

  • Hopper loading, artifact inventory, process capture, cross-version investigation, and reconstruction verification remain synchronous calls.
  • REA has strong process/session ownership and persistent snapshot/workspace primitives, but no general background-job abstraction.
  • There is no tasks/get, tasks/result, tasks/list, tasks/cancel, task retention store, or related-task metadata.
  • Guided prompts and completion are shipped, but they do not execute or retain work.
  • Process permission elicitation is tracked separately in #96.
  • Ordinary progress and cancellation are tracked in #98.

User problem

Expensive work can exceed a comfortable tool-call lifetime. Agents cannot:

  • start work and continue other reasoning;
  • recover a result after a client reconnect;
  • poll durable phase status;
  • cancel through a stateful protocol;
  • distinguish waiting for user input from active computation;
  • retrieve completed evidence without re-running analysis.

Proposed architecture

1. Internal operation model

Introduce an SDK-independent operation state machine with queued, working, input_required, completed, failed, and cancelled states.

Each operation should own:

  • cryptographically strong ID;
  • operation kind and normalized request identity;
  • originating session/authorization context;
  • created/updated timestamps;
  • bounded TTL;
  • status and safe status message;
  • progress state;
  • cancellation signal;
  • cleanup state;
  • final typed tool result or typed failure;
  • evidence IDs produced during execution.

2. MCP Tasks adapter

When the client advertises the required Tasks capability:

  • accept a task-augmented tools/call;
  • return CreateTaskResult promptly;
  • implement tasks/get, tasks/result, tasks/list, and tasks/cancel;
  • attach io.modelcontextprotocol/related-task metadata to associated progress and elicitation;
  • bind task access to the originating connection or authorization context;
  • make tasks/result return exactly the underlying tool result.

3. Compatibility path

For clients without Tasks:

  • retain current synchronous behavior;
  • use ordinary progress and cancellation from #98;
  • never advertise task-backed behavior that the client cannot consume.

4. Initial eligible operations

Start with operations whose runtime or output justifies task execution:

  1. binary/Hopper open and analysis;
  2. exhaustive artifact inventory;
  3. bounded process capture;
  4. persistent cross-version investigation;
  5. reconstruction verification;
  6. large batch decompilation or comparison.

Small navigation and read-only metadata calls should remain synchronous.

Security and lifecycle requirements

  • Task IDs must be unguessable and scoped to the originating context.
  • tasks/list must not expose work across clients.
  • Cancellation must stop owned work and run verified cleanup.
  • Expired results must be deleted promptly.
  • Task results must retain Evidence v2 identity and limitations.
  • input_required must not be used to bypass permission policy.
  • An MCP disconnect may retain a task only when its authorization context remains safely recoverable; otherwise cancel it.
  • Concurrency and retained-byte limits must be enforced per client.

Acceptance criteria

  • An internal operation abstraction exists independently of MCP SDK Tasks types.
  • Hopper analysis, artifact inventory, process capture, cross-version investigation, and reconstruction verification can run through it.
  • Capability-negotiated MCP Tasks support tasks/get, tasks/result, tasks/list, and tasks/cancel.
  • tasks/result is contract-equivalent to the corresponding synchronous tool result.
  • Status messages identify useful phases without exposing sensitive provider diagnostics.
  • Progress tokens continue across the task lifetime.
  • input_required can associate a permission elicitation from #96 with the task.
  • Cancellation propagates through providers and verifies cleanup.
  • Results have documented TTL, byte, and concurrency limits.
  • Task access is bound to the correct connection/authorization context.
  • Synchronous fallback remains fully supported.
  • Tests cover success, typed failure, cancellation, cancellation races, expiry, input_required, disconnect, result retrieval, unauthorized lookup, list isolation, and unsupported-client fallback.
  • Documentation marks the MCP Tasks surface experimental and identifies the supported protocol/SDK versions.

Non-goals

  • Making every tiny REA tool asynchronous.
  • Treating Tasks as permanent evidence storage.
  • Allowing task execution to expand filesystem, executable, or network policy.
  • Depending on deprecated MCP sampling, roots, or logging.

Dependencies

  • #98 for common progress/cancellation primitives.
  • #96 for scoped permission elicitation.
  • #99 for addressable retained evidence after task completion.

July 2026 SDK and Tasks extension update

REA currently pins the split MCP SDK packages at 2.0.0-beta.4. Investigation of beta.3 and beta.4 found that their exported task schemas describe the experimental 2025-11-25 task design, but the SDK does not provide the former high-level task manager/runtime. Meanwhile, current MCP Tasks work has moved to the Extensions Track and uses a different evolving contract, including different operation and result shapes.

The internal operation model in this issue remains required and should proceed independently of MCP wire types. The MCP adapter described above is now a historical target, not an implementation contract.

Before implementing the public adapter:

  • select and document one exact Tasks extension revision and compatible SDK version;
  • reconcile tasks/list and tasks/result assumptions with the selected extension;
  • reconcile task capability negotiation, result discrimination, update/input flow, cancellation, and related-task metadata with that revision;
  • keep all extension-specific schemas and lifecycle translation in the MCP adapter;
  • retain synchronous fallback and ordinary progress/cancellation from #98;
  • add conformance tests proving the selected wire contract rather than relying only on exported TypeScript types.

Acceptance criteria referring to specific task methods or metadata should be evaluated against the selected extension revision before implementation. No task capability should be advertised until REA implements and tests the complete selected contract.

Originally created by @morluto on GitHub (Jul 13, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/97 ## Summary Add a provider-neutral asynchronous job model and expose eligible long-running REA operations through capability-negotiated MCP Tasks. Preserve synchronous tool calls for clients that do not support Tasks. MCP Tasks are experimental. REA's core execution model must not depend directly on unstable SDK APIs; the MCP Tasks adapter should sit over an internal operation abstraction with explicit ownership, status, cancellation, retention, and result identity. ## Current state in REA 1.3.0 - Hopper loading, artifact inventory, process capture, cross-version investigation, and reconstruction verification remain synchronous calls. - REA has strong process/session ownership and persistent snapshot/workspace primitives, but no general background-job abstraction. - There is no tasks/get, tasks/result, tasks/list, tasks/cancel, task retention store, or related-task metadata. - Guided prompts and completion are shipped, but they do not execute or retain work. - Process permission elicitation is tracked separately in #96. - Ordinary progress and cancellation are tracked in #98. ## User problem Expensive work can exceed a comfortable tool-call lifetime. Agents cannot: - start work and continue other reasoning; - recover a result after a client reconnect; - poll durable phase status; - cancel through a stateful protocol; - distinguish waiting for user input from active computation; - retrieve completed evidence without re-running analysis. ## Proposed architecture ### 1. Internal operation model Introduce an SDK-independent operation state machine with queued, working, input_required, completed, failed, and cancelled states. Each operation should own: - cryptographically strong ID; - operation kind and normalized request identity; - originating session/authorization context; - created/updated timestamps; - bounded TTL; - status and safe status message; - progress state; - cancellation signal; - cleanup state; - final typed tool result or typed failure; - evidence IDs produced during execution. ### 2. MCP Tasks adapter When the client advertises the required Tasks capability: - accept a task-augmented tools/call; - return CreateTaskResult promptly; - implement tasks/get, tasks/result, tasks/list, and tasks/cancel; - attach io.modelcontextprotocol/related-task metadata to associated progress and elicitation; - bind task access to the originating connection or authorization context; - make tasks/result return exactly the underlying tool result. ### 3. Compatibility path For clients without Tasks: - retain current synchronous behavior; - use ordinary progress and cancellation from #98; - never advertise task-backed behavior that the client cannot consume. ### 4. Initial eligible operations Start with operations whose runtime or output justifies task execution: 1. binary/Hopper open and analysis; 2. exhaustive artifact inventory; 3. bounded process capture; 4. persistent cross-version investigation; 5. reconstruction verification; 6. large batch decompilation or comparison. Small navigation and read-only metadata calls should remain synchronous. ## Security and lifecycle requirements - Task IDs must be unguessable and scoped to the originating context. - tasks/list must not expose work across clients. - Cancellation must stop owned work and run verified cleanup. - Expired results must be deleted promptly. - Task results must retain Evidence v2 identity and limitations. - input_required must not be used to bypass permission policy. - An MCP disconnect may retain a task only when its authorization context remains safely recoverable; otherwise cancel it. - Concurrency and retained-byte limits must be enforced per client. ## Acceptance criteria - [ ] An internal operation abstraction exists independently of MCP SDK Tasks types. - [ ] Hopper analysis, artifact inventory, process capture, cross-version investigation, and reconstruction verification can run through it. - [ ] Capability-negotiated MCP Tasks support tasks/get, tasks/result, tasks/list, and tasks/cancel. - [ ] tasks/result is contract-equivalent to the corresponding synchronous tool result. - [ ] Status messages identify useful phases without exposing sensitive provider diagnostics. - [ ] Progress tokens continue across the task lifetime. - [ ] input_required can associate a permission elicitation from #96 with the task. - [ ] Cancellation propagates through providers and verifies cleanup. - [ ] Results have documented TTL, byte, and concurrency limits. - [ ] Task access is bound to the correct connection/authorization context. - [ ] Synchronous fallback remains fully supported. - [ ] Tests cover success, typed failure, cancellation, cancellation races, expiry, input_required, disconnect, result retrieval, unauthorized lookup, list isolation, and unsupported-client fallback. - [ ] Documentation marks the MCP Tasks surface experimental and identifies the supported protocol/SDK versions. ## Non-goals - Making every tiny REA tool asynchronous. - Treating Tasks as permanent evidence storage. - Allowing task execution to expand filesystem, executable, or network policy. - Depending on deprecated MCP sampling, roots, or logging. ## Dependencies - #98 for common progress/cancellation primitives. - #96 for scoped permission elicitation. - #99 for addressable retained evidence after task completion. ## July 2026 SDK and Tasks extension update REA currently pins the split MCP SDK packages at `2.0.0-beta.4`. Investigation of beta.3 and beta.4 found that their exported task schemas describe the experimental `2025-11-25` task design, but the SDK does not provide the former high-level task manager/runtime. Meanwhile, current MCP Tasks work has moved to the Extensions Track and uses a different evolving contract, including different operation and result shapes. The internal operation model in this issue remains required and should proceed independently of MCP wire types. The MCP adapter described above is now a historical target, not an implementation contract. Before implementing the public adapter: - select and document one exact Tasks extension revision and compatible SDK version; - reconcile `tasks/list` and `tasks/result` assumptions with the selected extension; - reconcile task capability negotiation, result discrimination, update/input flow, cancellation, and related-task metadata with that revision; - keep all extension-specific schemas and lifecycle translation in the MCP adapter; - retain synchronous fallback and ordinary progress/cancellation from #98; - add conformance tests proving the selected wire contract rather than relying only on exported TypeScript types. Acceptance criteria referring to specific task methods or metadata should be evaluated against the selected extension revision before implementation. No task capability should be advertised until REA implements and tests the complete selected contract.
bsakaguchi 2026-10-15 18:20:40 +00:00
bsakaguchi commented 2026-10-15 18:20:42 +00:00
Author
Owner
Copy link

@morluto commented on GitHub (Jul 17, 2026):

Current external-contract research confirms this should remain open but must not target the removed experimental SDK API. The MCP TypeScript SDK v2 removed its prior experimental Tasks surface pending the SEP-2663 Tasks Extension. REA should first select and pin an exact extension revision, then implement an SDK-independent retained-operation state machine and conformance adapter while preserving the synchronous path. Progress and resource prerequisites are already shipped.

<!-- gh-comment-id:5001695839 --> @morluto commented on GitHub (Jul 17, 2026): Current external-contract research confirms this should remain open but must not target the removed experimental SDK API. The MCP TypeScript SDK v2 removed its prior experimental Tasks surface pending the SEP-2663 Tasks Extension. REA should first select and pin an exact extension revision, then implement an SDK-independent retained-operation state machine and conformance adapter while preserving the synchronous path. Progress and resource prerequisites are already shipped.
bsakaguchi commented 2026-10-15 18:20:42 +00:00
Author
Owner
Copy link

@morluto commented on GitHub (Jul 20, 2026):

Split into focused child issues:

These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.

<!-- gh-comment-id:5023447402 --> @morluto commented on GitHub (Jul 20, 2026): Split into focused child issues: - [ ] #390 - [ ] #391 These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.
bsakaguchi commented 2026-10-15 18:20:42 +00:00
Author
Owner
Copy link

@morluto commented on GitHub (Jul 20, 2026):

Closing as out of scope / premature for the current local CLI/MCP reverse-engineering focus: no supporting code exists, and these areas should be revisited only after in-tree providers and the public boundary are stable.

<!-- gh-comment-id:5023568882 --> @morluto commented on GitHub (Jul 20, 2026): Closing as out of scope / premature for the current local CLI/MCP reverse-engineering focus: no supporting code exists, and these areas should be revisited only after in-tree providers and the public boundary are stable.
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#63
No description provided.