> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bymiles.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting coding-agent work

> Resolve common setup, connection, and recovery issues when an agent uses Miles.

Most issues come down to sign-in, an interrupted run, browser connection, or an unclear site state. Ask the agent to show what it tried and what Miles returned before it retries anything.

## Login did not finish

Ask the agent to check the current sign-in state. If the code expired, it should create a new code. If the agent's network is blocked, it should show the host that needs access and stop retrying until that is fixed.

## The agent stopped mid-build

Ask the agent to check the current site state and resume the existing run. It should not start a duplicate site or build while work is still running.

```text theme={"dark"}
Check the current Miles site state and resume the existing work.
```

If the work was deliberately stopped, tell the agent whether to leave it stopped or start a new run.

## Design directions are missing

Miles may still be generating them or may be waiting for feedback. Ask the agent to show the current phase, the available directions, and any question Miles is waiting for you to answer.

## WordPress work needs a browser

Building and exporting HTML can happen without a browser. Converting a site into a WordPress theme, editing the converted site, and downloading a theme file need a connected Miles workspace. Open the authenticated link your agent gives you and keep that workspace open.

## Credits are low

Ask the agent to check your Miles account status before it starts another full build or conversion. Top up from the Miles dashboard when needed.

## A protected change is waiting

Ask the agent to show the requested change in plain language. Approve or decline that specific change. It must not treat a general “continue” message as approval.

## What to include when asking for help

Collect:

* the command that failed
* exact command output
* current site name or ID
* connected Miles account
* current site state
* any error ID or recovery message