On your server, start with sudo miko-host doctor. It checks everything Miko needs and names the next step. When the installer stops before installing, it says “Nothing was changed.”
- This looks like a container
Run the command on the VM or server itself.
- Miko supports Ubuntu 24.04/26.04 and Debian 12/13
Use one of those systems. On an older Ubuntu, upgrade with
sudo do-release-upgrade.- This CPU has no AVX2
Claude Code needs AVX2 on x86_64. Ask your provider for a newer CPU type, or use an arm64 server.
- Miko needs at least 2 GB of memory and 3 GB of free disk
Use a bigger server (4 GB of memory is recommended), or free some disk space.
- The server clock is … off
Run
sudo timedatectl set-ntp true, then run the command again.- Can't reach … Miko needs outgoing HTTPS only
Allow outgoing HTTPS from the server. Nothing needs to come in.
- Miko needs root once to install
Run the command as root, or install sudo.
- Another Miko install, update or uninstall is running
Wait a minute, then run the command again.
- System updates kept the package manager busy
Try again in a few minutes.
- Behind a proxy
With
--proxy, Miko installs, but connecting doesn't go through the proxy yet. Allow outgoing HTTPS to Miko directly.
These connecting errors leave Miko installed. Get a new code under Machines › Connect a server, then run echo <code> | sudo miko-host pair - on the server.
- This code expired or was already used
Get a new code. A code works once, for 10 minutes.
- This code was already used. If that wasn't you…
Remove the other machine in Machines.
- The browser saw different words and refused this server
Nothing was added to your account. If it's your server, get a new code and check the three words again.
- Too many pairing attempts from this network
Wait a minute, then try again.
- <machine> is busy connecting
Wait until the code expires, or run
sudo miko-host pair --cancelon the server so a new code works at once.- Already paired with an account
To move the server to the account in your browser, run
echo <code> | sudo miko-host pair --replace -.
In the app, each message says what happened, whether your work is safe, and one next step.
- <machine> is offline
If it's on, it reconnects by itself. Your agents there keep their work. Press Check it.
- <machine> needs an update
It updates by itself when its agents are quiet. Press Update now to update at once.
- <machine> runs a different Miko
Press Update now, or Reload this page.
- Miko was updated
Press Reload to get the new version.
- <machine> isn't connected to your account
Press Connect it and connect it again with a new code. The same goes for “<machine> can't reach Miko”.
- Claude Code isn't ready on <machine>
Press Update now.
If the machine card says its processor can't run Claude Code (it needs AVX2), use another server.
- Paused when <machine> restarted
Press Resume. It picks up the same conversation.
- <machine> needs git
Run
sudo apt install gitthere, then press Look again.- <project>'s folder is missing
Press Pick the folder and choose it again.
- Miko can't start right now
Your agents keep working. Miko tries again by itself. Press Try now to try at once.
- You're signed out
Sign in again. Your agents keep working.
- This device was removed
Sign in again to add it back. Your agents keep working.
- This device's time is up
It was added as a public computer, and its 12 hours ended. Sign in again.
- This browser lost the keys Miko kept for it
Press Add with my passkey.
Then, in Settings › Manage devices, press Remove… on the old entry marked Lost keys, then Revoke.
- Miko couldn't read the keys it keeps in this browser
Reload the page.
- This device's clock looks off
Set the date and time to automatic, then try again.
- Too many tabs
Close a Miko tab you don't use, then reload.
- Update your browser
Use Chrome or Edge 137, Firefox 130, or Safari 17 or later.
- Typing is on <device>
Nothing was sent. Press Type here to take over.
- <device> took over typing
What you typed after that wasn't sent. Press Type here to take it back.
- Not sure it arrived
Look at the agent before you send it again.
- Already handled
The question was answered or ended first. Nothing was sent.
- That's pay per use, not your subscription
Press Sign out and try again, then pick the other option in the app's own list.
- <account> looks different on <machine>
Press Sign out and try again.
- Miko only waits for Codex limits
For Claude, send your next message when the limit resets.
- Too many tries
Wait a few minutes and try again.
- This invite link is incomplete
Open the whole link from your invite email. It ends with a long code after #invite=.
- This link doesn't work any more
It may be incomplete or already used. Ask for a new code on the sign-in page.
- Nothing arrives on iPhone
In your iPhone's Settings › Notifications, check that Miko is allowed to send notifications.
- Notifications are blocked for this site
Allow them in the browser's site settings, then come back.
- Miko couldn't reach this device's push service
Turn notifications off and on again.
- Miko got it on this device. Don't see it?
Check this device's notification settings for your browser, and Focus or Do Not Disturb.
- No Allow button on the notification
Safari and iPhone show no buttons. Tap the notification, then Allow on the card.
Elsewhere, buttons show only when the notification shows the whole request.
- Sign in again
A connection needs you to sign in again. Agents keep working without it until then. Press Sign in again.
- Couldn't reach it
Miko couldn't reach the service from your machine. Press Test again.
- Your browser blocked the new tab
Allow pop-ups for Miko and try again.
- Nothing is running there now
The website stopped. Ask your agent to start it again.
- Too many previews on <machine>
Close one and try again.
- Sign in to Claude on that machine first
Routines run with Claude. Sign in on the machine the routine runs on.
- An account or project is missing from the routine sheet
The sheet lists Claude accounts signed in on an up-to-date machine, with that machine's projects.
- This routine is already running
The current run keeps going, and the next one starts at its usual time.
- Something didn't work
Nothing was lost. Press Try again.
Still stuck?
Email contact@getmiko.app. For a server, include the output of sudo miko-host doctor --json.