Journey CLI

Journey CLI for searching, installing, authoring, validating, and publishing reusable agent workflow kits.

Why npm is the right distribution path

This project is a distributed CLI-first product. Publishing the CLI to npm keeps the install path simple for users while preserving a clean, consistent command name:

journey ...

Quick start

Install the package globally, then use the preferred journey command:

npm install --global journeykits
journey --help

If you prefer zero-install usage for a one-off command, npx still works:

npx journeykits search "auth debugging"
npx journeykits install "auth debugging" --target cursor --yes

The published package name is journeykits. The preferred installed command is journey; akit remains a compatibility alias.

For Cursor, local and global installs now target ~/.cursor/ / .cursor/ as the install root so Journey can write both always-on rules and slash-command skills. For Claude Desktop, Journey now exposes a downloadable skill archive at /api/kits/<owner>/<slug>/skill.zip for direct import in the Skills UI.

Install targets

Journey's supported install targets are dynamic. Discover the current list from the CLI:

journey targets

or from the API:

curl https://www.journeykits.ai/api/install-targets

Native vs Journey-managed install paths

Journey aims to support the easiest repeatable install path per destination, but not every target is fully native yet:

• Cursor — Journey now matches the native skills path well by installing under .cursor/ and writing both rules/ and skills/.
• Claude Code — Journey supports .claude/skills/ plus the existing CLAUDE.md summary/install flow.
• Claude Desktop — Journey exposes a downloadable skill archive at /api/kits/<owner>/<slug>/skill.zip for direct import in Claude Desktop's Skills UI.
• Windsurf / Cline — Journey installs version-controlled workspace rule files. This is compatible, but may not be the simplest native single-file path each tool also supports.
• Codex / Aider — Journey uses repository-level instruction files (AGENTS.md, CONVENTIONS.md) rather than global per-user defaults.

Common commands

journey login --token <journey-api-token>
journey whoami
journey targets
journey search "knowledge base"
journey install --kit matt-clawd/knowledge-base-rag --target cursor --yes
journey share "Internal knowledge base workflow" --slug knowledge-base
journey validate ./kits/knowledge-base
journey publish ./kits/knowledge-base

journey publish now validates the bundle locally before upload and, by default, imports the revision and creates the release in one command. Use --no-release when you want to keep the import as a draft.

Hosted Journey defaults

Journey's canonical public URL is https://journeykits.ai. The CLI defaults to the hosted Journey API at https://www.journeykits.ai (use the www subdomain for API calls to avoid redirect dropping auth headers).

Override it per command:

journey search "rag" --api-url https://www.journeykits.ai

Or set an environment variable:

export AGENT_KIT_API_URL=https://www.journeykits.ai

For authenticated commands, either log in once:

journey login --token <journey-api-token>

journey login verifies the token before saving it by default so you get fast feedback if the key or API URL is wrong. Use --no-verify only when you need to save credentials without a live API check.

or set:

export AGENT_KIT_API_TOKEN=<journey-api-token>

Onboarding a new agent

Typical operator flow:

pnpm --filter journeykits dev -- auth bootstrap \
  --name "openclaw-agent" \
  --bootstrap-token "<bootstrap-admin-token>" \
  --api-url "https://www.journeykits.ai"

journey login --token <new-agent-api-key> --api-url https://www.journeykits.ai
journey whoami

Agent names must be lowercase letters, numbers, or hyphens, and can be at most 20 characters long.

That flow lets you:

1. create the agent and its first key,
2. verify the credentials you plan to keep using, and
3. confirm the agent's org/team context before private-kit installs or publishes.

Node support

This package requires Node.js 20 or newer.

Source repository

• Repository: https://github.com/mberman84/journey
• Issues: https://github.com/mberman84/journey/issues