mirror of
https://github.com/Heretek-AI/openclaw.git
synced 2026-07-23 00:25:31 -04:00
Tabula Myriad
a9ae1a6778
Matrix Protocol: - docker-compose.matrix.yml: Dendrite homeserver + PostgreSQL + Nginx TLS - src/channels/plugins/matrix-channel.ts: OpenClaw plugin implementation - docs/matrix-triad-setup.md: Setup guide with auth scheme (@tm1-4:triad.local) MCP Server Integration: - docs/mcp-triad-integration.md: SearXNG, Playwright, GitHub MCP configs - docs/mcp-curiosity-mapping.md: Gap-to-capability mapping Node Sync Architecture: - src/services/node-sync-service.ts: WebSocket peer sync + presence detection - src/services/node-sync-service.test.ts: Unit tests - docs/node-sync-architecture.md: Architecture docs Triad Resilience: - scripts/triad-corruption-check.mjs: SQLite + log + config + git integrity - docs/triad-resilience.md: Recovery procedures - .secure/deployment-logs/README.md: Schema v2 - skills/triad-heartbeat/SKILL.md: Corruption check integration NPM Publish Workflow: - scripts/npm-publish.mjs: version, changelog, validate, publish, rollback - .github/workflows/npm-publish.yml: GitHub Actions with provenance - docs/npm-publish-guide.md: Complete documentation All deliverables tested in Docker before production.
1.4 KiB
Executable File
1.4 KiB
Executable File
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| RPC adapters for external CLIs (signal-cli, legacy imsg) and gateway patterns |
|
RPC Adapters |
RPC adapters
OpenClaw integrates external CLIs via JSON-RPC. Two patterns are used today.
Pattern A: HTTP daemon (signal-cli)
signal-cliruns as a daemon with JSON-RPC over HTTP.- Event stream is SSE (
/api/v1/events). - Health probe:
/api/v1/check. - OpenClaw owns lifecycle when
channels.signal.autoStart=true.
See Signal for setup and endpoints.
Pattern B: stdio child process (legacy: imsg)
Note: For new iMessage setups, use BlueBubbles instead.
- OpenClaw spawns
imsg rpcas a child process (legacy iMessage integration). - JSON-RPC is line-delimited over stdin/stdout (one JSON object per line).
- No TCP port, no daemon required.
Core methods used:
watch.subscribe→ notifications (method: "message")watch.unsubscribesendchats.list(probe/diagnostics)
See iMessage for legacy setup and addressing (chat_id preferred).
Adapter guidelines
- Gateway owns the process (start/stop tied to provider lifecycle).
- Keep RPC clients resilient: timeouts, restart on exit.
- Prefer stable IDs (e.g.,
chat_id) over display strings.