onako 0.5.1

Dispatch and monitor Claude Code tasks from your phone

Onako

Dispatch and monitor Claude Code tasks from your phone.

Onako is a lightweight server that runs on your machine. It spawns Claude Code sessions in tmux, and you monitor them through a mobile-friendly web dashboard. Fire off tasks from an iOS Shortcut or the dashboard, check in from anywhere.

Install

pipx install onako

Requires tmux and Claude Code.

Usage

onako                              # starts server, drops you into tmux
onako --session my-project         # custom session name

If you're already inside tmux, onako auto-detects your session and skips the attach. Open http://localhost:8787 on your phone (same network) or set up Tailscale for access from anywhere.

onako stop                         # stop the server
onako status                       # check if running
onako clean                        # remove worktrees for finished tasks
onako reset                        # full teardown: stop, kill session, clean worktrees
onako serve                        # foreground server (for development)
onako version                      # print version

Dispatching tasks from the CLI

onako task "fix the login bug"                          # create a task
onako task "add tests" --branch feat/tests              # run in a git worktree
onako task "refactor auth" --branch feat/auth --base-branch develop

Flags

onako --dangerously-skip-permissions    # skip Claude Code permission prompts
onako --no-attach                       # start server without attaching to tmux
onako --dir /path/to/project            # set working directory for tasks

Adopting existing tmux windows

If you already have work running in another tmux session, move those windows into onako's session so they show up in the dashboard:

tmux move-window -s <session>:<window> -t onako

How it works

Onako monitors all tmux windows in the configured session. Windows it creates (via the dashboard) are "managed" tasks. Windows created by you or other tools are discovered automatically as "external" — both get full dashboard support: view output, send messages, kill.

Task state is persisted in SQLite so it survives server restarts.