@agentium/cli

The CLI scaffolds TypeScript projects and runs development commands. Use Node.js 22.18+ within v22 or 24.11+ within v24. These commands target Agentium 4.0.0; see the release migration notes.

Create an application

npx @agentium/cli@4.0.0 init my-agent --template basic
cd my-agent
npm install
export OPENAI_API_KEY="your-key"
export OPENAI_MODEL="gpt-6.1-sol"
npm run typecheck
npm start

The basic template makes one Agent request, prints its response, and closes owned resources. Read the generated README for the selected template’s setup. For repeated use, install the CLI with npm install -g @agentium/cli and run agentium directly.

Templates

agentium init <name> also accepts the aliases new and create. The --template (-t) option defaults to basic.

Template	Starting point	Additional setup
`basic`	One Agent request with cleanup	OpenAI credentials and text model
`rag`	In-memory vector retrieval passed as evidence to an Agent	Provider credentials; replace sample documents
`voice`	VoiceAgent with an OpenAI Realtime provider	Supply a media transport for microphone and playback
`browser`	BrowserAgent with Playwright	Run `npx playwright install chromium`

Project names must be lowercase npm names without scopes or paths. The CLI refuses an existing destination before writing. Generated package ranges track the CLI release and include a TypeScript check.

Watch an entry point

agentium dev --entry ./src/index.ts

The entry defaults to ./src/index.ts; -e is the short option. This command launches npx tsx --watch with terminal input/output inherited from the parent process. Install tsx in the application. Your entry point owns any HTTP server, environment loading, logging, and shutdown behavior. To serve agents over HTTP, configure Express in your application.

Install a skill

agentium skills install ./skills/my-skill

A local directory must contain a readable SKILL.md; passing the file itself is also supported. This validates the local path. For an npm package or Git package source, the command runs npm installation with lifecycle scripts disabled (--ignore-scripts). Register the installed tools or skill directory explicitly in your Agent or harness configuration. Installation does not create a runtime manifest or automatically attach a skill. See SKILL.md directories for runtime configuration.

Publish a package

Run this only from the package directory you intend to publish:

agentium publish --access public

This wraps npm publish; --access defaults to public. Package preparation, npm credentials, release approval, and versioning belong to your release workflow.

Reference

Package APIs

Type guides

Upgrades

Architecture and tooling

Create an application

Templates

Watch an entry point

Install a skill

Publish a package

​Create an application

​Templates

​Watch an entry point

​Install a skill

​Publish a package

Create an application

Templates

Watch an entry point

Install a skill

Publish a package