test-claude-runtimelisted

# Test the Claude Code runtime How to spawn the **native `claude-code`** runtime against an isolated test server and observe its behavior. Assumes you've started a server with `/launch-grackle` (and have `GRACKLE_URL` + `GRACKLE_API_KEY` exported). ## Allowed model names ✅ | Model | Works? | Notes | | -------- | ------ | --------------------------------------------------------------- | | `sonnet` | ✅ | Default persona (`claude-code` / "Software Engineer") uses this | | `opus` | ✅ | | | `haiku` | ✅ | | No model gating — native Claude Code works out of the box (subscription/OAuth). These are the values `grackle runtimes` advertises and they all spawn. ## Spawn it The default persona already uses `claude-code`: ```bash grackle spawn local "<prompt>" # uses default persona (claude-code / sonnet) ``` Or make an explicit persona (e.g. to pick opus): ```bash grackle persona create "Claude Opus Tester" --runtime claude-code --model opus --prompt "You are a test agent." grackle spawn local "<prompt>" --persona claude-opus-tester ``` ## ⚠️ Key gotcha: native Claude Code does NOT surface real tool failures The Claude Agent SDK runs tools **internally** and (in streaming mode) does **not** emit real `tool_result` blocks with `is_error`. The adapter instea