[BUG] /schedule fails to connect despite valid claude.ai authentication (team account)
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?
Description:
## Summary
The /schedule skill consistently fails with "We're having trouble connecting with your
remote claude.ai account" even though authentication is confirmed working.
## Steps to Reproduce
- Run /schedule in Claude Code
- Observe error: "We're having trouble connecting with your remote claude.ai account
to set up a scheduled task."
## Auth Status
Running claude auth status returns:
{
"loggedIn": true,
"authMethod": "claude.ai",
"apiProvider": "firstParty",
"subscriptionType": "team"
}
## Environment
- Claude Code VSCode extension
- OS: Windows 11 Pro
- Auth method: claude.ai
- Subscription: Team
## Expected Behavior
/schedule should connect and allow creation of a recurring scheduled agent.
## Actual Behavior
Fails every attempt with the connection error message. No additional error details provided.
What Should Happen?
/schedule should open a flow to create a recurring remote agent, letting you set a name, cron schedule, and prompt — then save it to run automatically on claude.ai.
Error Messages/Logs
Steps to Reproduce
- Open Claude Code in VSCode
- Start a conversation
- Type /schedule
- Observe the error: "We're having trouble connecting with your remote claude.ai account to set up a scheduled task."
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.121 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗