Expose scheduled task concurrent session limit as a user-configurable setting

Status Open
Maintainer reply None cached
Activity 1 comment · opened Sep 2, 2026

Problem

The Claude Desktop scheduled task scheduler has a concurrent session limit of 3, controlled server-side by a GrowthBook feature flag. There is no user-configurable setting to adjust this.

For fleets with 40+ scheduled tasks, 3 concurrent slots creates severe slot starvation during peak dispatch windows. Observed impact on a production fleet:

  • 283+ retry-minutes for a single task waiting for a slot
  • 4,290 skipped dispatches in one night when 3 permission-blocked sessions held all slots
  • 16 of 41 tasks that ran but never posted their terminal completion marker, because they waited hours for a slot, then exhausted their context window doing substantive work before reaching the final step

The retry mechanism works (tasks do eventually get slots), but the queue depth means tasks start with hours of accrued wait time, leaving less context budget for actual work.

Request

Expose the global and perTask limits as user-configurable settings, either in:

  • claude_desktop_config.json (preferred, already has scheduler settings like ccdScheduledTasksEnabled)
  • ~/.claude/settings.json
  • Or a dedicated scheduler config section

A reasonable default of 3 is fine for most users. Power users running large scheduled task fleets need the ability to raise it to 5-8.

Workarounds attempted

  1. Destaggered 9 tasks from morning peak to afternoon to reduce contention
  2. Reordered terminal steps in task definitions so critical steps fire earlier before context exhaustion

These help but do not solve the fundamental capacity constraint for large fleets.

Environment

  • macOS (Apple Silicon)
  • Claude Desktop (latest as of 2026-09-01)
  • 56 registered scheduled tasks, ~41 enabled

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗