Skip to content

[BUG] Scheduled tasks with Chrome MCP pause execution until user focuses the task in UI #40669

@jubss1607

Description

@jubss1607

Preflight Checklist

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

What's Wrong?

Summary

Scheduled tasks that use Chrome MCP tools (tabs_context_mcp, javascript_tool, navigate, etc.)
do not execute autonomously in the background. The task shows "Running" status but stops
executing until the user clicks on it in the Claude Code UI.

Steps to Reproduce

  1. Create a scheduled task (recurring cronExpression) that uses Chrome MCP tools
  2. Let it fire automatically on schedule
  3. Observe: task shows "Running" but no Chrome MCP tool calls are made
  4. Click on the task in the Scheduled panel
  5. Observe: task immediately resumes and Chrome MCP tools start executing

Expected Behavior

Scheduled tasks should execute fully autonomously in the background, including Chrome MCP
tool calls, without requiring user focus or interaction.

Actual Behavior

Chrome MCP tools are only invoked when the task session is actively focused in the UI.
Background execution stalls silently — no error, no timeout, just a frozen "Running" state.

Environment

  • Claude Code version: 2.1.73 / 1.1.9310
  • macOS (German locale, CEST timezone)
  • Chrome extension: active, Chrome open with extension enabled
  • Task type: recurring scheduled task (cronExpression)
  • Chrome MCP tools used: tabs_context_mcp, javascript_tool, navigate, tabs_create_mcp

Impact

This makes scheduled tasks with Chrome MCP unusable for automation — the entire purpose
of a scheduler is autonomous background execution. A flight scraper cron job that requires
user interaction every 4 hours is not a scheduler.

Workaround

None found. The task resumes only when the user clicks on it in the UI.

What Should Happen?

Scheduled tasks that use Chrome MCP tools (tabs_context_mcp, javascript_tool, navigate, tabs_create_mcp) should execute fully and autonomously in the background without requiring the user to click on or focus the task in the Claude Code UI. The task should complete all tool calls and finish execution regardless of whether the user is viewing the task.

Error Messages/Logs

No error is shown. The task status shows "Running" indefinitely. 
Chrome MCP tool calls are not made until user clicks on the task in the Scheduled panel.
Once clicked/focused, the task immediately resumes and completes successfully.

Timeline observed:
- 18:58 CEST: task starts (status: Running)
- 20:33 CEST: still Running, no Chrome MCP calls made
- 20:43 CEST: user clicks on task → task immediately resumes → Chrome MCP navigate, javascript_tool calls fire

Session log confirms tools only executed after user interaction:
tabs_context_mcp, javascript_tool, tabs_create_mcp, navigate — all called only after click.

Steps to Reproduce

  1. Open Claude Code with Chrome extension active and Chrome browser open
  2. Create a scheduled task with a cronExpression (e.g. every 4 hours) that uses Chrome MCP tools:
    • tabs_context_mcp (createIfEmpty: true)
    • javascript_tool
    • navigate
    • tabs_create_mcp
  3. Wait for the task to fire automatically on schedule (do NOT click on it)
  4. Observe: task shows "Running" status in the Scheduled panel
  5. Switch to another app — do not interact with Claude Code
  6. Wait 10+ minutes
  7. Observe: no Chrome MCP tool calls are made, task is frozen
  8. Click on the task in the Scheduled panel
  9. Observe: task immediately resumes and executes all Chrome MCP tool calls

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.73 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

The Chrome extension is installed and active. Chrome browser is open during all test runs.
The scheduled task runs correctly when the user is actively viewing it in the UI.
The same Chrome MCP tools work correctly in a manually triggered one-time test task.
The issue is specific to recurring scheduled tasks running autonomously in the background.
The task does NOT show any error — it silently waits in "Running" state until user interaction.
Claude Code app version shown in UI: 1.1.9310

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:mcpbugSomething isn't workinghas reproHas detailed reproduction stepsplatform:macosIssue specifically occurs on macOSstaleIssue is inactive

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions