Troubleshooting

The usual suspects: the API is not running, the provider is not configured, or the detector needs a nudge.

The editor says the service is unreachable

The editor reaches its service through a single origin. If that link is down, reload the page — and whoever runs the service can confirm it is up.

Detection finds nothing

• Raise Sensitivity in the inspector and re-run Detect.
• Check the page actually resolved — a blank or solid-colour page yields no ink.
• Very light scans benefit from a contrast pass before upload.

Detection finds too much (artwork, borders)

• Lower Sensitivity.
• Delete the stray boxes with the select tool — re-running Detect will not delete your manual boxes' text, but it does replace the automatic set.

OCR or translation fails

Provider errors surface verbatim in the stage status line. Common causes: no API key stored, a model name the provider does not recognise, a base URL missing its /v1, or a key without access to the chosen model. On the Antigravity route, check that the agy CLI is installed and signed in on the host that runs the API.

Reading is slow, or the CLI stalls. Antigravity answers a vision prompt in roughly 25–30 s and the -high variants can stall for minutes. Keep the OCR model on gemini-3.8-flash-low, lower AMYTL_AGY_CONCURRENCY if several people use the demo at once, and read a page in batches rather than one call per region.

Inpainting leaves grey smudges

That happens where a mask touches high-contrast line art — the solver pulls the line colour into the hole. Shrink the mask's dilate value, or switch the mask off and erase by hand with the box tool before running again.

Typeset text overflows its bubble

Select the layer and reduce the font size, lower the line height, or re-run translation with a style instruction asking for shorter lines.