Install and remove

Connect your Linux server

1. Get the command

   In the web app, choose Add a machine, then Linux server, and select Get a code. Copy the command shown for that machine.

2. Run it on the target server

   The command downloads the installer and passes your pairing code through MIKO_CODE. Review the installation plan and the request for root access.

3. Confirm the machine

   Compare the three words shown in the browser and on the server before approving the connection.

The command looks like this. Use the fresh code from Add a machine

curl -fsSL https://get.getmiko.app | MIKO_CODE=YOUR-CODE sh

YOUR-CODE is a placeholder. Use the complete command generated by your Connect page, including its address. When your browser’s time zone is not UTC, the command also sets MIKO_TZ to that zone. Do not reuse a code from a screenshot or send it to support.

Inspect the production installer’s plan

curl -fsSL https://get.getmiko.app | sh -s -- --dry-run

The bootstrap verifies the signed release list, its expiry and version, and the download’s size and SHA-256 before unpacking. Dry run shows the checks and plan without applying the installation.

What the command adds

Area	Changes
Programs	A versioned release in /usr/lib/miko-host-releases, the /usr/lib/miko-host link and the miko-host command in /usr/local/bin. The release supplies its Node runtime.
Accounts	miko-host runs the service. miko-user runs agents in /home/miko-user; it has no password, SSH login or sudo. A miko-hook group supports the local hooks.
Configuration and state	/etc/miko-host holds host.json, update.json, identity and install.json. Host state is under /var/lib/miko-host; updater state is under /var/lib/miko-update.
Services	miko-host.service and the updater service, timer and path unit.
Packages and hardening	Missing base packages are libcap2-bin, bubblewrap, socat and git. The plan also lists resource limits, core-dump policy, SSH login denial and any AppArmor or needrestart changes.
Provider programs	The installer schedules the verified Claude Code installation under /opt/miko/claude-code. The other agents run when they are turned on for that Host. Codex and OpenCode then use Miko’s pinned Linux builds under /opt/miko/codex and /opt/miko/opencode.
Tools folder	The Host service creates /opt/miko/tools and /opt/miko/tools/bin for publishing tools. These two folders are not listed in the plan.

For a connected server, the default plan caps Host and agent memory at 85% and uses CPU weight 50. Core dumps are disabled by default; –keep-crash-dumps retains the system handler. The plan lists the installer’s system-wide changes before you accept them; the tools folder above is created later by the Host service.

Read the actual plan before accepting it: the package list and hardening steps depend on the server. The journal at /etc/miko-host/install.json records what the installer owns.

Remove Linux Host

Command	What remains
sudo miko-host uninstall	Keeps miko-user’s home, profiles, projects and transcripts, plus host.db and user IDs for a reinstall. Removes the installed Host and its machine keys.
sudo miko-host uninstall –purge	Also removes Host state and the Host service account. Keeps miko-user and its home.
sudo miko-host uninstall –purge –delete-user-data	Also deletes miko-user and /home/miko-user. Requires confirmation of the machine name.

Before deleting user data

Back up projects, uncommitted work and any profiles you need. Full removal deletes the Miko user’s home. Apt packages remain because other software may use them. Remove the disconnected machine from Miko’s device or machine list separately.

Uninstall removes /opt/miko/claude-code, but not /opt/miko/tools or other folders under /opt/miko. After uninstalling, remove /opt/miko yourself if nothing else on the server uses it.

If the miko-host command has already been removed, use the installer’s –uninstall option with the same purge flags. Keep the installer address recorded for your installation; the uninstall output prints the follow-up command.

Install or remove the Mac app

Open the Mac app, complete Provider setup and sign in through the provider’s own program. Miko keeps its local state and app-managed provider installations under ~/Library/Application Support/Miko; externally installed CLIs and project folders remain separate.

1. Save work and sign out

   Back up your project folders and sign out of the provider accounts you are removing. Deleting an application is not the same as revoking a provider session.

2. Stop the agents

   Use Emergency stop so no agent is working, then quit Miko. Quitting Miko does not stop its background runtime, Miko Runtime: the runtime keeps your terminals and keeps running.

3. Quit Miko Runtime

   Open Activity Monitor, select Miko Runtime and choose Quit (not Force Quit). The runtime closes its terminals and exits when it is asked to quit. Check that neither Miko nor Miko Runtime is still listed.

4. Remove the application and local data

   Move Miko.app to the Trash. For removal of Miko’s local profiles and state, also remove ~/Library/Application Support/Miko after backing up any work stored there. Remove any separate project folders only if you intend to delete them.

This does not cancel a Miko subscription, delete a Cloud machine or remove an externally installed CLI. Manage those separately. Provider-owned credentials may also need to be revoked at the provider.