2.1 KiB
2.1 KiB
INSTALL
Purpose
This file is the shortest installation and verification guide for another engineering-focused agent.
Use this when you want to apply the current Telegram/OpenClaw PoC to the openclawtest environment without reading the entire project history first.
Target environment
Current supported target:
openclawtest- Telegram-only
This is not yet a general package installer for arbitrary environments.
Prerequisites
- access to this repo
- access to the
openclawtestenvironment on the same machine - permission to run the provided scripts
Install / refresh
Fastest path:
bash scripts/install-openclawtest-poc.sh
This does two things:
- refreshes the live
openclawtestPoC by reapplying the patch and restarting the gateway - runs a verification pass over the live state and runtime markers
Manual paths
Apply patch only
bash scripts/apply-openclaw-poc-patch.sh /home/openclawtest/.nvm/versions/node/v22.22.2/lib/node_modules/openclaw/dist
Refresh live openclawtest runtime
bash scripts/refresh-openclawtest-poc.sh
Verify current live state
bash scripts/verify-openclaw-poc.sh \
/home/openclawtest/.openclaw \
/home/openclawtest/.nvm/versions/node/v22.22.2/lib/node_modules/openclaw/dist
Rollback
bash scripts/rollback-openclaw-poc-patch.sh /home/openclawtest/.nvm/versions/node/v22.22.2/lib/node_modules/openclaw/dist
What success looks like
After install/refresh:
- gateway is running
- patch markers exist in the live OpenClaw dist files
- Telegram assistant replies can show reply-end buttons
- clicking buttons can update state and UI
Validation checklist
- Send a Telegram assistant reply through
openclawtest - Confirm buttons appear
- Click
continueorstop - Confirm state/debug files appear or update:
~/.openclaw/reply-end-controls.json~/.openclaw/reply-end-debug.log
- For stop-state validation, send a later message and confirm the assistant becomes more restrained
Read next if needed
HANDOFF.mdINTEGRATION.mdreports/final-readiness-report.md