[idea] preserve permissions (--yolo) on agent restart #1308
Closed
johnlazar-x
started this conversation in
Ideas
Replies: 2 comments
|
I have a working fork implementation on branch feature/preserve-agent-resume-access (https://github.com/johnlazar-x/herdr/tree/feature/preserve-agent-resume-access). It persists allow-listed permission arguments for Codex, Claude Code, Copilot CLI, and OpenCode, then reapplies them during native session restore. I will only open a PR if this direction is approved and an issue/approval path is provided. |
0 replies
|
I've added detection of the model used and attempting to restore the agent back to that model and compute budget |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
idea / problem
Herdr correctly restores supported agent conversations after a server restart, but it resumes them without the permission/access mode they were launched with. For example, a Codex pane started with codex --yolo resumes as codex resume , which can reintroduce approval prompts and change the agent’s effective access.
requested change
Persist a safe, allow-listed per-pane permission profile with the native agent session reference and reapply it when Herdr performs native session restore.
This should cover documented permission controls for Codex, Claude Code, Copilot CLI, and OpenCode, while excluding arbitrary argv, config overrides, environment variables, and secrets. Unknown or unsupported values should fail closed to the provider’s normal safe behavior.
why you want this
Long-running multi-agent workspaces become unreliable after planned restarts, updates, host reboots, or reconnects: agents return to the right conversation but no longer have the same operating mode. Preserving explicit launch permissions would make restart behavior deterministic while retaining a narrow, auditable security boundary.
All reactions