@task0/cli

Task-centric control layer for agent workflows. task0 manages projects, tasks, agent-runs, and OKRs; the workflow inside each task is driven by the agent and the operator — task0 does not enforce a lifecycle.

Requirements

• Node.js 20 or newer (for the npm-based installs)
• macOS, Linux (Windows: use the npm install path; no native binary yet)

Install

npm (recommended)

npm install -g @task0/cli
# or: pnpm add -g @task0/cli
# or: bun  install -g @task0/cli

One-shot installer

curl -fsSL https://raw.githubusercontent.com/cy0-labs/task0/main/apps/cli/install.sh | sh

Two-step variant for the security-conscious:

curl -fsSL https://raw.githubusercontent.com/cy0-labs/task0/main/apps/cli/install.sh -o install.sh
less install.sh
sh install.sh

Pin a version with TASK0_VERSION=0.2.0 sh install.sh.

Single-file binary (optional)

Pre-built binaries are attached to GitHub Releases for major versions:

| Platform | Asset | |-----------------|---------------------------------| | macOS arm64 | task0-darwin-arm64 | | macOS x64 | task0-darwin-x64 | | Linux x64 | task0-linux-x64 | | Linux arm64 | task0-linux-arm64 |

curl -fsSL -o task0 \
  https://github.com/cy0-labs/task0/releases/latest/download/task0-darwin-arm64
chmod +x task0 && ./task0 --version

No Node.js required — Bun runtime is embedded in the binary.

Quick start

task0 --help
task0 project init                 # bootstrap task0.yml in the current directory
task0 task init "<title or URL>"   # create a task
task0 task list                    # list active tasks
task0 task done <id>               # mark a task as done

Run as a service (autostart on login / boot)

task0 daemon register installs an OS-level autostart service in addition to recording the daemon identity. The server URL comes from the active profile's api_url — set it once per profile, then register reads it. After registering you can sign out, reboot, and the daemon reconnects on its own.

# 1. Tell the active profile which server to talk to (once per profile)
task0 profile set api_url https://central.example.com:4318

# 2a. user-level (default) — starts at user login, no sudo needed
task0 daemon register

# 2b. system-level — starts at boot, runs without an active login
sudo -E task0 daemon register --system

# pause / resume without forgetting the identity
task0 daemon stop
task0 daemon start

# disable everything: stop the service, remove the unit, clear the identity
task0 daemon logout

To target a different server for one invocation without writing it to the profile, export TASK0_API_URL — it overrides the profile's api_url for that shell session.

Per platform:

| Platform | Scope | File written | |----------|----------|--------------| | macOS | user | ~/Library/LaunchAgents/cc.cy0.task0.plist (launchd) | | macOS | system | /Library/LaunchDaemons/cc.cy0.task0.plist (launchd, needs sudo) | | Linux | user | ~/.config/systemd/user/cc.cy0.task0.service (systemd) | | Linux | system | /etc/systemd/system/cc.cy0.task0.service (systemd, needs sudo) |

Logs land in ~/.task0/logs/daemon.{out,err}.log. To watch them live:

tail -f ~/.task0/logs/daemon.out.log

Linux user-scope note: systemd kills the service when you log out. To keep it running across logouts, enable lingering once: sudo loginctl enable-linger $USER.

Useful flags on register:

• --no-install — register identity only; do not write a service unit
• --no-start — write the unit but do not start it immediately
• --force — re-register over an existing identity

For debugging or supervised setups you can also invoke the WebSocket loop directly in the foreground with task0 daemon run (this is the same command that the service unit invokes internally).

Environment variables

| Variable | Purpose | |-------------------------------|----------------------------------------------------------------------| | TASK0_API_URL | Override the task0 server endpoint (default http://127.0.0.1:4318) | | TASK0_HOME | Override the on-disk state dir (default ~/.task0) | | TASK0_DISABLE_ERROR_CAPTURE | Set to 1 to disable local crash reports | | EDITOR | Editor used for interactive prompts |

Security note — TASK0_API_URL decides which host receives daemon registration calls and the locally-stored Bearer token tied to that identity. Only point it at a server you control. The default loopback address is always safe; anything else should be a hostname you own (e.g. a self-hosted central server on your VPN). Never set it to a third-party URL from an untrusted source.

Links

• Repo: https://github.com/cy0-labs/task0
• Issues: https://github.com/cy0-labs/task0/issues
• Release manual: docs/02_tech_docs/release-packages.md