#api-versioning
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2548 issues
`gateway/model-pricing` repeatedly logs: `pricing bootstrap failed: TimeoutError: The operation was aborted due to timeout` This happens frequently on startup/runtime, but there appears to be no config flag or env var to disable model-pricing bootstrap when pricing is non-critical.
The `cron` tool's `add` action consistently fails with `gateway closed (1008): pairing required` error when called from an agent session, even on a local loopback setup with proper authentication. **Affected operations:** - ‚ùå `cron add` (write operation) ‚Üí fails with "pairing required" - ‚úÖ `cron status` (read operation) ‚Üí works - ‚úÖ `cron list` (read operation) ‚Üí works This makes it **impossible to create cron jobs** from the agent, CLI, or any interface, breaking a core automation feature.
`web_fetch` appears to falsely block normal public URLs in Clash Verge / Mihomo fake-ip environments, returning: `Blocked: resolves to private/internal/special-use IP address` This makes `web_fetch` unusable in a common China-based network setup where a proxy is required for normal access.
After auto-updating to v2026.3.24, the gateway was silently killed by macOS launchd ~3 hours later and never restarted, despite `KeepAlive: true` in the LaunchAgent plist. The service was dead for 4+ hours with zero alerts until manual recovery.
After re-authenticating OpenAI Codex multiple times, Gateway kept logging `refresh_token_reused` and some runs failed with OAuth refresh errors. In our case, the root cause appears to be that the main agent auth store retained both: - `openai-codex:default` (older login) - a newer named Codex profile (email-based profile key) Different paths seemed to use different profiles, which led to refresh-token rotation conflicts. Removing the stale `openai-codex:default` entry and keeping only the newest named profile fixed the issue.
After updating to OpenClaw 2026.4.1, the `exec-approvals.json` file was reset/initialized with strict defaults, removing all previously working allowlist entries. This broke all automated workflows (cron jobs, ClawFlow scheduler) that rely on non-interactive command execution.
The Claude desktop app opens but the main content area is completely blank/black. Only the left sidebar renders. The issue started after an automatic update.
# OpenClaw Cron 调度时间偏移严重，执行时间记录不准确
The `llm-task` plugin returns "LLM returned empty output" for all Ollama models while working correctly with Anthropic models.
`github_copilot/gpt-5.4` is not accessible via the `/chat/completions` endpoint on the GitHub Copilot API. When a request is sent through the LiteLLM proxy (via the Anthropic `/v1/messages` pass-through endpoint), it always routes through `litellm.acompletion()` → `/chat/completions`, which GitHub Copilot rejects with: ``` model "gpt-5.4" is not accessible via the /chat/completions endpoint code: unsupported_api_for_model ```
When re-authenticating the Qwen model, it shows authentication successful but the terminal still running starting Qwen OAuth.
When all configured credentials return `model_cooldown` with a `reset_seconds` value indicating hours-long unavailability, OpenClaw has no circuit breaker. The session retries every ~20 seconds indefinitely, producing thousands of failed attempts and making the session completely unusable until manually reset.