Troubleshooting

The failures you are most likely to meet, and their fixes.

A command hangs on the first call

That is the machine waking from suspension, usually a second, occasionally more after a long sleep. The CLI retries by itself; nothing to do.

"Your computer is not responding"

Most often a brand-new computer whose address has not propagated yet. Wait a minute and run modem again. If it stays silent, modem setup --new provisions a fresh machine, note that this is a new disk: the previous one is not carried over.

The login code is refused

Paste the code, not the URL. The URL opens in the browser; the page then shows a short code, and that is what the terminal wants. Tool-login codes expire after a few minutes: start the flow again if you were interrupted. A reconnect code from the site (modem login --code XXXX-XXXX) is valid for 60 minutes.

An agent asks me to log in again

Its credentials live on the computer's disk. If you provisioned a new computer, everything needs connecting once more: modem connect github, modem connect claude.

My terminal misbehaves after a session

Scroll acting as arrow keys, mouse coordinates printed as text: the terminal was left in a raw mode. Type reset and press Return. Current versions restore the terminal on exit, whatever the exit was.

A job stopped early

Check modem ls. Status timed_out means it hit its limit, rerun with a larger --timeout, or split the work. Status failed means a non-zero exit; modem logs <id> shows why.

An agent waited for a time that never came

A countdown inside an agent does not survive suspension: the machine froze while it waited. Anything time-based belongs in a job, and recurring work in a scheduled mission: see the roadmap.

Pushing a folder is slow

modem push skips node_modules, virtualenvs and build output, but a large repository is still a large repository. Cloning from Git on the computer is usually faster.

Still stuck

Write to dom@fabriquestudio.fr with the output of modem doctor.