zhi/HarborForge.OpenclawPlugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: wakeup message says 'continue in same session', not 'only reply WAKEUP_OK' #9

Merged
hzhang merged 1 commits from fix/wakeup-message-no-ack-only into main 2026-05-21 10:05:34 +00:00
Conversation 0 Commits 1 Files Changed 2 +17 -6
hzhang commented 2026-05-21 10:05:29 +00:00
Contributor
Copy Link

E2e of init-hf-project exposed an ack-only trap in the wakeup message text. The original phrasing — "Follow the hf-wakeup workflow … Only reply WAKEUP_OK in this session." — contradicts itself; MiniMax-M2.5 obeys the literal only and stops after the ack. The scheduler re-wakes every 30s because the slot stays not_started, and the agent ack-loops forever (3 consecutive WAKEUP_OK-only replies for slot 7 in dind-t2).

Rewrites the message to be unambiguous: first-line WAKEUP_OK ack, then continue the workflow in the SAME session (calendar_status → task → sub-workflow → calendar_complete/abort), with an explicit warning that stopping after the ack leaves the slot stuck in not_started.

Version 0.3.3 → 0.3.4.

🤖 Generated with Claude Code

E2e of `init-hf-project` exposed an ack-only trap in the wakeup message text. The original phrasing — `"Follow the hf-wakeup workflow … Only reply WAKEUP_OK in this session."` — contradicts itself; MiniMax-M2.5 obeys the literal `only` and stops after the ack. The scheduler re-wakes every 30s because the slot stays `not_started`, and the agent ack-loops forever (3 consecutive WAKEUP_OK-only replies for slot 7 in dind-t2). Rewrites the message to be unambiguous: first-line `WAKEUP_OK` ack, then continue the workflow in the SAME session (calendar_status → task → sub-workflow → calendar_complete/abort), with an explicit warning that stopping after the ack leaves the slot stuck in `not_started`. Version 0.3.3 → 0.3.4. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
hzhang added 1 commit 2026-05-21 10:05:29 +00:00
fix(plugin): wakeup message says 'continue in same session', not 'only reply WAKEUP_OK' 102809dc2a 
E2e showed the old wakeup text trapped agents in an ack-only loop:

> "You have due slots. Follow the `hf-wakeup` workflow of skill
>  `hf-hangman-lab` to proceed. Only reply `WAKEUP_OK` in this session."

The two clauses contradicted each other — "follow the workflow" vs
"only reply WAKEUP_OK". MiniMax-M2.5 prioritised the literal "only"
and never proceeded past the ack; the scheduler then re-woke every 30s
because the slot stayed `not_started`, and the agent kept re-acking
forever (verified: 3 consecutive WAKEUP_OK-only replies across slot 7).

Rewrites the wakeup message to be explicit:
  - first line MUST be `WAKEUP_OK` (the ack token the plugin looks for)
  - then continue IN THE SAME session: drive calendar_status → task
    fetch → sub-workflow → calendar_complete/abort
  - flags the loop trap so the agent knows what to avoid

Bumps version 0.3.3 → 0.3.4.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hzhang merged commit 2a2a298d15 into main 2026-05-21 10:05:34 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
nav orion river zhi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: zhi/HarborForge.OpenclawPlugin#9
Delete Branch "fix/wakeup-message-no-ack-only"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?