Troubleshooting
anycap is not found
Section titled “anycap is not found”ls -la ~/.local/bin/anycapexport PATH="$HOME/.local/bin:$PATH"command -v anycapReload your shell profile after confirming the binary exists.
Authentication fails
Section titled “Authentication fails”anycap statusanycap login --headlessIn CI, confirm ANYCAP_API_KEY exists in the process environment without printing it. Remember that an environment value takes precedence over persistent credentials.
A model rejects a parameter
Section titled “A model rejects a parameter”Model contracts evolve. Inspect the selected model and exact mode instead of copying parameters from another model:
anycap image models <model-id> schema --mode image-to-imagePass only fields and enum values advertised by the current schema.
A local file is not accepted
Section titled “A local file is not accepted”- Confirm the path exists.
- Use
--filefor media understanding and the documented--paramfield for generation. - In MCP, confirm the canonical file path is under an effective allowed root.
- Do not upload to Drive merely to feed a local file into another AnyCap command.
A local video is too large
Section titled “A local video is too large”actions video-read --file accepts files up to 100 MB. Compress an oversized file first:
ffmpeg -i input.mp4 -vcodec libx264 -crf 28 output.mp4Capture diagnostics
Section titled “Capture diagnostics”Keep trace_id, request_id, task_id, upstream_request_id, and stage fields from failed calls. Submit a focused report:
anycap feedback --type bug \ -m "describe the unexpected result" \ --request-id <request-id>See Feedback and diagnostics for structured failure reports.