Task commands

This reference is for Nexia maintainers who already have authorized access to the private host environment. Core is not distributed to external developers. These host commands are not prerequisites for the public CLI and cloud sandbox; start with the quickstart.

Run host commands from the Core root. Find a task or start ordinary App development:

task help
task dev:up:core12

The reference below covers arguments, profiles and reset scope.

Signature

Run Task from the Core repository root:

task <task-name> [VARIABLE=value] [-- <forwarded arguments>]1

Taskfile.yml includes the recipes under tasks/. Colon-separated parts are part of the command name; for example, task dev:up:typesense is one command. Print the live catalog grouped by work area at any time:

task help1

Minimal example

The shortest normal development cycle is:

task up
task status
task logs -- app  # Ctrl+C to stop following logs
task down1234

task up is the only short start alias. It means task dev:up:core. The explicit profile names are preferable in scripts and documentation.

Parameters

Forwarded arguments

Use -- to stop Task from parsing the remaining arguments. The selected recipe passes them to its underlying tool.

Task variables

Task variables are NAME=value tokens, not forwarded arguments.

Package tasks work with SDK and App source folders under packages/. The local package selection is the separate package-key list stored from PACKAGES=...; it decides which source folders generated local Composer configuration uses.

Runtime profiles

Each start command converges on a final profile: selected services start, unselected optional services stop, and existing Compose containers are reused. Running core and then runtime does not create a second app or database.

These are baseline service sets. A configured Reverb backend or browser key adds reverb to any selected profile and removes it from that profile's stop set. Agent response streaming remains SSE; Reverb carries Shell realtime invalidation, including Agent task changes.

There is deliberately no bare task dev:up, task full, or task agent:up. Use the profile name so the resulting service set is visible in the command.

Environment and inspection

Backend and frontend

Database

Quality and tests

Use the smallest relevant test while developing. task check is the local promotion gate, not the default response to every edit.

Packages, Agent, and services

task apps:list shows the keys accepted by PACKAGES before setup.

On a fresh setup, PACKAGES=all selects SDK and all App sources while PACKAGES=none selects no local sources. After setup, add or remove keys with task apps:add PACKAGES=... or task apps:remove PACKAGES=...; a replacement list is refused. apps:update and apps:update-all refuse existing work branches rather than switching them to develop; finish the task and switch intentionally before synchronizing.

Start the Agent Edge and Gateway with task dev:up:agent. When Reverb is configured, the same convergence also retains its WebSocket server for Agent task and Shell invalidation events. agent:restart and agent:logs operate the two Agent services; shell, sync, and test commands target the Gateway's Python workspace.

Options and safety

The three reset and destroy commands prompt before deletion. A profile switch, task down, and task logs do not delete volumes or application data.

Output or return

Task returns the exit status of the underlying command. task status prints the Compose service table, task logs stays attached until interrupted, and task help lists only public recipes and their aliases. Profile commands print Compose start/stop results and the Agent screen-search or Resource Dataset Import Ollama configuration checks required by that profile.

Errors

Related

• Run Nexia — understand the services before selecting a profile
• Artisan commands — look up commands forwarded through task artisan
• Quickstart — bootstrap the local environment once
• Fix installation errors — recover when a Task command cannot start the runtime