/amux

description: Use when you need to interact with the amux system — manage board tasks, check sessions/workers, send emails, message via Telegram, automate browsers, work with CRM contacts, or use journal/files/org/torrents/graph/SQL/dictation
allowed-tools: Bash, Read, Edit, Write
argument-hint: [board|memory|sessions|workers|schedule|notes|email|gmail|calendar|telegram|journal|files|org|groups|torrents|graph|map|sql|dictation|tts|habits|review|connectors|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:** `$AMUX_URL` (self-signed TLS — always use `curl -sk`)

---

Board (tasks / issues)

# List all items
curl -sk $AMUX_URL/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"}' \
  $AMUX_URL/api/board

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

# Delete item
curl -sk -X DELETE $AMUX_URL/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"}' $AMUX_URL/api/board/ITEM_ID/claim

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

---

Sessions

# List sessions
curl -sk $AMUX_URL/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"}' $AMUX_URL/api/sessions/SESSION_NAME/send

# Peek at a session's terminal output
curl -sk "$AMUX_URL/api/sessions/SESSION_NAME/peek?lines=100"

**Modern equivalent:** `/api/workers/*` is the canonical, still-growing replacement for parts of this API — `send` in particular is "the canonical spelling... promoted out of the catch-all" per its own source comment. Prefer it for new code; `/api/sessions/*` still works (legacy alias) and isn't going anywhere yet.

curl -sk $AMUX_URL/api/workers | python3 -m json.tool          # list
curl -sk $AMUX_URL/api/workers/WORKER_ID                       # get one
curl -sk -X PATCH -H 'Content-Type: application/json' \
  -d '{"desc":"..."}' $AMUX_URL/api/workers/WORKER_ID           # update
curl -sk -X POST $AMUX_URL/api/workers/WORKER_ID/start          # start
curl -sk -X POST $AMUX_URL/api/workers/WORKER_ID/stop           # stop
curl -sk $AMUX_URL/api/workers/WORKER_ID/peek                   # peek
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"text":"your message"}' $AMUX_URL/api/workers/WORKER_ID/send
curl -sk $AMUX_URL/api/workers/WORKER_ID/dead-letters            # undelivered sends

---

Memory

# Read this session's memory
curl -sk $AMUX_URL/api/sessions/SESSION_NAME/memory

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

# Read/write global memory (shared across all sessions)
curl -sk $AMUX_URL/api/memory/global
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"content":"..."}' $AMUX_URL/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 $AMUX_URL/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"
  }' $AMUX_URL/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"
  }' $AMUX_URL/api/schedules

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

# Delete a schedule
curl -sk -X DELETE $AMUX_URL/api/schedules/SCHED_ID

# View recent runs
curl -sk $AMUX_URL/api/schedules/runs | python3 -m json.tool

# Trigger a schedule immediately
curl -sk -X POST $AMUX_URL/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)

**Corrected 2026-08-28** — this section previously documented a `/api/notes*` family that does not exist on the running server (confirmed live: 404 on both `/api/notes` and `/api/notes/test`, and `GET /api/debug/routes` lists no such family). Notes are backed by `/api/memories` (the `memories` primitive) instead — see `skills/amux-worker.md`'s "Gap found" section for the full investigation.

# List all notes
curl -sk $AMUX_URL/api/memories | python3 -m json.tool

# Read a note
curl -sk $AMUX_URL/api/memories/MEMORY_ID

# Create a note (global scope; memory_type "reference" fits documents best)
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"scope":{"level":"global"},"name":"my-note","content":"# Title\n\nBody text here","memory_type":"reference"}' \
  $AMUX_URL/api/memories

# Update a note's content
curl -sk -X PATCH -H 'Content-Type: ap