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 #1564] [MERGED] feat(clients): register ZCode during setup #2974

New issue
Closed
opened 2026-10-17 21:12:25 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-17 21:12:25 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1564
Author: @IvenKooLab
Created: 10/10/2026
Status: ✅ Merged
Merged: 10/12/2026
Merged by: @morluto

Base: main ← Head: feat/zcode-client

📝 Commits (4)

  • c1b9b23 feat(clients): register ZCode during setup
  • 8657bf2 fix(clients): preserve ZCode fallback servers and honor enable flag
  • a443d33 fix(clients): reject non-regular ZCode fallback files before reading
  • 4462432 fix(clients): integrate ZCode setup and preserve fallback settings

📊 Changes

10 files changed (+638 additions, -14 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/references/connection-and-recovery.md (+1 -1)
📝 docs/client-configuration.md (+20 -0)
📝 docs/installation.md (+1 -0)
📝 src/application/ClientConfigurationDocument.ts (+45 -2)
📝 src/application/ClientRegistrationStatus.ts (+3 -1)
📝 src/application/SetupClientConfiguration.ts (+89 -10)
📝 src/application/SupportedClients.ts (+17 -0)
📝 tests/boundary/filesystem/clientLifecycle.test.ts (+1 -0)
📝 tests/boundary/filesystem/setupClientConfigCleanupOwnership.test.ts (+60 -0)
➕ tests/boundary/filesystem/zcodeClientConfiguration.test.ts (+401 -0)

📄 Description

Summary

Registers ZCode (Z.ai's coding-agent CLI) as a supported client during npx rea-agents setup, following the same pattern as the merged Qwen Code registration (#1415). After this change, ZCode users can install REA with one command: setup writes the rea MCP server into the user-level ~/.zcode/cli/config.json and installs the REA skill into ~/.zcode/skills.

Problem and expected behavior

ZCode is not among the clients setup recognizes, so its users must hand-edit a nested JSON structure that no other client uses. Expected behavior: after setup, mcp.servers.rea exists in ~/.zcode/cli/config.json and the REA skill is installed under ~/.zcode/skills; uninstall removes exactly the rea entry and the installed skill directory.

ZCode's configuration dialect (verified against a live install):

  • MCP servers live in the nested mcp.servers table of the user-level config; entries carry command, args, and env (stdio, no transport discriminator).
  • Personal skills are discovered from ~/.zcode/skills, not the shared skills root.

Change and scope

  • SupportedClients: zcode definition — config path ~/.zcode/cli/config.json, marker ~/.zcode/cli, skill path ~/.zcode/skills, format zcode.
  • ClientConfigurationDocument:
    • mcp servers key for zcode (shared with opencode).
    • A zcode branch in parseClientConfiguration that returns the nested table with serversPath: ["mcp", "servers"].
    • withClientServers now treats a missing outer table as empty. This also fixes the same latent crash for a fresh opencode document (the other format using the mcp key), where a missing outer table previously threw during write.
  • docs/installation.md: ZCode row in the supported-clients table plus a short configuration note.
  • Skill install/uninstall plans are already data-driven from the definition's skillPath, so no SetupPlan/Uninstall changes are needed.
  • Intentionally out of scope: non-stdio transports and ZCode-specific skill variants.

Contract and boundary impact

  • Semantic owner and earliest changed stage: application-layer setup client registration (SupportedClients, ClientConfigurationDocument).
  • CLI and MCP/tool-catalog contract: none (no tools added or changed).
  • Provider, bridge, target-format, or platform compatibility: adds the zcode client configuration format (nested mcp.servers JSON).
  • Evidence, artifact, provenance, or reconstruction contract: not applicable.
  • Process execution, authorization, cleanup, or containment impact: uninstall removes only the rea entry and the installed skill directory.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none authored; generated catalogs stay CI-owned.

Evidence and regression coverage

  • Tests added or updated: tests/boundary/filesystem/zcodeClientConfiguration.test.ts (6 cases) — config path resolution, upsert preserving unrelated settings, fresh/empty documents (missing outer mcp table), and uninstall removing only the rea entry. clientLifecycle.test.ts expected-client list now includes zcode.
  • Base reproduction or other evidence: not applicable (feature).
  • User-visible CLI/MCP output (if applicable): setup and uninstall now list "ZCode" as a client label.
  • Remaining proof gaps: the full boundary suite was not run on a Unix host locally; two pre-existing symlink tests in clientLifecycle.test.ts fail on this Windows machine because Node cannot create symlinks without Developer Mode, reproduced identically on stock main.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm ci — clean install (Node v22.23.2, npm 10.9.8; .nvmrc pins 24.18.0, so CI covers the pinned toolchain)
  • npx vitest run tests/boundary/filesystem/zcodeClientConfiguration.test.ts — 6/6 passed
  • npx tsc -p tsconfig.json --noEmit — clean
  • npm run check:fast — typecheck + lint green (also passed as the pre-push hook)
  • npm run verify:test-discovery — all 733 test files discovered exactly once
  • npx vitest run tests/boundary/filesystem/clientLifecycle.test.ts — 41/43 passed; the 2 failures are the pre-existing Windows symlink cases described above (identical on main)

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; config I/O is covered by filesystem boundary tests.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: setup writes only the rea entry into ~/.zcode/cli/config.json (preserving all unrelated settings) and installs the skill under ~/.zcode/skills; no network access or process execution added.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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. (No open issue for ZCode support found; same-pattern precedent discussion in #1415.)
  • 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. (New client label in the setup client list only.)
  • 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/1564 **Author:** [@IvenKooLab](https://github.com/IvenKooLab) **Created:** 10/10/2026 **Status:** ✅ Merged **Merged:** 10/12/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `feat/zcode-client` --- ### 📝 Commits (4) - [`c1b9b23`](https://github.com/morluto/rea/commit/c1b9b23156a05ed9272a9cf25cd22dedcc9e3438) feat(clients): register ZCode during setup - [`8657bf2`](https://github.com/morluto/rea/commit/8657bf2d270307725d9cf6a87ac2882bd152391d) fix(clients): preserve ZCode fallback servers and honor enable flag - [`a443d33`](https://github.com/morluto/rea/commit/a443d33fdd9c88beca11524a4d34cc6e05027203) fix(clients): reject non-regular ZCode fallback files before reading - [`4462432`](https://github.com/morluto/rea/commit/44624327da2e4767a6b410ecc5154d3493cac154) fix(clients): integrate ZCode setup and preserve fallback settings ### 📊 Changes **10 files changed** (+638 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md` (+1 -1) 📝 `docs/client-configuration.md` (+20 -0) 📝 `docs/installation.md` (+1 -0) 📝 `src/application/ClientConfigurationDocument.ts` (+45 -2) 📝 `src/application/ClientRegistrationStatus.ts` (+3 -1) 📝 `src/application/SetupClientConfiguration.ts` (+89 -10) 📝 `src/application/SupportedClients.ts` (+17 -0) 📝 `tests/boundary/filesystem/clientLifecycle.test.ts` (+1 -0) 📝 `tests/boundary/filesystem/setupClientConfigCleanupOwnership.test.ts` (+60 -0) ➕ `tests/boundary/filesystem/zcodeClientConfiguration.test.ts` (+401 -0) </details> ### 📄 Description ## Summary Registers ZCode (Z.ai's coding-agent CLI) as a supported client during `npx rea-agents setup`, following the same pattern as the merged Qwen Code registration (#1415). After this change, ZCode users can install REA with one command: setup writes the `rea` MCP server into the user-level `~/.zcode/cli/config.json` and installs the REA skill into `~/.zcode/skills`. ## Problem and expected behavior ZCode is not among the clients setup recognizes, so its users must hand-edit a nested JSON structure that no other client uses. Expected behavior: after setup, `mcp.servers.rea` exists in `~/.zcode/cli/config.json` and the REA skill is installed under `~/.zcode/skills`; uninstall removes exactly the `rea` entry and the installed skill directory. ZCode's configuration dialect (verified against a live install): - MCP servers live in the **nested `mcp.servers` table** of the user-level config; entries carry `command`, `args`, and `env` (stdio, no transport discriminator). - Personal skills are discovered from `~/.zcode/skills`, not the shared skills root. ## Change and scope - `SupportedClients`: `zcode` definition — config path `~/.zcode/cli/config.json`, marker `~/.zcode/cli`, skill path `~/.zcode/skills`, format `zcode`. - `ClientConfigurationDocument`: - `mcp` servers key for `zcode` (shared with `opencode`). - A `zcode` branch in `parseClientConfiguration` that returns the nested table with `serversPath: ["mcp", "servers"]`. - `withClientServers` now treats a missing outer table as empty. This also fixes the same latent crash for a fresh `opencode` document (the other format using the `mcp` key), where a missing outer table previously threw during write. - `docs/installation.md`: ZCode row in the supported-clients table plus a short configuration note. - Skill install/uninstall plans are already data-driven from the definition's `skillPath`, so no `SetupPlan`/`Uninstall` changes are needed. - Intentionally out of scope: non-stdio transports and ZCode-specific skill variants. ## Contract and boundary impact - Semantic owner and earliest changed stage: application-layer setup client registration (`SupportedClients`, `ClientConfigurationDocument`). - CLI and MCP/tool-catalog contract: none (no tools added or changed). - Provider, bridge, target-format, or platform compatibility: adds the `zcode` client configuration format (nested `mcp.servers` JSON). - Evidence, artifact, provenance, or reconstruction contract: not applicable. - Process execution, authorization, cleanup, or containment impact: uninstall removes only the `rea` entry and the installed skill directory. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none authored; generated catalogs stay CI-owned. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/filesystem/zcodeClientConfiguration.test.ts` (6 cases) — config path resolution, upsert preserving unrelated settings, fresh/empty documents (missing outer `mcp` table), and uninstall removing only the `rea` entry. `clientLifecycle.test.ts` expected-client list now includes `zcode`. - Base reproduction or other evidence: not applicable (feature). - User-visible CLI/MCP output (if applicable): setup and uninstall now list "ZCode" as a client label. - Remaining proof gaps: the full boundary suite was not run on a Unix host locally; two pre-existing symlink tests in `clientLifecycle.test.ts` fail on this Windows machine because Node cannot create symlinks without Developer Mode, reproduced identically on stock `main`. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm ci` — clean install (Node v22.23.2, npm 10.9.8; `.nvmrc` pins 24.18.0, so CI covers the pinned toolchain) - `npx vitest run tests/boundary/filesystem/zcodeClientConfiguration.test.ts` — 6/6 passed - `npx tsc -p tsconfig.json --noEmit` — clean - `npm run check:fast` — typecheck + lint green (also passed as the pre-push hook) - `npm run verify:test-discovery` — all 733 test files discovered exactly once - `npx vitest run tests/boundary/filesystem/clientLifecycle.test.ts` — 41/43 passed; the 2 failures are the pre-existing Windows symlink cases described above (identical on `main`) ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; config I/O is covered by filesystem boundary tests. - Package or release metadata impact: none. - Security, privacy, process, or containment review: setup writes only the `rea` entry into `~/.zcode/cli/config.json` (preserving all unrelated settings) and installs the skill under `~/.zcode/skills`; no network access or process execution added. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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. (No open issue for ZCode support found; same-pattern precedent discussion in #1415.) - [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. (New client label in the setup client list only.) - [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-17 21:12:25 +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#2974
No description provided.