[BUG]

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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?

Summary of the test: confirmed automation is completely non-functional — 100% failure rate, every fire across all 3 routines (dozens of runs, Aug 18–24) dies at the exact same line (Claude Code process started) with zero further activity. It's not your strategy config, not the Robinhood connector specifically (the "no-MCP" diagnostic hung identically), and unaffected by today's fresh login. This is a platform-level bug in Anthropic's cloud routine bootstrap.

### What Should Happen?

claude should be able to trade automatically without me

### Error Messages/Logs

```shell
Confirmed the root cause is broader than I thought — and it's not fixable from our side. Both routines hang at the identical point: Claude Code process started → nothing after, ever. That includes the "Diagnostic - No MCP" routine — which, notably, still has the Robinhood connector force-attached in its mcp_connections despite the name. This happened on all 5 fires I checked (4 today for the momentum bot, 1 for the diagnostic), each with worker_status: idle and zero events after startup.
```

### Steps to Reproduce

create bot to trade on robinhood using these strategies

### Claude Model

Not sure / Multiple models

### Is this a regression?

No, this never worked

### Last Working Version

_No response_

### Claude Code Version

Claude Code CLI 2.1.235.

### Platform

Anthropic API

### Operating System

macOS

### Terminal/Shell

Terminal.app (macOS)

### Additional Information

_No response_

No repository file, test, or entry point is identified. Start by reproducing the automation with the stated Robinhood and no-MCP routines, then inspect the worker status and events after “Claude Code process started.” Done means identifying the bootstrap failure and providing a focused fix or confirmed ownership boundary.

Escrito por el modelo de indexación a partir del texto del issue.