docs: add bridge config example

This commit is contained in:
Haitao Pan 2026-04-10 08:46:04 +08:00
parent 7f180e0f02
commit 72cef71ff8
2 changed files with 48 additions and 1 deletions

View File

@ -8,7 +8,12 @@
- ACP stdio bridge entrypoint
- Go helper runtime packages used by the ACP bridge
- Unit tests for bridge routing, RPC contracts, mounts, runtime dispatch, and provider sync
- Architecture notes and public ingress topology docs in [docs/architecture/acp-forwarding-topology.md](/Users/shenlan/workspaces/cloud-neutral-toolkit/xworkmate-bridge/docs/architecture/acp-forwarding-topology.md)
## ACP Forwarding Topology
This repository exposes one bridge entrypoint and forwards to four verified public targets. The full Mermaid diagram lives in [docs/architecture/acp-forwarding-topology.md](/Users/shenlan/workspaces/cloud-neutral-toolkit/xworkmate-bridge/docs/architecture/acp-forwarding-topology.md).
Example provider sync config: [example/config.yaml](/Users/shenlan/workspaces/cloud-neutral-toolkit/xworkmate-bridge/example/config.yaml)
## Compatibility

42
example/config.yaml Normal file
View File

@ -0,0 +1,42 @@
# Example configuration for xworkmate-bridge public ingress and provider sync.
# The bridge itself validates inbound requests with:
# Authorization: Bearer ${ACP_AUTH_TOKEN}
# Each external provider can also carry its own outbound Authorization header.
bridge:
listenAddr: 127.0.0.1:8787
authToken: ${ACP_AUTH_TOKEN}
allowedOrigins:
- https://xworkmate.svc.plus
- http://localhost:*
- http://127.0.0.1:*
providers:
- providerId: openclaw
label: OpenClaw
endpoint: wss://openclaw.svc.plus
authorizationHeader: Bearer ${OPENCLAW_AUTH_TOKEN}
enabled: true
- providerId: codex
label: Codex
endpoint: https://acp-server.svc.plus/codex/acp/rpc
authorizationHeader: Bearer ${CODEX_AUTH_TOKEN}
enabled: true
- providerId: opencode
label: OpenCode
endpoint: https://acp-server.svc.plus/opencode/acp/rpc
authorizationHeader: Bearer ${OPENCODE_AUTH_TOKEN}
enabled: true
- providerId: gemini
label: Gemini
endpoint: https://acp-server.svc.plus/gemini/acp/rpc
authorizationHeader: Bearer ${GEMINI_AUTH_TOKEN}
enabled: true
notes:
- The bridge reads its own auth token from ACP_AUTH_TOKEN.
- The provider catalog is normally synced through xworkmate.providers.sync.
- session.message should resend routing on follow-up turns for codex and opencode.