Project Management Commands

Create and manage AGNT5 projects with Control Plane integration

The agnt5 project command family helps you create Control Plane projects, sync local configuration, and explore existing projects. Many operations require an API key because they call the Control Plane directly.

`agnt5 project create`

Creates a new project remotely and, for Python projects, scaffolds a ready-to-run repository on disk. The command is also available as a top-level shortcut agnt5 create.

Syntax

agnt5 project create [project-name] [options]
agnt5 create [project-name] [options]

Options

Flag	Description
`--organization-id`	Force the Control Plane organization to associate with the new project.

Flow Summary

Prompt (or accept a CLI argument) for the project name
Prompt for a language (python or typescript)
Resolve the organization ID or prompt to choose
Call the Control Plane to create the project
Generate full project skeleton for Python projects
Write .agnt5/project-ref for future CLI commands
Print next steps

Python Project Scaffolding

For Python projects, the CLI generates:

app.py, src/<project>/functions.py
tests/__init__.py, tests/test_functions.py
pyproject.toml, agnt5.yaml, Dockerfile
.gitignore, README.md

Non-Python languages currently skip the scaffolding step but still create the remote project and update your local metadata.

`agnt5 project list`

Lists projects visible to your API key in a simple table. Pagination, search, and ordering options are available.

Syntax

agnt5 project list [options]

Options

Flag	Description
`--page`, `-p`	Page number to request (default: `1`)
`--page-size`	Number of projects per page (default: `20`)
`--search`, `-s`	Filter by name, ref, or slug
`--language`, `-l`	Filter by language (e.g., `python`)
`--status`	Filter by status returned from the Control Plane
`--order-by`	Sort column: `created`, `updated`, `name` (default: `updated`)
`--order-dir`	Sort direction: `asc` or `desc` (default: `desc`)

The output includes truncated IDs, names, references, languages (with versions when available), statuses, and creation dates. Pagination metadata at the bottom shows how many results are displayed relative to the total.

`agnt5 project info`

Work in Progress

Placeholder command that will eventually print detailed metadata about the current project or a provided ID. For now it simply acknowledges the request. Use agnt5 project list to locate IDs until the implementation is complete.

Syntax

agnt5 project info [project-id]

This command will eventually provide comprehensive project details including configuration, deployment status, environment variables, and resource usage metrics.

`agnt5 project init`

Work in Progress

Reserved for initializing an existing directory as an AGNT5 project. The command currently prints a stub message.

Syntax

agnt5 project init

This command will eventually initialize an existing directory as an AGNT5 project by creating the necessary configuration files and project metadata.

Command

agnt5 project init

Response

Command acknowledged but not yet implemented.
Use 'agnt5 project create' to create new projects.

Local Project Metadata

Most project-aware commands rely on two files created during project create:

File	Purpose
`.agnt5/project-ref`	Binds the working directory to a Control Plane project reference
`agnt5.yaml`	Holds language, environment, deploy, and variable configuration for the deployment pipeline

If you clone an existing project make sure both files are present (or run SaveProjectRef / SaveDeploymentProjectConfig helper functions) before using agnt5 deploy.

Project Reference File

The .agnt5/project-ref file contains the Control Plane project reference that links your local directory to the remote project. This file is automatically created during agnt5 project create and is required for deployment commands.

Deployment Configuration

The agnt5.yaml file contains project-specific configuration used by the deployment pipeline:

# Example agnt5.yaml structure
language: python
version: "3.12"
environment:
  development:
    # Development-specific config
  production:
    # Production-specific config
deploy:
  # Deployment configuration
variables:
  # Environment variables