Skip to content

Project

A project is one working context over a deployment — its own conversations, its own runs, its own agent config. Create one, then chat with it.

Terminal window
aura project create acme/vrp --name "vrp demo" # creates it, and selects it
aura chat # acts on the selected project
Command Does
aura project create <handle> --name <name> Create a project from a deployment (--description)
aura project list List your projects, marking the selected one
aura project use <id> Select the project other commands act on
aura project current Show which project is selected, and where that came from (--id for just the id)
aura project checkout <ref> Reset the workspace to a snapshot, tag, or deployment — discards uncommitted workspace state (y/N prompt; --yes to skip)
aura project delete <id> Delete a project and everything in it (--yes skips the prompt)
aura project instructions show Print both blocks — the deployment’s, and the project’s own
aura project instructions set <file> Replace the project’s own block
aura project instructions delete Remove both of the project’s blocks
aura project instructions pull <handle> Pull the instructions from a deployment
aura project skills list List every skill in force, labelled by scope
aura project skills show <skill> Print one skill in full, and which scope is in force
aura project skills set <dir> Upload one of the project’s own skills
aura project skills delete <skill> Remove that skill from the project
aura project skills pull <handle> Pull the skills from a deployment

create, list and current name no project: create names its deployment, and the other two are about your projects as a set.

use <id> and delete <id> name one as a positional, because there the project is what the verb acts on — and delete is irreversible, so it should never reach a project you did not name.

Every other verb acts on the selected project, with --project <id> to override it for a single command. Their positional is the operand: the file, directory, skill, handle, or ref.