---
summary: "End-to-end guide for running SKYKOI as a personal assistant with safety cautions"
read_when:
  - Onboarding a new assistant instance
  - Reviewing safety/permission implications
title: "Personal Assistant Setup"
---

# Building a personal assistant with SKYKOI

SKYKOI is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** kois. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on koi.

## ⚠️ Safety first

You’re putting an koi in a position to:

- run commands on your machine (depending on your Pi tool setup)
- read/write files in your workspace
- send messages back out via WhatsApp/Telegram/Discord/Mattermost (plugin)

Start conservative:

- Always set `channels.whatsapp.allowFrom` (never run open-to-the-world on your personal Mac).
- Use a dedicated WhatsApp number for the assistant.
- Heartbeats now default to every 30 minutes. Disable until you trust the setup by setting `kois.defaults.heartbeat.every: "0m"`.

## Prerequisites

- SKYKOI installed and onboarded — see [Getting Started](/start/getting-started) if you haven't done this yet
- A second phone number (SIM/eSIM/prepaid) for the assistant

## The two-phone setup (recommended)

You want this:

```
Your Phone (personal)          Second Phone (assistant)
┌─────────────────┐           ┌─────────────────┐
│  Your WhatsApp  │  ──────▶  │  Assistant WA   │
│  +1-555-YOU     │  message  │  +1-555-ASSIST  │
└─────────────────┘           └────────┬────────┘
                                       │ linked via QR
                                       ▼
                              ┌─────────────────┐
                              │  Your Mac       │
                              │  (SKYKOI)      │
                              │    Pi koi     │
                              └─────────────────┘
```

If you link your personal WhatsApp to SKYKOI, every message to you becomes “koi input”. That’s rarely what you want.

## 5-minute quick start

1. Pair WhatsApp Web (shows QR; scan with the assistant phone):

```bash
SKYKOI channels login
```

2. Start the Gateway (leave it running):

```bash
SKYKOI gateway --port 18789
```

3. Put a minimal config in `~/.SKYKOI/SKYKOI.json`:

```json5
{
  channels: { whatsapp: { allowFrom: ["+15555550123"] } },
}
```

Now message the assistant number from your allowlisted phone.

When onboarding finishes, we auto-open the dashboard and print a clean (non-tokenized) link. If it prompts for auth, paste the token from `gateway.auth.token` into Control UI settings. To reopen later: `SKYKOI dashboard`.

## Give the koi a workspace (KOIS)

SKYKOI reads operating instructions and “memory” from its workspace directory.

By default, SKYKOI uses `~/.SKYKOI/workspace` as the koi workspace, and will create it (plus starter `KOIS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `HEARTBEAT.md`) automatically on setup/first koi run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it). `MEMORY.md` is optional (not auto-created); when present, it is loaded for normal sessions. Subkoi sessions only inject `KOIS.md` and `TOOLS.md`.

Tip: treat this folder like SKYKOI’s “memory” and make it a git repo (ideally private) so your `KOIS.md` + memory files are backed up. If git is installed, brand-new workspaces are auto-initialized.

```bash
SKYKOI setup
```

Full workspace layout + backup guide: [Koi workspace](/concepts/koi-workspace)
Memory workflow: [Memory](/concepts/memory)

Optional: choose a different workspace with `kois.defaults.workspace` (supports `~`).

```json5
{
  koi: {
    workspace: "~/.SKYKOI/workspace",
  },
}
```

If you already ship your own workspace files from a repo, you can disable bootstrap file creation entirely:

```json5
{
  koi: {
    skipBootstrap: true,
  },
}
```

## The config that turns it into “an assistant”

SKYKOI defaults to a good assistant setup, but you’ll usually want to tune:

- persona/instructions in `SOUL.md`
- thinking defaults (if desired)
- heartbeats (once you trust it)

Example:

```json5
{
  logging: { level: "info" },
  koi: {
    model: "anthropic/claude-opus-4-6",
    workspace: "~/.SKYKOI/workspace",
    thinkingDefault: "high",
    timeoutSeconds: 1800,
    // Start with 0; enable later.
    heartbeat: { every: "0m" },
  },
  channels: {
    whatsapp: {
      allowFrom: ["+15555550123"],
      groups: {
        "*": { requireMention: true },
      },
    },
  },
  routing: {
    groupChat: {
      mentionPatterns: ["@SKYKOI", "SKYKOI"],
    },
  },
  session: {
    scope: "per-sender",
    resetTriggers: ["/new", "/reset"],
    reset: {
      mode: "daily",
      atHour: 4,
      idleMinutes: 10080,
    },
  },
}
```

## Sessions and memory

- Session files: `~/.SKYKOI/koi/<koiId>/sessions/{{SessionId}}.jsonl`
- Session metadata (token usage, last route, etc): `~/.SKYKOI/koi/<koiId>/sessions/sessions.json` (legacy: `~/.SKYKOI/sessions/sessions.json`)
- `/new` or `/reset` starts a fresh session for that chat (configurable via `resetTriggers`). If sent alone, the koi replies with a short hello to confirm the reset.
- `/compact [instructions]` compacts the session context and reports the remaining context budget.

## Heartbeats (proactive mode)

By default, SKYKOI runs a heartbeat every 30 minutes with the prompt:
`Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.`
Set `kois.defaults.heartbeat.every: "0m"` to disable.

- If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown headers like `# Heading`), SKYKOI skips the heartbeat run to save API calls.
- If the file is missing, the heartbeat still runs and the model decides what to do.
- If the koi replies with `HEARTBEAT_OK` (optionally with short padding; see `kois.defaults.heartbeat.ackMaxChars`), SKYKOI suppresses outbound delivery for that heartbeat.
- Heartbeats run full koi turns — shorter intervals burn more tokens.

```json5
{
  koi: {
    heartbeat: { every: "30m" },
  },
}
```

## Media in and out

Inbound attachments (images/audio/docs) can be surfaced to your command via templates:

- `{{MediaPath}}` (local temp file path)
- `{{MediaUrl}}` (pseudo-URL)
- `{{Transcript}}` (if audio transcription is enabled)

Outbound attachments from the koi: include `MEDIA:<path-or-url>` on its own line (no spaces). Example:

```
Here’s the screenshot.
MEDIA:https://example.com/screenshot.png
```

SKYKOI extracts these and sends them as media alongside the text.

## Operations checklist

```bash
SKYKOI status          # local status (creds, sessions, queued events)
SKYKOI status --all    # full diagnosis (read-only, pasteable)
SKYKOI status --deep   # adds gateway health probes (Telegram + Discord)
SKYKOI health --json   # gateway health snapshot (WS)
```

Logs live under `/tmp/SKYKOI/` (default: `SKYKOI-YYYY-MM-DD.log`).

## Next steps

- WebChat: [WebChat](/web/webchat)
- Gateway ops: [Gateway runbook](/gateway)
- Cron + wakeups: [Cron jobs](/automation/cron-jobs)
- macOS menu bar companion: [SKYKOI macOS app](/platforms/macos)
- iOS node app: [iOS app](/platforms/ios)
- Android node app: [Android app](/platforms/android)
- Windows status: [Windows (WSL2)](/platforms/windows)
- Linux status: [Linux app](/platforms/linux)
- Security: [Security](/gateway/security)