[BUG] Claude Code Scheduled Task - MCP/Tool access

Resolved 💬 3 comments Opened Mar 19, 2026 by claywalker-lumos Closed Mar 23, 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?

Claude Code (desktop app) scheduled tasks are not able to use existing+connected Slack tools and MCP connectors (officially distributed connectors) unless I manually intervene. Attached a screenshot example.

<img width="800" height="648" alt="Image" src="https://github.com/user-attachments/assets/90435a09-d5de-4a12-b86d-0ddaa0f61a24" />

What Should Happen?

Scheduled tasks in claude code should be able to access my MCP tools connected and complete the task, just as if I had initiated it manually

Error Messages/Logs

The Slack MCP tools (`mcp__slack__*`) are not available in this session. The scheduled task requires Slack integration to read messages from #data-help and post replies, but no Slack connector is currently connected.

**Action needed:** Connect the Slack MCP server so this scheduled task can function. You can do this by adding a Slack MCP configuration to your Claude Code settings.

No actions were taken — exiting silently since the required tools are unavailable.

Steps to Reproduce

  1. using claude code in the desktop, create a workflow that uses connected tools. Make sure the first step is to scan a slack channel, and verify that it's able to complete the task.
  2. schedule the task
  3. open scheduled tasks and click "run now". It should fail (based on my experience)

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.1.6679 (f8f4ff) 2026-03-13T18:26:03.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗