| .github | ||
| docs | ||
| example | ||
| internal | ||
| scripts | ||
| .dockerignore | ||
| .gitignore | ||
| AGENTS.md | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| main_test.go | ||
| main_tools.go | ||
| main.go | ||
| Makefile | ||
| README.md | ||
XWorkmate Bridge
xworkmate-bridge is the standalone repository for the XWorkmate ACP Bridge Server and the embedded Go helper previously stored under xworkmate-app/go/go_core.
What lives here
- ACP Bridge HTTP/WebSocket server
- 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
ACP Forwarding Topology
This repository exposes one APP-facing bridge entrypoint and proxies traffic
to four independent upstream production services. The APP-facing canonical ACP
paths remain /acp/rpc and /acp under
https://xworkmate-bridge.svc.plus.
Architecture topology: docs/architecture/acp-forwarding-topology.md
ADR for the unified APP-facing bridge contract: docs/architecture/adr-unified-bridge-entrypoints.md
Example provider sync config: example/config.yaml
API reference: docs/api-reference.md
Compatibility
For compatibility with xworkmate-app, the built helper binary name remains xworkmate-go-core.
Commands
make test
make build
./build/bin/xworkmate-go-core serve --listen 127.0.0.1:8787
GitHub Actions
This repository includes one GitHub Actions pipeline with four stages:
prep: Go static checksbuild: build thelinux/amd64artifact for the x86 target host and upload itdeploy: run Ansible CD withx-evor/playbooksvalidate: verify the public endpoints after deployment
GitHub Releases are published only after deploy and validate both succeed.
In this repository, a published Release means the built image has been deployed
to xworkmate-bridge.svc.plus and passed post-deploy validation there.
Deploy stage
The deploy stage checks out:
- this service repository into
xworkmate-bridge/ - the
x-evor/playbooksrepository intoplaybooks/
Then it runs playbooks/deploy_xworkmate_bridge_vhosts.yml, which builds the service for linux/amd64 and deploys it to the target host with Ansible.
Validate stage
The validate stage proves production alignment against the bridge public contract:
- bridge root and
/api/ping - strict image / tag / commit / version match against the built image ref
- upstream ACP capability probes for
codex,opencode, andgemini - minimal
session.startsmoke tests throughhttps://xworkmate-bridge.svc.plus/acp/rpc
Required GitHub secrets:
SINGLE_NODE_VPS_SSH_PRIVATE_KEY: private key used by the Actions runner to SSH into the target hostWORKSPACE_REPO_TOKEN: token with access to checkoutx-evor/playbooks
Optional GitHub secrets:
SSH_KNOWN_HOSTS: pre-seeded known_hosts content for stricter host verification
Optional workflow input:
internal_service_token: manual dispatch input that is forwarded to Ansible asINTERNAL_SERVICE_TOKEN
Environment
ACP_LISTEN_ADDR: listen address forservemode, default127.0.0.1:8787OUTPUT_DIR: optional output directory formake buildOUTPUT_PATH: optional explicit build path formake build