Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: “Allow always” popup approval does not persist for subsequent exec commands [1 pull requests, 6 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59847•Fetched 2026-04-08 02:39:50
View on GitHub
Comments
6
Participants
4
Timeline
19
Reactions
0
Author
ericshenyiericshenyi
Participants
11687841168784chearmstrongchearmstrongericshenyiericshenyilpflhhlpflhh
Timeline (top)
commented ×6cross-referenced ×3mentioned ×3subscribed ×3

Here’s a clean bug report draft you can paste:

Title: “Allow always” approval in popup does not persist for subsequent exec commands

OpenClaw version

  • OpenClaw 2026.3.31

Environment

  • Surface: webchat
  • Runtime: direct
  • Host: gateway
  • OS: Windows
  • Shell: PowerShell
  • Model session observed from: openai-codex/gpt-5.4

Summary When an exec approval popup appears and I click Allow always, the next exec command still requires approval again. This suggests approval persistence is not being honored.

Steps to reproduce

  1. Trigger an exec command that requires approval, for example: 
    python --version
  2. In the popup, click Allow always
  3. Trigger the same command again: 
    python --version

Expected behavior

  • After choosing Allow always, the second identical command should run without prompting for approval again.

Actual behavior

  • The second identical command still triggers a fresh approval request.

Observed session evidence First command:

  • Command: 
    python --version
  • Result: 
    Python 3.14.3

Second command:

  • Same command: 
    python --version
  • Result: 
    Python 3.14.3
  • But it still required another approval prompt before running.

Notes

  • This may be a popup/UI approval persistence bug or a gateway approval-state bug.
  • There may also be a mismatch between popup approval state and chat/tool-visible approval state.

Impact

  • Repetitive approvals for harmless repeated commands
  • “Allow always” appears misleading or non-functional
  • Makes automation flows much more cumbersome

Root Cause

Here’s a clean bug report draft you can paste:

Title: “Allow always” approval in popup does not persist for subsequent exec commands

OpenClaw version

  • OpenClaw 2026.3.31

Environment

  • Surface: webchat
  • Runtime: direct
  • Host: gateway
  • OS: Windows
  • Shell: PowerShell
  • Model session observed from: openai-codex/gpt-5.4

Summary When an exec approval popup appears and I click Allow always, the next exec command still requires approval again. This suggests approval persistence is not being honored.

Steps to reproduce

  1. Trigger an exec command that requires approval, for example: 
    python --version
  2. In the popup, click Allow always
  3. Trigger the same command again: 
    python --version

Expected behavior

  • After choosing Allow always, the second identical command should run without prompting for approval again.

Actual behavior

  • The second identical command still triggers a fresh approval request.

Observed session evidence First command:

  • Command: 
    python --version
  • Result: 
    Python 3.14.3

Second command:

  • Same command: 
    python --version
  • Result: 
    Python 3.14.3
  • But it still required another approval prompt before running.

Notes

  • This may be a popup/UI approval persistence bug or a gateway approval-state bug.
  • There may also be a mismatch between popup approval state and chat/tool-visible approval state.

Impact

  • Repetitive approvals for harmless repeated commands
  • “Allow always” appears misleading or non-functional
  • Makes automation flows much more cumbersome

Fix Action

Fixed

PR fix notes

PR #59880: fix(exec): reuse gateway allow-always approvals

Description (problem / solution / changelog)

Summary

  • let gateway-host allowlist mode honor durable exact-command trust that was persisted via allow-always
  • add a regression test covering repeated exact gateway commands after an allow-always approval

Testing

  • pnpm.cmd exec vitest run src/agents/bash-tools.exec.approval-id.test.ts -t 'reuses gateway allow-always approvals for repeated exact commands|keeps ask=always prompts even when durable allow-always trust matches|keeps ask=always prompts for static allowlist entries without allow-always trust'
  • pnpm.cmd exec vitest run src/agents/bash-tools.exec-host-gateway.test.ts
  • pnpm.cmd lint src/agents/bash-tools.exec-host-gateway.ts src/agents/bash-tools.exec.approval-id.test.ts

Closes #59847.

Changed files

  • src/agents/bash-tools.exec-host-gateway.ts (modified, +5/-1)
  • src/agents/bash-tools.exec.approval-id.test.ts (modified, +56/-0)

Code Example

python --version

---

python --version

---

python --version

---

Python 3.14.3

---

python --version

---

Python 3.14.3

---
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Here’s a clean bug report draft you can paste:

Title: “Allow always” approval in popup does not persist for subsequent exec commands

OpenClaw version

  • OpenClaw 2026.3.31

Environment

  • Surface: webchat
  • Runtime: direct
  • Host: gateway
  • OS: Windows
  • Shell: PowerShell
  • Model session observed from: openai-codex/gpt-5.4

Summary When an exec approval popup appears and I click Allow always, the next exec command still requires approval again. This suggests approval persistence is not being honored.

Steps to reproduce

  1. Trigger an exec command that requires approval, for example: 
    python --version
  2. In the popup, click Allow always
  3. Trigger the same command again: 
    python --version

Expected behavior

  • After choosing Allow always, the second identical command should run without prompting for approval again.

Actual behavior

  • The second identical command still triggers a fresh approval request.

Observed session evidence First command:

  • Command: 
    python --version
  • Result: 
    Python 3.14.3

Second command:

  • Same command: 
    python --version
  • Result: 
    Python 3.14.3
  • But it still required another approval prompt before running.

Notes

  • This may be a popup/UI approval persistence bug or a gateway approval-state bug.
  • There may also be a mismatch between popup approval state and chat/tool-visible approval state.

Impact

  • Repetitive approvals for harmless repeated commands
  • “Allow always” appears misleading or non-functional
  • Makes automation flows much more cumbersome

Steps to reproduce

This issue is repeatable if you try to Trigger an exec command that requires approval:

Trigger an exec command that requires approval, for example: Copy python --version In the popup, click Allow always Trigger the same command again: Copy python --version

Expected behavior

After choosing Allow always, the second identical command should run without prompting for approval again.

Actual behavior

The second identical command still triggers a fresh approval request.

OpenClaw version

2026.3.31

Operating system

Windows 11

Install method

No response

Model

openai-codex

Provider / routing chain

OpenClaw main session → model openai-codex/gpt-5.4 → tool/runtime layer → gateway host for exec

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The "Allow always" approval in the popup does not persist for subsequent exec commands, suggesting a bug in approval persistence or a mismatch between popup and chat/tool-visible approval states.

Guidance

  • Verify that the approval persistence issue is specific to the openai-codex/gpt-5.4 model or if it occurs with other models as well.
  • Check the gateway host configuration for exec commands to ensure that it is set to honor the "Allow always" approval.
  • Investigate the possibility of a mismatch between the popup approval state and the chat/tool-visible approval state, and how this might be causing the approval persistence issue.
  • Test the "Allow always" approval with different types of exec commands to see if the issue is specific to certain commands or if it is a general problem.

Example

No specific code snippet can be provided without more information about the underlying system, but a potential debugging approach could involve logging the approval state after the "Allow always" option is selected and verifying that it is being correctly stored and retrieved for subsequent exec commands.

Notes

The root cause of the issue is unclear and may require further investigation into the approval persistence mechanism and the interaction between the popup, chat/tool, and gateway host. The issue may be specific to the openai-codex/gpt-5.4 model or the Windows 11 operating system.

Recommendation

Apply a workaround, such as implementing a custom approval persistence mechanism or modifying the gateway host configuration to honor the "Allow always" approval, as the root cause of the issue is unclear and may require further investigation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

After choosing Allow always, the second identical command should run without prompting for approval again.

#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING