miko-setup-launch

Files (1)

• SKILL.md

SKILL.md (first lines)

**CRITICAL: Never use `Read`, `Edit`, or `Write` tools on `~/.miko/.env` or any file inside `~/.miko/`. Use only `Bash` commands (`grep`, `printf >>`, etc.) to interact with env files — secrets must never be read into the conversation context.**

# Setup Launch

Prints a summary of the completed setup and offers to start Miko.

Use the absolute `MIKO_ENTRY` launcher from the prerequisites step. Verify `node "$MIKO_ENTRY" --installation` reports the selected mikoagents/miko commit. If this skill is invoked independently, resolve the default or user-selected install directory first; run prerequisites if no verified fork installation exists. Do not resolve a bare global `miko` executable.

Include the source commit and launcher path in the summary. Preserve an already authorized background method. When replacing an existing service, inspect its current command, wait until `/status` reports idle, and gracefully stop it before switching to this launcher; keep its environment and tunnel configuration. Avoid starting a second worker on the same port.

## Step 1: Gather Configuration

Read current state:

```bash
# Base URL
grep '^MIKO_BASE_URL=' ~/.miko/.env 2>/dev/null | cut -d= -f2-

# Linear
grep -c '^LINEAR_CLIENT_ID=' ~/.miko/.env 2>/dev/null

# GitHub
gh auth status 2>&1 | head -1

# Slack
grep -c '^SLACK_BOT_TOKEN=' ~/.miko/.env 2>/dev/null

# Repositories
cat ~/.miko/config.json 2>/dev/null

# Claude auth
grep -c -E '^(ANTHROPIC_API_KEY|CLAUDE_CODE_OAUTH_TOKEN)=' ~/.miko/.env 2>/dev/null
```

## Step 2: Print Summary

Print a formatted summary:

```
┌─────────────────────────────────────┐
│         Miko Setup Complete        │
├─────────────────────────────────────┤
│                                     │
│  Endpoint: https://your-url.com     │
│  Claude:   ✓ API key configured     │
│                                     │
│  Surfaces:                          │
│    Linear:  ✓ Workspace connected   │
│    GitHub:  ✓ CLI authenticated     │
│    Slack:   ✓ Bot configured        │
│                                     │
│  Repositories:                      │
│    • yourorg/yourrepo               │
│    • yourorg/another-repo           │
│                                     │
└─────────────────────────────────────┘
```

Use ✓ for configured items and ✗ for skipped/unconfigured items.

## Step 3: Make Miko Persistent

Miko needs to run as a background process so it stays alive and restarts after reboots. **Use the `AskUserQuestion` tool if available** to ask:

> **How would you like to keep Miko running in the background?**
>
> 1. **pm2** (recommended) — Node.js process manager. Simple to set up, auto-restarts on crash, log management built in. Best for most users.
> 2. **systemd** (Linux only) — OS-level service manager. Starts on boot automatically, managed with `systemctl`. Best for dedicated Linux servers.
> 3. **Neither** — run the fork launcher in the foreground for now.

### Option 1: pm2

The agent should run all of these commands directly:

1. Check if pm2 is installed (`which pm2`). If not, install it (`npm install -g pm2`).
2. Start the verified launcher: `pm2 start "$MIKO_ENTRY" --name miko --interpreter "<absolute node executable>" -- start`. Resolve Node with `command -v node` (Bash) or `(Get-Command node).Source` (PowerShell). For an existing pm2 process, update its script/interpreter to these paths instead of only restarting a process that still points to the npm CLI.
3. Save the process list: `pm2 save`
4. On supported Unix systems, use `pm2 startup` to configure reboot persistence. On Windows, preserve an existing scheduled task or background launcher and replace its Miko invocation with `node "<MIKO_ENTRY>" start`; use `Start-Process -WindowStyle Hidden` for a background launch. Do not claim reboot persistence from `pm2 save` alone on Windows.

After setup, inform the user of useful commands:
- `pm2 logs miko` — view logs
- `pm2 restart miko` — restart
- `pm2 stop miko` — stop

### Option 2: systemd (Linux only)

The agent should run all of these commands directly:

1. Resolve the actual values for the service file:
   ```bash
   NODE_BIN=$(command -v node)
   MIKO_USER=$(whoami)
   ```

2. Write the service file:
   ```bash
   sudo tee /etc/systemd/system/miko.service > /dev/null << EOF
   [Unit]
   Description=Miko AI Agent
   After=network.target

   [Service]
   Type=simple
   User=$MIKO_USER
   EnvironmentFile=/home/$MIKO_USER/.miko/.env
   ExecStart="$NODE_BIN" "$MIKO_ENTRY" start
   Restart=always
   RestartSec=10

   [Install]
   WantedBy=multi-user.target
   EOF
   ```

3. Enable and start:
   ```bash
   sudo systemctl daemon-reload
   sudo systemctl enable miko
   sudo systemctl start miko

From mikoagents/miko, Apache-2.0.

More from mikoagents/miko