feat: agentmask + service discovery infrastructure by FUDCo · Pull Request #952 · MetaMask/ocap-kernel

FUDCo · 2026-05-15T01:39:29Z

Summary

Lands the (current state of) Erik's rekm/agentmask branch as base (agentmask vats, OpenClaw MetaMask vendor plugin, capability schema discovery) onto main
Adds service-discovery type vocabulary, service matcher, sample services (Echo, RandomNumber), and a bridge that wires an LLM into the matcher's ranker
Adds openclaw service discovery plugin with skill, tools, and validation plan
Plus assorted relay/daemon/kernel-cli improvements and fixes

Important caveat: this requires using the updated version of the MetaMask browser extension (Erik's updates to put the ocap kernel into it and then some further stuff I needed to add on top of that) in the chip/agentmask branch of the metamask-extension repo. While the changes this PR represents are being proposed for merging into our main branch, we don't really have that option for the browser extension since it's not our repo to mess with. (I suppose we could merge it with some negotiation with the MetaMake team, but since it's highly experimental I'm pretty sure they wouldn't be too keen on that idea. I believe Erik's plan was to eventually have it in under a flag, but I don't thing that's yet an option.)

Test plan

Follow the procedure in packages/agentmask/openclaw-plugin-discovery/VALIDATION.md end-to-end (matcher daemon and LLM service consumer on VPS, sample services + MetaMask browser extension (providing MetaMask services) on laptop, OpenClaw agent driving discovery and contact)
Verify (peerId, providerTag) re-registration dedup by reloading the MetaMask extension and confirming the matcher evicts the prior provider entry
Verify cold-start path: full reset of all parts, then exercise discovery / find-services / call-service

Note

Medium Risk
Large new surface (LLM-driven wallet/signing and service contact) plus daemon/relay operational changes; correctness depends on experimental MetaMask extension integration documented outside this PR.

Overview
Introduces @ocap/agentmask as a monorepo home for AgentMask / OpenClaw integration: long-form docs (capability vendor, two-way kernel comms, host-developer kernel guide), plus two installable plugins that drive the ocap daemon via redeem-url and queueMessage.

@openclaw/metamask exposes tools to redeem a vendor OCAP URL, requestCapability, call capability methods, and list session capabilities (with Vitest coverage). @openclaw/discovery adds matcher-centric tools (discovery_find_services, contact initiation, service_call, tracked state) and a SKILL that forces matcher-first workflows instead of hard-coded services.

@metamask/kernel-cli gains a global --home flag (per-invocation OCAP_HOME), relay --public-ip / separate ~/.libp2p-relay bookkeeping, and stricter daemon startup (PID interlock, no silent socket takeover). .yarnrc.yml forwards HTTPS_PROXY for sandboxed installs; .claude/settings.json relaxes sandbox network/filesystem for Yarn.

End-to-end validation is documented in VALIDATION.md (matcher + consumer on VPS, MetaMask extension + sample services on laptop); the matching MetaMask extension changes live on a separate branch, not in this repo.

^{Reviewed by Cursor Bugbot for commit 9f0e86d. Bugbot is set up for automated code reviews on this repo. Configure here.}

Add the @ocap/agentmask package with an OpenClaw plugin that lets an LLM agent request and use wallet capabilities from a MetaMask capability vendor via the OCAP kernel daemon. The plugin provides three tools: - metamask_request_capability: redeem OCAP URL and request capabilities - metamask_call_capability: call methods on obtained capabilities - metamask_list_capabilities: list capabilities obtained in the session Also includes docs migrated from the extension repo (capability-vendor, demo-two-way-comms, kernel-guide) and updates demo-two-way-comms with parallel Manual CLI / OpenClaw agent instructions for the away side. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…edemption The agent can now ask the user for their OCAP URL during conversation and redeem it on the fly via the new metamask_obtain_vendor tool, rather than requiring the URL to be pre-configured in .env or plugin config. - Add metamask_obtain_vendor tool (accepts URL, redeems, stores vendor kref) - Move ocapUrl into mutable PluginState (seeded from config, overridable) - ensureVendor() directs the agent to metamask_obtain_vendor when no URL set - Update SKILL.md workflow and demo doc OpenClaw section Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…ion__ After obtaining a capability from the vendor, request_capability now calls __getDescription__ on it to retrieve method schemas (name, args, return type). The full schema is shown in the tool response and stored in plugin state. list_capabilities also shows method names. Discovery is best-effort — if the capability is not discoverable, the tool still works without method listings. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…CAP_HOME

…s into crypto

socket-security · 2026-05-15T01:40:23Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Vulnerability	Quality	Maintenance
jsdom@29.0.2 ⏵ 29.1.1	⁺¹		⁺¹
@typescript-eslint/utils@8.58.0 ⏵ 8.59.2
rolldown@1.0.0-rc.13 ⏵ 1.0.0-rc.17	⁺⁴
@vitest/browser@4.1.3 ⏵ 4.1.5	⁺¹		⁺¹	⁺¹
vitest@4.1.3 ⏵ 4.1.5			⁺¹
@vitest/coverage-v8@4.1.3 ⏵ 4.1.5
@metamask/create-release-branch@4.1.4 ⏵ 4.2.0	⁺³		⁺¹	⁺¹
postcss@8.5.8 ⏵ 8.5.14	⁺¹	⁺²		⁺²
vite@8.0.6 ⏵ 8.0.10	⁺¹		⁺¹
turbo@2.9.1 ⏵ 2.9.9
@vitest/browser-playwright@4.1.3 ⏵ 4.1.5				⁺¹
vite-plugin-static-copy@4.0.1 ⏵ 4.1.0	⁺¹		⁺¹
@metamask/json-rpc-engine@10.2.4 ⏵ 10.3.0				⁺⁵
@vitest/eslint-plugin@1.6.14 ⏵ 1.6.16	⁺¹		⁺¹

View full report

socket-security · 2026-05-15T01:40:25Z

Warning

MetaMask internal reviewing guidelines:

Do not ignore-all
Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
@SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Potential code anomaly (AI signal): npm `@emnapi/core` is 100.0% likely to have a medium risk anomaly Notes: No explicit evidence of overt malware (network exfiltration, credential theft, backdoors, or filesystem/process activity) appears in this fragment. However, the module contains high-sensitivity dynamic execution capabilities: napi_run_script performs eval-like execution of a JavaScript string obtained from WebAssembly, and emnapiCreateFunction can use the Function constructor for wrapper generation. Combined with wasm-driven indirect callback dispatch and reflective object mutation, this runtime is security-sensitive and should only be used with fully trusted WebAssembly and tightly controlled inputs. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/rolldown@1.0.0-rc.17` → `npm/eslint-plugin-import-x@4.10.6` → `npm/eslint-import-resolver-typescript@4.3.4` → `npm/@emnapi/core@1.10.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@emnapi/core@1.10.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `@emnapi/core` is 100.0% likely to have a medium risk anomaly Notes: Primary concern is direct dynamic code execution. `napi_run_script` uses eval() on a string originating from wasm-provided input, and `ee` uses new Function(...) to construct wrapper functions. If the wasm module or its inputs are attacker-controlled, this provides JavaScript code execution in the host context. Aside from these dynamic execution sinks, the remaining code mainly performs wasm memory/table management and worker async orchestration typical of such runtimes, with no clear hardcoded exfiltration or backdoor behavior in this fragment. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/rolldown@1.0.0-rc.17` → `npm/eslint-plugin-import-x@4.10.6` → `npm/eslint-import-resolver-typescript@4.3.4` → `npm/@emnapi/core@1.10.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@emnapi/core@1.10.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `@emnapi/core` is 100.0% likely to have a medium risk anomaly Notes: This module appears to be a legitimate wasm-to-JS/Node-API bridge/runtime, but it contains high-impact dynamic execution capabilities: napi_run_script uses eval() on a string originating from the WASM/handle side, and the binding layer can generate functions via new Function(). It also performs indirect host callback invocation based on runtime handles selected by worker/work-queue control. No explicit exfiltration/backdoor behavior is visible in the provided fragment, so malware likelihood is low, but security risk is moderate-to-high due to host-context code execution if the WASM module or its inputs are not fully trusted. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/rolldown@1.0.0-rc.17` → `npm/eslint-plugin-import-x@4.10.6` → `npm/eslint-import-resolver-typescript@4.3.4` → `npm/@emnapi/core@1.10.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@emnapi/core@1.10.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `@rolldown/binding-wasm32-wasi` is 100.0% likely to have a medium risk anomaly Notes: This loader establishes a Node.js WASI/worker environment that: 1) passes the entire host process.env into the WASI instance (exposing all environment variables, including secrets, to loaded modules); 2) preopens the filesystem root (granting broad file read/write access under the host’s root directory); and 3) implements importScripts via synchronous fs.readFileSync + eval (allowing any local JS file to be executed in the loader context). If an untrusted or compromised WASM module or script is provided, it can read sensitive environment variables, access or modify arbitrary files, and execute arbitrary JavaScript—posing a moderate security risk. Recommended mitigations: restrict WASI preopens to a minimal directory, limit or sanitize environment variables passed into WASI, and replace or sandbox the eval-based importScripts mechanism. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/rolldown@1.0.0-rc.17` → `npm/@rolldown/binding-wasm32-wasi@1.0.0-rc.17` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@rolldown/binding-wasm32-wasi@1.0.0-rc.17`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `@rolldown/binding-wasm32-wasi` is 100.0% likely to have a medium risk anomaly Notes: A JS loader bootstraps a WASI-enabled WebAssembly module and forwards the full host process.env into the WASI environment and worker contexts while preopening the host filesystem root. This design enables an untrusted or tampered WASM binary to read environment variables and access numerous files, potentially exfiltrating data through any available host or network channel. Treat the module as high-risk unless the WASM artifact is from a trusted source; mitigate by restricting preopens to specific directories, avoiding full process.env exposure, and validating the integrity of the WASM binary. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/rolldown@1.0.0-rc.17` → `npm/@rolldown/binding-wasm32-wasi@1.0.0-rc.17` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@rolldown/binding-wasm32-wasi@1.0.0-rc.17`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `rolldown` is 100.0% likely to have a medium risk anomaly Notes: No direct signs of classic malware behavior (e.g., exfiltration/persistence/backdoors) are visible in this JS wrapper. However, it has meaningful security/supply-chain risk characteristics: it can load and execute native code from an environment-controlled path (NAPI_RS_NATIVE_LIBRARY_PATH), and in WebContainer it may execute pnpm to install a binding at runtime before requiring it. The actual maliciousness probability is therefore low-to-moderate for this wrapper, but the execution impact is high if the environment or package supply chain is compromised. Confidence: 1.00 Severity: 0.60 From: packages/kernel-utils/package.json → `npm/rolldown@1.0.0-rc.17` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.0.0-rc.17`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm `undici` is 100.0% likely to have a medium risk anomaly Notes: The code performs an in-place re-encoding of a local file (undici-fetch.js) and overwrites it with latin1-encoded data. There is no evidence of exfiltration, backdoors, or network activity. However, the lack of validation, error handling, and the fact that it can corrupt or permanently alter a source file constitutes a nontrivial risk. In a supply-chain or extension context, such a script could be misused to tamper with code. It is not inherently malicious by itself but is risky and should be restricted or audited before typical usage in a build or runtime environment. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/jsdom@29.1.1` → `npm/undici@7.25.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/undici@7.25.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

github-actions · 2026-05-15T01:51:08Z

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	70.59% ⬇️ -0.83%	8528 / 12081
🔵	Statements	70.4% ⬇️ -0.85%	8667 / 12311
🔵	Functions	71.58% ⬇️ -0.67%	2051 / 2865
🔵	Branches	64.14% ⬇️ -0.93%	3446 / 5372

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
packages/agentmask/src/index.ts	100%	100%	100%	100%
packages/kernel-cli/src/app.ts	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	36-465
packages/kernel-cli/src/commands/daemon-entry.ts	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	13-141
packages/kernel-cli/src/commands/daemon-spawn.ts	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	10-84
packages/kernel-cli/src/commands/relay.ts	90.12% ⬆️ +3.68%	98.03% ⬆️ +1.37%	63.63% ⬆️ +16.97%	93.5% ⬆️ +2.43%	139, 145-151, 202, 209
packages/kernel-node-runtime/src/daemon/rpc-socket-server.ts	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	43-276
packages/kernel-utils/src/libp2p-relay.ts	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	20-221
packages/kernel-utils/src/nodejs/index.ts	100% 🟰 ±0%	100% 🟰 ±0%	100% 🟰 ±0%	100% 🟰 ±0%
packages/kernel-utils/src/nodejs/libp2p-relay-home.ts	100%	100%	100%	100%
packages/llm-bridge/src/conversation.ts	96.66%	78.57%	100%	96.66%	152
packages/llm-bridge/src/index.ts	0%	0%	0%	0%	36-85
packages/llm-bridge/src/openclaw-client.ts	94.44%	100%	75%	100%	76
packages/llm-bridge/src/protocol.ts	0%	100%	100%	0%	26-86
packages/llm-bridge/src/run-bridge.ts	0%	0%	0%	0%	53-184
packages/ocap-kernel/src/index.ts	100% 🟰 ±0%	100% 🟰 ±0%	100% 🟰 ±0%	100% 🟰 ±0%
packages/ocap-kernel/src/remotes/kernel/OcapURLManager.ts	100% 🟰 ±0%	100% 🟰 ±0%	100% 🟰 ±0%	100% 🟰 ±0%
packages/ocap-kernel/src/vats/VatManager.ts	100% 🟰 ±0%	100% 🟰 ±0%	100% 🟰 ±0%	100% 🟰 ±0%
packages/sample-services/src/cluster-config.ts	100%	100%	100%	100%
packages/sample-services/src/index.ts	100%	100%	100%	100%
packages/sample-services/src/echo-service/index.ts	0%	0%	0%	0%	18-76
packages/sample-services/src/echo-service/service.ts	0%	0%	0%	0%	4-24
packages/sample-services/src/random-number-service/index.ts	0%	0%	0%	0%	21-79
packages/sample-services/src/random-number-service/service.ts	0%	0%	0%	0%	4-56
packages/sample-services/src/vat-lib/contact-endpoint.ts	0%	0%	0%	0%	60-101
packages/sample-services/src/vat-lib/describe.ts	0%	100%	0%	0%	21-25
packages/sample-services/src/vat-lib/index.ts	100%	100%	100%	100%
packages/sample-services/src/vat-lib/matcher-registration.ts	0%	0%	0%	0%	39-70
packages/sample-services/src/vat-lib/registration-token.ts	0%	0%	0%	0%	24-37
packages/service-discovery-types/src/contact.ts	100%	100%	100%	100%
packages/service-discovery-types/src/index.ts	100%	100%	100%	100%
packages/service-discovery-types/src/matcher.ts	100%	100%	100%	100%
packages/service-discovery-types/src/method-schema-convert.ts	94.11%	86.36%	100%	94.11%	54-55
packages/service-discovery-types/src/service-description.ts	100%	100%	100%	100%
packages/service-matcher/src/cluster-config.ts	100%	100%	100%	100%
packages/service-matcher/src/index.ts	100%	100%	100%	100%
packages/service-matcher/src/matcher-vat/index.ts	87.5%	67.74%	90.62%	88.59%	125-127, 151, 182-184, 238-246, 275, 282, 307, 312-314, 344-346, 365-367, 385, 407, 560-563, 604, 614, 637-639

Generated in workflow #4422 for commit 9f0e86d by the Vitest Coverage Report Action

Pre-redemption of the configured matcher URL was fire-and-forget, so a tool call landing during the redemption window would see a misleading 'no matcher connection' error from requireMatcher. Park the pending promise in state.matcherPending and have requireMatcher await it, surfacing the underlying failure when redemption rejects.

… discovery/daemon.ts Both OpenClaw plugins kept a near-identical copy of the daemon caller; the discovery version added optional ocapHome support, so a future fix in one copy would drift from the other. Sync the two files (metamask now accepts the same optional ocapHome param, even though it does not use it today) and add a header note instructing future editors to keep them in sync. Plugins remain self-contained so 'openclaw plugins install -l' still works on either directory in isolation.

sirtimid

A batch of type-design and error-handling suggestions surfaced by a multi-agent review pass. Each is non-blocking but cheap to address now.

- ocap-kernel(OcapURLManager): propagate OcapURL{Issuer,Redemption}Service through getServices / getIssuerService / getRedemptionService - service-discovery-types(matcher): add _AssertSameShape drift guards for ServiceQuery and ServiceMatch - service-discovery-types(contact): tag ContactResponse with a 'kind' discriminator so a ServicePoint whose API happened to define credentialSpec / requiredCertifications can't be misclassified; update sample-services and the discovery plugin to match - kernel-utils(libp2p-relay): type tersePeer / terseAddr with PeerId and Multiaddr instead of any - kernel-node-runtime(rpc-socket-server): narrow unlink catch to ENOENT so EPERM/EBUSY/EISDIR surface instead of becoming opaque EADDRINUSE from the subsequent listen() - llm-bridge(conversation): commit user turn to persistent history only after the assistant reply lands; a failed client.chat would otherwise leave an unpaired user turn and corrupt the next ingest - service-matcher(matcher-vat): distinguish 'all bridge-cited ids unknown' from 'no matches' — the former throws so a hallucinating ranker is loud, not silent - discovery plugin(state): collapse matcher + matcherPending into a discriminated MatcherSlot ('absent' | 'pending' | 'resolved') so the type system rules out the contradictory both-set state - discovery + metamask plugins: replace hand-rolled safeParse with a superstruct wrapper per CLAUDE.md conventions, eliminating the per-field typeof ladder and the KNOWN_KEYS drift hazard

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 91440a1. Configure here.}

@libp2p/interface declares Multiaddr but does not re-export it, so the build failed under the stricter library check in CI. Import it from its authoritative module and declare the dependency explicitly.

CapData bodies are smallcaps-encoded JSON with a leading '#' marker, so the previous JSON.parse(body) always threw and the catch returned undefined — making 'kind !== public' true for every response and rejecting every public contact as non-public. Match the kind field by regex against the raw body, the same way extractKref reaches into it.

rekmarks and others added 30 commits May 14, 2026 17:48

docs: Tweak demo-two-way-comms.md

a62a296

feat: legible relay status output

15ac7d6

feat: add @ocap/service-discovery-types package and URL endowment types

23e15b4

feat: add @ocap/service-matcher package

3fd6338

fix: register vat with subcluster before awaiting runVat

4c0bd3c

chore: enable tsx in sandbox

f86840f

feat: add @openclaw/discovery plugin with validation plan

18fa135

feat(kernel-cli): add --home flag for per-invocation OCAP_HOME

31343ad

feat(discovery): ocapHome config and validation refinements

5bddbbd

feat(matcher): durable publicFacet kref for stable OCAP URL

26c9658

refactor(relay): use ~/.libp2p-relay as own home, not OCAP_HOME

4c98195

docs(VALIDATION): fix prettier-mangled sanity-check sentence

79c5668

fix(matcher): durable-kind behavior calling convention

d0d650b

docs(VALIDATION): cold start vs in-place update; matcher bundle relaunch

2e39429

feat(relay): announce configured public IP via LIBP2P_RELAY_PUBLIC_IP

2b6b588

feat(daemon): refuse to start if another daemon is alive under same O…

005e9ce

…CAP_HOME

feat(matcher): keyword/method-name overlap ranker

a5207a9

docs(discovery-plan): note browser-extension lifetime issue

963d545

feat(service-matcher): add reset-everything.sh for VPS-side test cycles

bc98a05

feat: add @ocap/llm-bridge package and integrate with matcher

90586a0

docs(VALIDATION): locate openclaw config, reuse existing gateway token

c2a623b

feat(llm-bridge): log every prompt and reply to the bridge log file

1f67b41

refactor: rename OCAP_MATCHER_URL to MATCHER_OCAP_URL

86c9c67

docs(VALIDATION): untangle prereq-2 indentation

ff523f7

feat: extract Echo and RandomNumber into @ocap/sample-services package

f4f1d9a

docs(VALIDATION): reflect sample-services move out of the extension

8f6ac5d

chore: align chip-side package versions with main after rebase

a0fdefa

FUDCo added 3 commits May 14, 2026 17:48

sample-services: split reset scripts between matcher and laptop hosts

0f90bbe

fix(scripts): guard empty arrays under set -u; opt sample-service vat…

f38edfa

…s into crypto

feat(service-matcher): dedup re-registrations by (peerId, providerTag)

3a023a1

docs: Update changelogs

bd1868d

FUDCo marked this pull request as ready for review May 15, 2026 06:48

FUDCo requested a review from a team as a code owner May 15, 2026 06:48

cursor Bot reviewed May 15, 2026

View reviewed changes

Comment thread packages/agentmask/openclaw-plugin-discovery/index.ts

Comment thread packages/agentmask/openclaw-plugin-metamask/daemon.ts

FUDCo added 2 commits May 15, 2026 11:45

sirtimid reviewed May 18, 2026

View reviewed changes

Comment thread discovery-plan.md Outdated

Remove working doc file that accidentally got committed.

e046f8d

cursor Bot reviewed May 19, 2026

View reviewed changes

Comment thread packages/agentmask/openclaw-plugin-discovery/index.ts

sirtimid reviewed May 21, 2026

View reviewed changes

Comment thread packages/kernel-utils/src/libp2p-relay.ts Outdated

sirtimid reviewed May 21, 2026

View reviewed changes

cursor Bot reviewed May 26, 2026

View reviewed changes

Comment thread packages/agentmask/openclaw-plugin-discovery/tools/initiate-contact.ts

FUDCo added 2 commits May 26, 2026 14:08

fix(kernel-utils): import Multiaddr from @multiformats/multiaddr

968b095

@libp2p/interface declares Multiaddr but does not re-export it, so the build failed under the stricter library check in CI. Import it from its authoritative module and declare the dependency explicitly.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: agentmask + service discovery infrastructure#952

feat: agentmask + service discovery infrastructure#952
FUDCo wants to merge 40 commits into
mainfrom
chip/agentmask

FUDCo commented May 15, 2026 •

edited by cursor Bot

Loading

Uh oh!

socket-security Bot commented May 15, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented May 15, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented May 15, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

sirtimid left a comment •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

FUDCo commented May 15, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

socket-security Bot commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Coverage Report

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

sirtimid left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

FUDCo commented May 15, 2026 •

edited by cursor Bot

Loading

socket-security Bot commented May 15, 2026 •

edited

Loading

socket-security Bot commented May 15, 2026 •

edited

Loading

github-actions Bot commented May 15, 2026 •

edited

Loading

sirtimid left a comment •

edited

Loading