You use the command line tool of PAS Code (PAS CLI) to create a PAS Code project, to add components such as apps, services, and agents to that project, and to run the project locally.
Every action of the CLI is a command. You call a command through the pas executable, followed by the command name and its arguments:
pas <command> [arguments] [options]
Some commands group related subcommands. For grouping commands such as pas platform and pas generate, you always call one of their subcommands, for example pas platform login or pas generate app.
If you did not install the CLI globally, call any command through npx instead:
npx -y @pas/cli <command> [arguments] [options]
Arguments in angle brackets, for example <name>, are required. When you omit a required argument, the CLI asks you for the value. Arguments in square brackets, for example [alias], are optional. When you omit them, the CLI offers you a selection list.
Every command supports --help to print its arguments and options, and --verbose to print the detailed output of the processes the command starts.
Use pas --version to print the installed CLI version.
Command Reference
|
Commands and Options |
Description |
||
|---|---|---|---|
|
|
|
Groups the commands that generate PAS components into an existing project. Call one of its subcommands. |
|
|
|
|
Generates an AI agent inside an existing service. |
|
|
|
|
Sets the target directory. When you omit it, the command lists the services of the project and asks for the directory inside the selected service. |
|
|
|
Generates an Angular frontend application in packages/<name>. |
||
|
|
|
Adds end-to-end tests with |
|
|
|
Leaves the generated code unformatted. |
||
|
|
Generates a project bundle in packages/<name>. A project bundle groups apps and services that are deployed together. |
||
|
|
|
Omits the bundle-wide deployment configuration file. |
|
|
|
Leaves the generated code unformatted. |
||
|
|
Generates a NestJS backend service in packages/<name>. |
||
|
|
|
|
Adds end-to-end tests. |
|
|
|
Generates an AI agent together with the service. |
|
|
|
|
Leaves the generated code unformatted. |
|
|
|
Prints information about the installed CLI. Use it to check that the CLI is installed and callable. |
||
|
|
Creates a new PAS Code project in a directory named after the project. The command asks whether a matching repository is created on the active platform, and logs you in first when no platform is active. Example components are included by default. |
||
|
|
|
Creates an empty project (without example components). |
|
|
|
Leaves the generated code unformatted. |
||
|
|
|
Groups the commands that manage the connections to your Scheer PAS platforms. Call one of its subcommands. |
|
|
|
|
Deletes a stored platform connection from your computer. When you omit the alias, the command asks you to select one. |
|
|
|
Groups the commands that manage your access to the Git service of the active platform. Call one of its subcommands. |
||
|
|
Registers the SSH public key of your computer in the Git service of the active platform, so you can push to its repositories. When you omit the path, the command lists the keys in |
||
|
|
Opens your browser to authorize your user for the Git service of the active platform. Run this command when another Git command reports that the Git service is not authorized. |
||
|
|
Creates a repository with the given name on the active platform, adds it as the Git remote |
||
|
|
Lists the platform connections stored on your computer with their URLs and marks the active one. |
||
|
|
Authenticates you against the platform at the given URL. The command opens your browser for the login, stores the credentials on your computer, activates the platform, and registers your SSH key in the Git service of the platform. |
||
|
|
|
Gives the connection a short name. Without an alias, the platform URL is used. |
|
|
|
Activates a stored platform connection, so subsequent commands work against that platform. When you omit the alias, the command asks you to select one from the stored connections. |
||
|
|
Starts the current project locally with |
||
|
|
|
Switches the Kubernetes context to the cluster of the profile and starts Tilt instead, which runs the project on that cluster. Profiles are stored as JSON files in |
|