Summary
When a session is archived and later resumed, HAPI does not preserve the previous permission mode.
A common example is YOLO mode:
- Switch the session to YOLO
- Archive / pause the session
- Resume it later by sending a new message
- The resumed session runs in
default again instead of the previous permission mode
Why this is painful
If the user expects the previous mode to continue, the model starts running with the wrong permission mode immediately. Then the user has to:
- stop the agent
- change the permission mode again
- resend / continue
That wastes time and tokens.
Expected behavior
HAPI should remember the last active permission mode for the session and restore it automatically when resuming the archived session.
That should apply both to:
- mode changes made during the session
- sessions originally started in YOLO mode
Notes
From the current behavior, the permission mode appears to be kept only in live session state, not persisted as resume-time preference.
Summary
When a session is archived and later resumed, HAPI does not preserve the previous permission mode.
A common example is YOLO mode:
defaultagain instead of the previous permission modeWhy this is painful
If the user expects the previous mode to continue, the model starts running with the wrong permission mode immediately. Then the user has to:
That wastes time and tokens.
Expected behavior
HAPI should remember the last active permission mode for the session and restore it automatically when resuming the archived session.
That should apply both to:
Notes
From the current behavior, the permission mode appears to be kept only in live session state, not persisted as resume-time preference.