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

[PR #4944] [MERGED] fix(setup): admit only strict JSON for Claude Code configuration #6684

New issue
Closed
opened 2026-11-01 21:42:16 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:42:16 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4944
Author: @kaoru0822-kitauji
Created: 10/18/2026
Status: ✅ Merged
Merged: 10/18/2026
Merged by: @kaoru0822-kitauji

Base: main ← Head: fix/claude-code-strict-json-config

📝 Commits (1)

  • 877c202 fix(setup): admit only strict JSON for Claude Code configuration

📊 Changes

5 files changed (+227 additions, -78 deletions)

View changed files

📝 src/application/ClientConfigurationDocument.ts (+7 -0)
📝 src/application/SupportedClients.ts (+2 -1)
➕ tests/acceptance/setup/claudeCodeStrictJsonSetup.test.ts (+128 -0)
📝 tests/boundary/filesystem/clientConfigurationBom.test.ts (+79 -74)
📝 tests/boundary/filesystem/windowsNpxRegistration.test.ts (+11 -3)

📄 Description

Summary

Fixes #4940. Claude Code setup reported ready for a .claude.json with a comment or trailing comma, kept that syntax in the file it wrote, and doctor then reported the registration aligned. The issue reporter found that native Claude Code rejects such a file as corrupt JSON. With this change, setup, doctor and uninstall refuse those files as malformed before writing anything or creating a backup. Plain JSON and BOM-prefixed JSON still configure.

Problem and expected behavior

Trigger: .claude.json = { // comment\n "mcpServers": {...} } (or a trailing comma). Claude Code shared the generic json client format. parseDocument reads that format through jsonc-parser with comments and trailing commas enabled. The broken rule: setup must not admit configuration the selected native client cannot load. Expected: needs_human with no write or backup, and doctor reporting the registration invalid rather than aligned.

Change and scope

  • SupportedClients.ts: Claude Code now uses its own claude_code configuration format instead of json.
  • ClientConfigurationDocument.ts (parseDocument): the new format is parsed with strict JSON.parse after removing a leading UTF-8 BOM. This matches the native behavior described in the issue and follows the existing per-client strict readers (Pi, Kimi, ZCode). Setup, doctor and uninstall already use this parser, so no downstream changes are needed.
  • Registration entries, server key and serialization still fall through to the defaults the json format used.
  • Not included: other json-format clients (Cursor, Claude Desktop, Windsurf, etc.) keep JSONC admission. Their native readers were not re-examined here. Empty-file handling for Claude Code is unchanged.
  • Contribution scope: not applicable (ordinary fix within existing setup boundaries).

Contract and boundary impact

  • Semantic owner and earliest changed stage: parseDocument in src/application/ClientConfigurationDocument.ts, selected by the client's format in SupportedClients.ts.

  • Contribution scope fit and linked maintainer decision: not applicable.

  • CLI and MCP/tool-catalog contract: setup's clientStates[].client.format for Claude Code changes from "json" to "claude_code". No tool catalog changes.

  • Provider, bridge, target-format, or platform compatibility: none.

  • Evidence, artifact, provenance, or reconstruction contract: none.

  • Target selection, authority, upstream behavior, and cleanup details: not applicable.

  • Generated metadata: setup_clients[].format for claude_code in the generated product catalog becomes "claude_code". npm run docs:check passes.

  • Read existing files or captured data.

  • Change process memory, registers, files, or configuration. (Only refusals change: fewer writes than before.)

Evidence and regression coverage

  • Tests added or updated:
    • New tests/acceptance/setup/claudeCodeStrictJsonSetup.test.ts (public CLI):
      • Comment and trailing-comma fixtures: setup --dry-run and --yes return needs_human with a "malformed" remediation, doctor reports invalid, uninstall reports failed, file bytes are unchanged and no .rea.backup exists.
      • Plain and BOM-prefixed JSON: setup returns configured, the backup is byte-exact, the BOM is kept, the output passes JSON.parse, and doctor reports aligned.
    • tests/boundary/filesystem/clientConfigurationBom.test.ts: removed claude_code from the comment-preserving JSONC matrix, which encoded the bug.
    • tests/boundary/filesystem/windowsNpxRegistration.test.ts: Claude Code fixtures now use the claude_code format.
  • Base reproduction:
    • On base 847472acf, node scripts/rea.mjs setup --client claude_code --skill=false --dry-run --json with HOME/CLAUDE_CONFIG_DIR pointed at an isolated directory holding the issue's fixture returned planned, exit 0. With this change it returns needs_human, exit 1.
    • With the source fix reverted, the new acceptance test fails both refusal cases (2 failed, 2 passed).
  • Remaining proof gaps: native Claude Code was not run. The strict-JSON behavior comes from the issue reporter's observation with Claude Code 2.1.263. Only macOS was tested.

Validation performed

  • npm run test:focused -- tests/acceptance/setup/claudeCodeStrictJsonSetup.test.ts tests/boundary/filesystem/clientConfigurationBom.test.ts tests/boundary/filesystem/windowsNpxRegistration.test.ts tests/acceptance/setup/clientConfigurationDiagnosticsCli.test.ts tests/boundary/filesystem/clientConfigurationDialects.test.ts tests/boundary/filesystem/clientLifecycle.test.ts tests/boundary/filesystem/clientRegistrationStatus.test.ts tests/boundary/filesystem/productCatalog.test.ts: 8 files passed, 167 passed, 2 skipped (Windows-only)
  • The same focused run of the new acceptance test with the source fix reverted: 2 failed, 2 passed (expected)
  • npm run check:fast: passed
  • npm run docs:check: passed
  • npx oxfmt --check on the changed files: passed
  • Issue reproduction CLI command, before and after: planned/exit 0 before, needs_human/exit 1 after

Compatibility, safety, and release

  • Breaking changes or migration steps: none intended. A Claude Code config with comments or trailing commas, which Claude Code itself reportedly rejects, is now refused instead of edited.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable. macOS only. Native Claude Code not run.
  • Package or release metadata impact: the product catalog format value for claude_code changes.
  • Security, privacy, process, or containment review: refusals happen before any write or backup.

Author readiness

Human owner:

  • 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.

🤖 Generated with Claude Code

🔄 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/4944 **Author:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Created:** 10/18/2026 **Status:** ✅ Merged **Merged:** 10/18/2026 **Merged by:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Base:** `main` ← **Head:** `fix/claude-code-strict-json-config` --- ### 📝 Commits (1) - [`877c202`](https://github.com/morluto/rea/commit/877c2022cdea14371a295ec1cb03be41da8dfba2) fix(setup): admit only strict JSON for Claude Code configuration ### 📊 Changes **5 files changed** (+227 additions, -78 deletions) <details> <summary>View changed files</summary> 📝 `src/application/ClientConfigurationDocument.ts` (+7 -0) 📝 `src/application/SupportedClients.ts` (+2 -1) ➕ `tests/acceptance/setup/claudeCodeStrictJsonSetup.test.ts` (+128 -0) 📝 `tests/boundary/filesystem/clientConfigurationBom.test.ts` (+79 -74) 📝 `tests/boundary/filesystem/windowsNpxRegistration.test.ts` (+11 -3) </details> ### 📄 Description ## Summary Fixes #4940. Claude Code setup reported `ready` for a `.claude.json` with a comment or trailing comma, kept that syntax in the file it wrote, and doctor then reported the registration `aligned`. The issue reporter found that native Claude Code rejects such a file as corrupt JSON. With this change, setup, doctor and uninstall refuse those files as malformed before writing anything or creating a backup. Plain JSON and BOM-prefixed JSON still configure. ## Problem and expected behavior Trigger: `.claude.json` = `{ // comment\n "mcpServers": {...} }` (or a trailing comma). Claude Code shared the generic `json` client format. `parseDocument` reads that format through `jsonc-parser` with comments and trailing commas enabled. The broken rule: setup must not admit configuration the selected native client cannot load. Expected: `needs_human` with no write or backup, and doctor reporting the registration `invalid` rather than `aligned`. ## Change and scope - `SupportedClients.ts`: Claude Code now uses its own `claude_code` configuration format instead of `json`. - `ClientConfigurationDocument.ts` (`parseDocument`): the new format is parsed with strict `JSON.parse` after removing a leading UTF-8 BOM. This matches the native behavior described in the issue and follows the existing per-client strict readers (Pi, Kimi, ZCode). Setup, doctor and uninstall already use this parser, so no downstream changes are needed. - Registration entries, server key and serialization still fall through to the defaults the `json` format used. - Not included: other `json`-format clients (Cursor, Claude Desktop, Windsurf, etc.) keep JSONC admission. Their native readers were not re-examined here. Empty-file handling for Claude Code is unchanged. - Contribution scope: not applicable (ordinary fix within existing setup boundaries). ## Contract and boundary impact - Semantic owner and earliest changed stage: `parseDocument` in `src/application/ClientConfigurationDocument.ts`, selected by the client's format in `SupportedClients.ts`. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: setup's `clientStates[].client.format` for Claude Code changes from `"json"` to `"claude_code"`. No tool catalog changes. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata: `setup_clients[].format` for `claude_code` in the generated product catalog becomes `"claude_code"`. `npm run docs:check` passes. - [x] Read existing files or captured data. - [x] Change process memory, registers, files, or configuration. (Only refusals change: fewer writes than before.) ## Evidence and regression coverage - Tests added or updated: - New `tests/acceptance/setup/claudeCodeStrictJsonSetup.test.ts` (public CLI): - Comment and trailing-comma fixtures: setup `--dry-run` and `--yes` return `needs_human` with a "malformed" remediation, doctor reports `invalid`, uninstall reports `failed`, file bytes are unchanged and no `.rea.backup` exists. - Plain and BOM-prefixed JSON: setup returns `configured`, the backup is byte-exact, the BOM is kept, the output passes `JSON.parse`, and doctor reports `aligned`. - `tests/boundary/filesystem/clientConfigurationBom.test.ts`: removed `claude_code` from the comment-preserving JSONC matrix, which encoded the bug. - `tests/boundary/filesystem/windowsNpxRegistration.test.ts`: Claude Code fixtures now use the `claude_code` format. - Base reproduction: - On base `847472acf`, `node scripts/rea.mjs setup --client claude_code --skill=false --dry-run --json` with `HOME`/`CLAUDE_CONFIG_DIR` pointed at an isolated directory holding the issue's fixture returned `planned`, exit 0. With this change it returns `needs_human`, exit 1. - With the source fix reverted, the new acceptance test fails both refusal cases (2 failed, 2 passed). - Remaining proof gaps: native Claude Code was not run. The strict-JSON behavior comes from the issue reporter's observation with Claude Code 2.1.263. Only macOS was tested. ## Validation performed - `npm run test:focused -- tests/acceptance/setup/claudeCodeStrictJsonSetup.test.ts tests/boundary/filesystem/clientConfigurationBom.test.ts tests/boundary/filesystem/windowsNpxRegistration.test.ts tests/acceptance/setup/clientConfigurationDiagnosticsCli.test.ts tests/boundary/filesystem/clientConfigurationDialects.test.ts tests/boundary/filesystem/clientLifecycle.test.ts tests/boundary/filesystem/clientRegistrationStatus.test.ts tests/boundary/filesystem/productCatalog.test.ts`: 8 files passed, 167 passed, 2 skipped (Windows-only) - The same focused run of the new acceptance test with the source fix reverted: 2 failed, 2 passed (expected) - `npm run check:fast`: passed - `npm run docs:check`: passed - `npx oxfmt --check` on the changed files: passed - Issue reproduction CLI command, before and after: `planned`/exit 0 before, `needs_human`/exit 1 after ## Compatibility, safety, and release - Breaking changes or migration steps: none intended. A Claude Code config with comments or trailing commas, which Claude Code itself reportedly rejects, is now refused instead of edited. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. macOS only. Native Claude Code not run. - Package or release metadata impact: the product catalog format value for `claude_code` changes. - Security, privacy, process, or containment review: refusals happen before any write or backup. ## Author readiness Human owner: - [ ] 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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:42:16 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/procedure-reference-stacked
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#6684
No description provided.