The C3 Agentic AI Platform provides two tools for managing packages: the C3 AI Package Manager (CLI) and C3 AI Studio. These tools support core package development tasks, including creation, build, deployment, versioning, and dependency management. This section explains what each tool does, how it supports package workflows, and when to use which interface.

​
Overview of Tools

C3 AI Package Manager (CLI)

Command-line tool for creating, building, deploying, and upgrading packages

C3 AI Studio

Web-based IDE for editing, validating, and deploying packages

​
C3 AI Package Manager (CLI)

The C3 AI Package Manager is a command-line interface for managing packages from the terminal. It is designed for developers who prefer working in a scriptable environment or who are integrating package operations into automated workflows.The CLI supports the full package lifecycle. Developers can create new packages, build them, deploy them to an environment, list what packages exist in the environment, and upgrade them to a newer version.The following commands are available:
c3 pkg create myPackage         # Create a new package
c3 pkg build myPackage          # Build the package
c3 pkg deploy myPackage         # Deploy to current environment
c3 pkg upgrade myPackage 1.2.0  # Upgrade to specific version
c3 pkg list                     # List packages in the environment
Using the CLI provides a fast, efficient way to manage packages—particularly for developers who prefer terminal workflows or want to script repeated tasks. It is also useful in environments where automation is preferred, such as integration with CI/CD pipelines.Common use cases include creating new packages for applications, building and deploying packages for testing, and upgrading existing packages as dependencies evolve.

​
Summary

C3 AI provides two tools for managing packages: The CLI is suited for command-line users and automation workflows. Studio offers a visual interface for managing packages through a browser-based IDE. Both tools support the full package lifecycle, from creation to deployment, and interact with shared backend systems such as the Artifact Hub. The Artifact Hub plays a central role in storing, versioning, and distributing packages once they have been built. To learn how artifacts are stored, validated, and shared across environments, see Artifact Management.