/amux

description: Use when you need to interact with the amux system — manage board tasks, check sessions, send emails, automate browsers, or work with CRM contacts
allowed-tools: Bash, Read, Edit, Write
argument-hint: [board|memory|sessions|schedule|notes|email|browser|crm|help] [args...]

/amux — amux Session Integration

You are running inside an **amux** managed Claude Code session. amux is a local multiplexer that manages multiple Claude sessions, a shared kanban board, notes, CRM, scheduler, email, browser automation, and per-session memory.

**Base URL:** `https://localhost:8822` (self-signed TLS — always use `curl -sk`)

---

Board (tasks / issues)

# List all items
curl -sk https://localhost:8822/api/board | python3 -m json.tool

# Add item
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"title":"...", "desc":"...", "status":"todo", "session":"SESSION_NAME"}' \
  https://localhost:8822/api/board

# Update item
curl -sk -X PATCH -H 'Content-Type: application/json' \
  -d '{"status":"doing"}' https://localhost:8822/api/board/ITEM_ID

# Delete item
curl -sk -X DELETE https://localhost:8822/api/board/ITEM_ID

# Claim a task atomically (prevents two sessions taking same task)
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"session":"SESSION_NAME"}' https://localhost:8822/api/board/ITEM_ID/claim

Statuses: `backlog` · `todo` · `doing` · `done` (plus any custom columns)

---

Sessions

# List sessions
curl -sk https://localhost:8822/api/sessions | python3 -m json.tool

# Send a message to a session
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"text":"your message"}' https://localhost:8822/api/sessions/SESSION_NAME/send

# Peek at a session's terminal output
curl -sk "https://localhost:8822/api/sessions/SESSION_NAME/peek?lines=100"

---

Memory

# Read this session's memory
curl -sk https://localhost:8822/api/sessions/SESSION_NAME/memory

# Update this session's memory
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"content":"# My Notes\n..."}' https://localhost:8822/api/sessions/SESSION_NAME/memory

# Read/write global memory (shared across all sessions)
curl -sk https://localhost:8822/api/memory/global
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"content":"..."}' https://localhost:8822/api/memory/global

---

Scheduler (recurring / one-time tasks)

Schedule commands to run in sessions at specific times or on a cron schedule.

# List all schedules
curl -sk https://localhost:8822/api/schedules | python3 -m json.tool

# Create a one-time schedule
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{
    "title": "Weekly analytics",
    "session": "gtm-videos",
    "command": "Run the weekly analytics report",
    "kind": "tmux",
    "sched_type": "once",
    "run_at": "2026-04-10T09:00"
  }' https://localhost:8822/api/schedules

# Create a recurring schedule (cron expression)
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{
    "title": "Weekly video check",
    "session": "gtm-videos",
    "command": "Check video pipeline status and post summary to board",
    "kind": "tmux",
    "sched_type": "recurring",
    "schedule_expr": "0 9 * * 1"
  }' https://localhost:8822/api/schedules

# Update a schedule
curl -sk -X PATCH -H 'Content-Type: application/json' \
  -d '{"enabled": 1}' https://localhost:8822/api/schedules/SCHED_ID

# Delete a schedule
curl -sk -X DELETE https://localhost:8822/api/schedules/SCHED_ID

# View recent runs
curl -sk https://localhost:8822/api/schedules/runs | python3 -m json.tool

# Trigger a schedule immediately
curl -sk -X POST https://localhost:8822/api/schedules/SCHED_ID/run

**Fields:** `title`, `session` (target session name), `command` (text sent to session), `kind` (`tmux`), `sched_type` (`once`|`recurring`), `schedule_expr` (cron: `min hour dom month dow`), `run_at` (ISO datetime for one-time), `watch` (0/1 — watch output after send), `watch_timeout` (seconds), `done_pattern` (regex to detect completion), `done_action` (`disable`|`reschedule`)

---

Notes (documents / reference material)

# List all notes
curl -sk https://localhost:8822/api/notes | python3 -m json.tool

# Read a note
curl -sk https://localhost:8822/api/notes/my-note

# Create or update a note (use slug as path)
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"content":"# Title\n\nBody text here"}' \
  https://localhost:8822/api/notes/my-note

# Delete a note (moves to trash)
curl -sk -X DELETE https://localhost:8822/api/notes/my-note

# Pin/unpin a note
curl -sk -X POST https://localhost:8822/api/notes/my-note/pin

---

Email (via Mail.app)

Accounts: ethan@mixpeek.com · esteininger21@gmail.com

# Read inbox (returns recent messages with subject, from, date, body, message_id)
curl -sk "https://localhost:8822/api/email/inbox?account=ethan@mixpeek.com&count=20&days=7"
# Params: account (filter to one account), count (max messages, default 20), days (lookback, default 7)

# Send email (validates email format, optional from account)
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"to":"x@example.com","subject":"Hi","body":"...","from":"ethan@mixpeek.com"}' \
  https://localhost:8822/api/email/send

# Reply to an existing email (by message_id from inbox response)
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"message_id":"<msg-id-from-inbox>","body":"Thanks!","reply_all":false}' \
  https://localhost:8822/api/email/reply

# Sync email → calendar events (background AI extraction)
curl -sk -X POST https://localhost:8822/api/email/sync

# Get extracted calendar events
curl -sk https://localhost:8822/api/email/events

**Workflow for replying:** call `/api/email/inbox` first to find the message, then use its `message_id` field in `/api/email/reply`.

---

Browser Automation

**Live backend** — same verbs, executed in YOUR real Chrome (real logins, real IP). Opens