Repository navigation
v0.6.8
/newon chat platforms now starts plan mode clean (#67).- Before: on Telegram and other chat platforms, the first
/planafter/newcontinued a finished plan. Its card
said "Approve plan rev 2", and the agent first read the old plan file. Approval itself was always correct: the card
named the new file, and the new plan was what got approved. - The fix: an unbound gateway reset now also finds finished plans, through a bounded index of the 256 most recent
session states. - Upgrading: plans that finished before the upgrade are added to that index once, at the first reset.
- Unchanged: same-session re-entry still keeps its plan history; approval logic and rule keys are untouched.
- Before: on Telegram and other chat platforms, the first
- README: the approval card's buttons were clicked on Telegram. In two runs on a Hermes v0.21.7 gateway, a real click
approved plans that were then implemented in the same turn (#31).
Not proven yet: the live gateway path. The Telegram /new repro from #67 runs again on a test agent with this release.
Install or update: hermes plugins install 100yenadmin/hermes-plan-mode --ref v0.6.8.