Configuration

Tactical Analysis: When the Terminal Stops Responding Antigravity Editor’s “Running…” deadlock is not a bug—it’s a configuration failure. The terminal becomes unresponsive because the integrated shell profile is either missing or mismatched, causing the tool call to wait indefinitely for a non-existent shell environment. The Diagnosis The error manifests as every tool call hanging in “Running” state. Traditional debugging—checking network, permissions, file paths—yields nothing. The root cause lies deeper: VS Code’s terminal integration expects terminal.integrated.defaultProfile.linux (or macos/windows) to point to a valid shell in the user’s settings.json. If this key is absent or points to a non-existent profile, the terminal spawn hangs, and any tool call that invokes a command never returns. ...

The Problem When using Cerebras models (e.g., cerebras/gpt-120b) through CliproxyAPI, you might encounter a 422 Unprocessable Entity error: { "message": "body.store: property 'body.store' is unsupported", "type": "invalid_request_error", "param": "validation_error", "code": "wrong_api_format" } This happens because Cerebras strictly validates incoming payloads and rejects any fields it doesn’t recognize — in this case, the store parameter that OpenClaw automatically includes for conversation storage. Root Cause CliproxyAPI, acting as a unified gateway for multiple LLM providers, includes standard OpenAI-compatible fields like store in every request. While most providers ignore unknown fields, Cerebras is strict and returns 422 for any unsupported parameter. ...