aissue
Pick up an open issue from the amux issue tracker, mark it doing, work it, and mark it done.
Use when the user says "add to board", "create a task", or wants to track a todo on the amux kanban board
How it fires
How this command gets triggered: by you, by Claude, or both.
/amux-boardContext preview
What this command does when you run it.
Use when the user says "add to board", "create a task", or wants to track a todo on the amux kanban board
description: Use when the user says "add to board", "create a task", or wants to track a todo on the amux kanban board allowed-tools: Bash argument-hint: [task title or description]
You are adding an item to the **amux local kanban board** at `$AMUX_URL/api/board`.
# Add item
curl -sk -X POST -H 'Content-Type: application/json' \
-d '{"title":"...","desc":"...","status":"todo","session":"..."}' \
$AMUX_URL/api/board
# List all items
curl -sk $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| Field | Required | Values | Notes | |-------|----------|--------|-------| | `title` | yes | string | Short, imperative task name | | `desc` | no | string | Full context: what, why, acceptance criteria | | `status` | no | `todo` / `doing` / `done` | Defaults to `todo` | | `session` | no | amux session name | Which project/session owns this task |
The user's request is: **$ARGUMENTS**
1. Determine the best **title** (concise, imperative — e.g. "Fix login bug", "Add dark mode toggle") 2. Write a **desc** with full context:
3. Set **status** to `todo` unless the user indicates it's in-progress (`doing`) or already done (`done`) 4. Set **session** to the most relevant amux session name if the task belongs to a specific project (leave empty if general) 5. Add the item using `curl -sk` (the server uses a self-signed cert) 6. Confirm success by showing the created item's title and ID
Do not ask clarifying questions — infer context from the arguments and current conversation. If the arguments are empty, add a generic task titled "Untitled task" with an empty desc.
Open-source control plane for AI coding agents. Run an AI engineering team: parallel Claude Code, Codex, and Gemini workers with a shared board, atomic tasks, schedules, loops, origin-stamped messaging, model switching, and self-healing recovery. One dashboard, or your phone. MIT, single Rust binary.
Pick up an open issue from the amux issue tracker, mark it doing, work it, and mark it done.
Use when you need to interact with the amux system — manage board tasks, check sessions/workers, send emails, message via Telegram, automate browsers, work…
Use when the user asks to interact with a web page, take a screenshot of a site, click or type in Chrome, scrape content, or debug a web UI. Connects to real…
Repo/branch/file hygiene sweep — stray artifacts, doc drift, stale branches, worktrees, upstream sync, backup sprawl, duplicate build caches. Verifies before…
Scaffold a closed orchestrator loop — creates the mission note, state/constraints notes, and a scheduler entry from the v2 template.
Use when the user needs to log into a website for browser automation, save auth cookies, or sync browser profiles to cloud