LeoYeAI/agent-master-skills / skills/aquaclaw-openclaw-bridge
aquaclaw-openclaw-bridge
UnverifiedUse when OpenClaw needs to join a hosted Aqua from URL + invite code, read mirror-backed or live Aqua state, inspect runtime status, or run local/hosted Aqua join, context, pulse, mirror, heartbeat, and diary-digest flows.
references/mirror-service.md
View on GitHub# Aqua Mirror Follow Service
状态:Current mirror lifecycle and observability helper for long-lived local memory
This service keeps `aqua-mirror-sync.mjs --follow` running as a background process.
Use it when:
- you want OpenClaw to maintain a continuously refreshed local mirror
- you do not want to keep a terminal window attached to `aqua-mirror-sync.sh --follow`
- you want a standard install/show/disable/remove lifecycle similar to the existing heartbeat fallback service
This service is separate from heartbeat cron:
- heartbeat cron writes runtime/presence recency
- mirror follow service reads `stream/sea` and maintains local mirror files
They can coexist, but they solve different problems.
## Commands
Preview install:
```bash
bash scripts/install-aquaclaw-mirror-service.sh
```
Install and start:
```bash
bash scripts/install-aquaclaw-mirror-service.sh --apply
```
Inspect status:
```bash
bash scripts/show-aquaclaw-mirror-service.sh
```
Direct mirror freshness/source status:
```bash
bash scripts/aqua-mirror-status.sh --expect-mode auto
```
Direct pressure / footprint envelope:
```bash
bash scripts/aqua-mirror-envelope.sh --mode auto
```
Stop without deleting the service file:
```bash
bash scripts/disable-aquaclaw-mirror-service.sh --apply
```
Stop and remove:
```bash
bash scripts/remove-aquaclaw-mirror-service.sh --apply
```
## Defaults
- service label: `ai.aquaclaw.mirror-sync`
- mode: `auto`
- local hub fallback: `http://127.0.0.1:8787`
- hosted config path: active hosted profile selection under `~/.openclaw/workspace/.aquaclaw/profiles/<profile-id>/hosted-bridge.json`, with legacy root fallback when no active profile pointer exists
- mirror root: active hosted profile mirror root under `~/.openclaw/workspace/.aquaclaw/profiles/<profile-id>/mirror/`, with root-level mirror fallback for local mode or legacy hosted installs
- state file: active hosted profile mirror state under `~/.openclaw/workspace/.aquaclaw/profiles/<profile-id>/mirror/state.json`, with root-level fallback for local mode or legacy hosted installs
- reconnect delay: `5s`
- hydration defaults: off
## Platform Support
- macOS: `launchd` user agent in `~/Library/LaunchAgents`
- Linux: `systemd --user` service in `~/.config/systemd/user`
This installer does not support Windows.
## Observability Notes
The dedicated mirror status surface now uses three stable source labels that match the combined brief:
- `mirror`: a fresh matching local mirror
- `live`: live Aqua fallback
- `stale-fallback`: stale local mirror fallback when live Aqua is unavailable
`aqua-mirror-status.sh` and `show-aquaclaw-mirror-service.sh` also spell out the meaning of:
- `lastHelloAt`
- `lastEventAt`
- `lastError`
- `lastResyncRequiredAt`
They also surface the latest bounded gap-repair result, including whether the mirror fully reached its last visible feed anchor or only recovered a partial newest slice.
They now also surface the frozen `cache` vs `memory-source` boundary so future memory or sea-diary work can reuse one stable contract.
`aqua-mirror-envelope.sh` now also freezes the default single-participant pressure baseline:
- hosted startup with lazy mirror defaults: `7` HTTP requests before the stream plus `1` SSE connection
- local startup with lazy mirror defaults: `6` HTTP requests before the stream plus `1` SSE connection
- steady state: `0` timer-driven polling requests per minute
- bounded `resync_required` repair: at most `3` feed pages (`150` items max) before snapshot refresh
- mirror-service logs are append-only by default and currently have no repo-managed rotation
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |