Last updated: 2026-02-16 Status: Not started
- GitHub repo
https://github.com/jonslimak/luojiis the source of truth. - Target machine agent performs installation and configuration work.
- Planning/review can happen on this machine, but status docs are updated in GitHub by the target machine workflow.
- Target machine updates these files each milestone:
plan.mdtask.mdprogress.txt
- Never commit secrets. Log only status/evidence and redact sensitive values.
- Milestone 0 - Repo and rollback baseline
- Milestone 1 - Local secure vertical slice
- Milestone 2 - Remote access via Tailscale Serve
- Milestone 3 - Telegram channel flow
- Milestone 4 - Model flexibility path
- Milestone 5 - Operational hardening and updates
- Keep implementation simple.
- Complete one milestone before expanding scope.
- Use soft gate review at the end of each milestone.
- Create a rollback point after each passed milestone.
- M0-T1: Initialize local git repo (if missing) and connect to
https://github.com/jonslimak/luoji. - M0-T2: Install Codex on the target machine and clone the same GitHub repo there.
- M0-T3: Validate target machine can pull and push to origin.
- M0-T4: Set default branch strategy and branch naming (
codex/<purpose>). - M0-T5: Create release note template for milestone tags.
- M0-T6: Create baseline tag (
vYYYY.MM.DD-1) before setup work. - M0-T7: Run dry-run rollback command and confirm it works.
Verification:
- M0-V1:
git remote -vshows expected origin. - M0-V2: Target machine can push a non-secret docs update.
- M0-V3: Baseline tag exists in
git tag. - M0-V4: Rollback dry-run command is documented and tested.
Soft gate decision:
- M0-GATE: Proceed / Pause (case by case)
- M1-T1: Install OpenClaw via official installer.
- M1-T2: Run
openclaw onboard --install-daemon. - M1-T3: Confirm local mode and loopback bind.
- M1-T4: Confirm gateway auth token is enabled.
- M1-T5: Configure OpenAI provider and primary model.
- M1-T6: Open Control UI and run first successful chat.
- M1-T7: Run
openclaw doctorand address blocking issues.
Verification:
- M1-V1:
openclaw gateway statusis healthy. - M1-V2:
openclaw healthis healthy. - M1-V3:
openclaw models statusconfirms OpenAI auth. - M1-V4: Control UI test message succeeds.
Soft gate decision:
- M1-GATE: Proceed / Pause (case by case)
Rollback point:
- M1-R1: Commit docs/changes (non-secret only).
- M1-R2: Create milestone tag and release note.
- M2-T1: Install and authenticate Tailscale on Mac mini.
- M2-T2: Configure OpenClaw for Tailscale Serve mode.
- M2-T3: Confirm gateway remains loopback-bound.
- M2-T4: Validate remote Control UI from second tailnet device.
- M2-T5: Run security audit and fix critical findings.
Verification:
- M2-V1: Remote UI session works over tailnet.
- M2-V2: No direct LAN/public gateway exposure.
- M2-V3:
openclaw security audithas no unresolved critical issues.
Soft gate decision:
- M2-GATE: Proceed / Pause (case by case)
Rollback point:
- M2-R1: Commit docs/changes (non-secret only).
- M2-R2: Create milestone tag and release note.
- M3-T1: Create Telegram bot token in BotFather.
- M3-T2: Configure Telegram channel in OpenClaw.
- M3-T3: Keep
dmPolicyas pairing. - M3-T4: Keep group mention requirement enabled.
- M3-T5: Approve first pairing code.
- M3-T6: Validate DM and group mention behavior.
Verification:
- M3-V1: Pairing list and approve flow works.
- M3-V2: Approved DM user receives responses.
- M3-V3: Group replies follow mention rule as expected.
- M3-V4: Logs show no recurring delivery errors.
Soft gate decision:
- M3-GATE: Proceed / Pause (case by case)
Rollback point:
- M3-R1: Commit docs/changes (non-secret only).
- M3-R2: Create milestone tag and release note.
- M4-T1: Confirm stable OpenAI primary model.
- M4-T2: Add fallback model configuration plan.
- M4-T3: Document provider switch procedure (OpenAI to Anthropic/others).
- M4-T4: Validate config with
openclaw models status.
Verification:
- M4-V1: Current OpenAI model remains stable.
- M4-V2: Fallback config is valid and visible.
- M4-V3: Provider switch procedure is clear and testable.
Soft gate decision:
- M4-GATE: Proceed / Pause (case by case)
Rollback point:
- M4-R1: Commit docs/changes (non-secret only).
- M4-R2: Create milestone tag and release note.
- M5-T1: Define weekly maintenance checklist.
- M5-T2: Perform one controlled update cycle: pre-update tag -> update -> doctor -> restart -> health check -> post-update tag.
- M5-T3: Test rollback to previous milestone tag and confirm recovery.
Verification:
- M5-V1: Update cycle completed without regressions.
- M5-V2: Rollback test succeeded.
- M5-V3: Maintenance checklist is documented and usable.
Soft gate decision:
- M5-GATE: Proceed / Pause (case by case)
Rollback point:
- M5-R1: Commit docs/changes (non-secret only).
- M5-R2: Create milestone tag and release note.
- C1: Auth mismatch check completed (token/scope status confirmed).
- C2: Pairing and mention policy validated before deeper debugging.
- C3: Telegram privacy mode and numeric IDs validated.
- C4:
openclaw doctorrun after setup/config changes. - C5:
openclaw security auditrun before remote/channel expansion. - C6: Tag created for each accepted milestone.