[BUG] Scheduled task (routine): per-site browser navigation approval is never persisted — "Always allow" has no effect, blocking unattended automation

Status Open
Reported on v2.1.217
Maintainer reply None cached
Activity 0 comments · opened Jul 31, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Environment

  • Claude Desktop app on Windows 10 Pro (10.0.19043)
  • Reproduced on TWO versions: the Microsoft Store build (1.22209.0.0) and a fresh

install of the latest desktop build (1.24012.1, Squirrel/AppData install)

  • Claude in Chrome extension connected (real Chrome browser)
  • Scheduled task (routine) created via the scheduled-tasks MCP tool, running 3x daily
  • Task uses claude-in-chrome tools to read x.com pages (user's own subscribed authors)

What happens

Every scheduled run pauses with the approval dialog:
"Claude가 이동 x.com하도록 허용하시겠습니까?" (Allow Claude to navigate to x.com?)
with options 거부 / 항상 허용 / 한 번만 허용.
Clicking "항상 허용" (Always allow) lets the current run proceed, but the approval
is NOT persisted:

  • The routine's "항상 허용됨" (Always allowed) section stores other tools fine

(Get page text, Read page, Computer, Browser batch, Bash commands) —
but the navigation approval for x.com never appears there.

  • The next scheduled run shows the exact same dialog again. Reproduced on 8+

consecutive runs across three days, including after a clean reinstall of the
latest app version and recreating the scheduled task from scratch
(clicked "항상 허용" on the 15:00 run → same dialog again on the 18:00 run).

What we tried

  • Clicked "항상 허용" on the dialog many times (never "한 번만 허용") — not persisted.
  • Project .claude/settings.local.json contains "mcp__claude-in-chrome__navigate"

in permissions.allow — dialog still appears.

  • Set the Chrome extension side panel mode to "묻지 않고 실행" (run without asking)

— dialog still appears (it comes from the desktop app, not the extension).

  • The extension options page "인증된 사이트" (verified sites) list stays empty.
  • Rewrote the task prompt to navigate via browser_batch (which IS in the task's

always-allowed list) instead of the standalone navigate tool — the same
per-origin dialog still appears, so the gate is on the navigation action itself.

  • Clean reinstall of the latest desktop app + recreated the task — no change.

Expected

Per the product's own messaging ("Tool approvals granted during a run are stored
on the task and auto-applied to future runs"), clicking "Always allow" for
navigation to a specific site during a scheduled run should be persisted on the
task, so subsequent runs proceed without a human click.

Impact

Any scheduled task that browses a website cannot run unattended — a human must
click an approval on every run, defeating the purpose of scheduling. A per-task,
per-origin persistent allow (with the ability to revoke in settings) would solve
this while keeping the safety gate for new/unknown sites.

What Should Happen?

Clicking "항상 허용" (Always allow) on the navigation approval dialog during a scheduled run should persist the approval on the task — the same way approvals for other tools (Read page, Get page text, Browser batch, Bash) are already stored in the task's "Always allowed" list. Subsequent scheduled runs should then proceed without any human click, enabling truly unattended automation. A per-task, per-origin persistent allow (revocable in settings) would keep the safety gate for new/unknown sites while fixing this.

Error Messages/Logs

No error message. The symptom is this approval dialog re-appearing on every scheduled run:
"Claude가 이동 x.com하도록 허용하시겠습니까?"
(Allow Claude to navigate to x.com?)
[거부] [항상 허용] [한 번만 허용]
Clicking "항상 허용" has no lasting effect — the task's "항상 허용됨" (Always allowed) list never gains the x.com navigation entry.

Steps to Reproduce

  1. In the Claude Desktop app on Windows, connect the Claude in Chrome extension.
  2. Create a scheduled task (routine) via the scheduled-tasks MCP tool. The task's prompt instructs Claude to open x.com pages with the claude-in-chrome browser tools.
  3. Wait for a scheduled run to start. The approval dialog "Allow Claude to navigate to x.com?" (거부 / 항상 허용 / 한 번만 허용) appears.
  4. Click "항상 허용" (Always allow). The run proceeds normally.
  5. Wait for the next scheduled run.
  6. The exact same dialog appears again. The navigation approval is never saved to the task's "Always allowed" list, while approvals for other tools (Read page, Get page text, Browser batch, Bash) are saved there correctly. Reproduced on 8+ consecutive runs across 3 days, including after a clean reinstall of the latest app version.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.217

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗