Skip to main content
The Artemis Platform CLI lets you build and manage Agent Platform projects from your terminal or CI pipeline. CLI lets developers automate the complete agentic lifecycle, including authentication, project sync, eval runs, and deployment, from external systems, without Studio. To create, review, customize, test, and deploy agents with the CLI, see Use the Artemis Platform CLI.

Prerequisites

  • Node.js 22 or later.
  • An Agent Platform account with access to the workspace and project you want to manage.
  • The Platform URL provided by your platform administrator. For hosted solution, it’s a region-specific platform URL.
  • Additional permissions or credentials when using model execution, connector OAuth, or Git synchronization.

Install the CLI

Install the CLI globally using npm:
To use the CLI as a project dependency, install it as a development dependency:
To upgrade or remove a global installation:

Install a release candidate (RC) build

Versions containing -rc. are release candidates, published separately from the stable @koreai/artemis-platform-cli package. Release candidates build are for testing only and you must use those in a non-production project. To try a release candidate (RC) build before its stable release, explicitly install the RC package using the command npm install --global @koredev/artemis-platform-cli@<version>-rc.<timestamp>. After installation, verify the version using the command artemis-platform-cli --version.

Connect to Agent Platform

Before using the CLI, configure the URLs for the Platform services. In most deployments, apiUrl, runtimeApiUrl, and searchAiApiUrl use the same base domain. For example:
For a private, regional, or a separately-routed deployment, use the base URLs provided by your platform administrator. For hosted solution, it’s a region-specific platform URL. Don’t append paths such as /api, /runtime, or /search unless your administrator explicitly provides URLs that require them. You can also configure the service URLs using environment variables:
Environment variables override stored URL settings for the current process.

Authenticate

Sign in to Platform using the device authorization flow:
The login command opens the device authorization flow in your browser. Complete the browser step using an account that has access to the workspace and project you want to manage. For CI pipelines, provide an access token instead of signing in interactively. See Use the CLI in CI.

Select a workspace and project

List and select the workspace you want to work in:
List and select a project:
Interactive commands use the selected project. For CI workflows, use an explicit --project <project-id> whenever the command supports it. Once the CLI is installed, connected, and authenticated, continue to Use the Artemis Platform CLI to create, review, customize, test, and deploy agents.