First checks
Check the target
Confirm the machine, project and provider account. Check whether the machine is connected and the account says it is signed in.
Read the exact message
A missing provider program, a sign-in request and a usage limit have different fixes. Do not switch billing methods just to clear a login message.
Check delivery before resending
If Miko says Not sure it arrived, look at the agent before sending the same instruction again.
Linux diagnostics and logs
sudo miko-host doctor --json
sudo miko-host logsDoctor checks Host dependencies, service state, clock, resources, configured network destinations and the pinned Claude Code installation. It does not check Codex or OpenCode. The logs command prints the recent Host and updater journal. The installer’s own log is /var/log/miko-install.log.
sudo systemctl status miko-host.service
sudo journalctl -u miko-host.service -u miko-update.service -n 200 --no-pagerKeep the original error, the time it happened and your installed version. Review logs before sharing: project names, file paths, terminal output or provider messages may contain private information. Never attach API keys, login codes, recovery keys or an entire profile directory.
Common messages
| What you see | What to do |
|---|---|
| The installer refuses the OS, container or resources | Check Requirements. Run on a supported VM or server with systemd, cgroup v2 and enough free space. |
| The installer says the CPU has no AVX2 | Use an arm64 server or an x86_64 CPU type with AVX2. |
| Can’t reach the gateway or release server | Check outbound HTTPS, WSS, DNS and the configured proxy. Run Doctor on that machine. |
| Pairing fails although --proxy is set | Pairing does not use --proxy. Allow direct outbound HTTPS and WSS to gw.getmiko.app, then pair again. |
| Claude Code is missing or fails verification | Run sudo miko-host update --check and inspect the updater logs. Keep signature checks enabled. |
| Codex has no Install option on a Mac | Codex needs Apple silicon. On an Intel Mac, use Claude Code or Grok Build, or run Codex on a Linux Host or Cloud machine. |
| Update your browser | Use Chrome or Edge 137+, Firefox 130+ or Safari 17+. |
| You’re signed out / this device was removed | Sign in again and follow the device approval flow. The agents on the machine keep working. |
| This device’s time is up | The public/shared-device session expired. Sign in again. |
| That’s pay per use, not your subscription | Sign out of the provider flow and choose the intended subscription option. |
| Not sure it arrived | Inspect the agent before sending again. |
| The project’s folder is missing | Choose the folder again on the correct machine. |
Mac provider problems
Open Provider setup and read the program and account status separately for each program: Codex, Claude Code, Grok Build, OpenCode and Antigravity. Install or repair the program if it is missing or damaged; use the provider’s own sign-in when the account needs it. A working program does not establish that the account has signed in or has available usage.
Avoid deleting your profile as a first repair step. The Mac’s local data includes account and conversation state. Back it up before any deliberate full removal. Closing the window is not an emergency stop.
Get help
Email contact@getmiko.app. Include your OS, the machine type, the action you tried, the exact error and when it happened. For Linux Host, include the reviewed output of sudo miko-host doctor --json. A small redacted excerpt is more useful than a complete private data directory.