/amux — amux Session Integration banner
mixpeek mixpeek

/amux — amux Session Integration

Development community intermediate

Description

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

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for mixpeek/amux, shared by 4 entries in this directory. It describes the repository, not this entry specifically.


description: Interact with the amux multiplexer — board, memory, sessions, and more allowed-tools: Bash, Read, Edit, Write argument-hint: [board|memory|sessions|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, and per-session memory.

amux API

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

Board

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

# Add item (id is auto-derived from session name, e.g. KITTYKAT-1)
curl -sk -X POST -H 'Content-Type: application/json' \
  -d '{"title":"...", "desc":"...", "status":"todo", "session":"SESSION_NAME"}' \
  https://localhost:8822/api/board

# Update item status
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

Board statuses: `todo` · `doing` · `done` (plus any custom columns)

Sessions

# List sessions (name, running, dir, model, tags)
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

# Get terminal output from a session
curl -sk https://localhost:8822/api/sessions/SESSION_NAME/peek

Memory

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

# Update this session's memory (replaces content)
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 by 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

Determining the Current Session Name

The current amux session name can be inferred from the tmux session:

tmux display-message -p '#S' | sed 's/^amux-//'

Or from `$TMUX` environment variable context. If you can't determine it, ask the user.

Instructions

The user's request is: **$ARGUMENTS**

Parse the arguments to determine what the user wants:

  • board or board list → list current board items, grouped by status
  • board add → add an item to the board; infer session from current tmux session
  • board done → mark an item done
  • memory or memory show → show current session's memory content
  • memory update → read the current MEMORY.md, extract useful facts from recent context, update via API
  • sessions → list all amux sessions with their status
  • help or empty → show a brief summary of available /amux commands
  • **any