@jelou/cli

Command-line tool for the Jelou platform — manage serverless functions, brains (AI projects), channels, WhatsApp bots and campaigns, marketplace apps, organization secrets, and Datum databases from one CLI.

Built for humans and AI coding agents alike: every command supports --json output, --describe introspection, and --no-input for CI. Agent skills auto-install into Claude Code, Cursor, Codex, and Windsurf on login so AI editors can drive the CLI from natural language.

Products covered:

• Functions — serverless TypeScript on Deno Subhosting (define() / app() SDK)
• Brains — AI projects with knowledge files
• Channels — connect brains to Web, WhatsApp, or other surfaces
• WhatsApp — bots, HSM templates, bulk campaigns
• Datum — managed PocketBase databases
• Marketplace — browse and install platform apps
• Secrets — organization-level secrets

Install

v1.0.0 has not been published yet. The @jelou/cli@0.2.13 currently on npm is the older Functions-only CLI and does not match the commands documented below. Until v1.0.0 ships, install from source:

git clone https://github.com/JelouLatam/jelou-cli.git
cd jelou-cli
deno install -A -f -n jelou --global ./mod.ts

Verify the installation:

jelou --version

npm, JSR, and platform binaries (Linux x64/arm64, macOS x64/arm64, Windows x64) land with the v1.0.0 release.

Local development build (jelou-dev)

When hacking on the CLI, you usually want a binary on PATH that's separate from the released jelou so the two don't fight over the same skills dir or muscle memory:

deno task bundle    # compile the current platform binary → dist/jelou-dev
deno task link      # symlink ~/.local/bin/jelou-dev → dist/jelou-dev
deno task unlink    # remove the symlink (only if it points at this repo)

After deno task link, run the dev binary as jelou-dev (which is what your shell history and any agent scripts will see, so a slip-up calling the released jelou is obvious).

The dev binary skips skill auto-install on jelou-dev login so it doesn't silently overwrite the released CLI's skills. To install dev skills for testing, run jelou-dev agent install --global explicitly — the rendered SKILL.md files get a banner and rewrite every bare jelou to jelou-dev in the body so AI agents drive the dev binary you're testing.

Pick a different link target with JELOU_DEV_LINK_DIR=/some/path, or pass --force to overwrite an existing symlink that points elsewhere.

Quick Start

# Authenticate
jelou login

# Create a new function
mkdir my-function && cd my-function
jelou functions init

# Start local dev server with hot reload
jelou functions dev
# → http://localhost:3000

# Deploy to production
jelou functions deploy
# → https://my-function.fn.jelou.ai

Agent Setup

jelou ships with agent skills for Claude Code, Cursor, Codex, and other AI editors. After logging in, they auto-install into any detected editor so a fresh session knows how to drive the CLI from natural language:

deno install -A -f -n jelou --global jsr:@jelou/cli
jelou login   # skills auto-install for detected editors

Open a new session in your editor and ask something like "create a brain in jelou", "list my databases", "send a WhatsApp campaign", or "list my channels" — the right jelou command gets invoked for you.

The CLI ships with these skills:

Manage skills manually any time:

jelou agent install --global                      # all skills, detected agents only
jelou agent install --global --all-targets        # all skills, every supported agent (including those not yet installed locally)
jelou agent install --global --only datum         # just one product
jelou agent install --global --only brain,whatsapp # multiple
jelou agent install --global --api                # Functions API variant

--all-targets is useful when an agent is installed after jelou login — or when you're about to install one and want the skills already in place. Cursor specifically gets a copy (not a symlink) because its skill loader doesn't accept YAML frontmatter; the SKILL.md is rewritten to an H1 + **Description:** shape that Cursor reads.

Opt out of auto-install during login with jelou login --skip-skills.

Commands

Run jelou <command> --help for flags and usage details.

Profiles

Multiple accounts (or environments) can coexist as named profiles. No more logging in and out when switching between staging and production.

# First login creates a profile (you pick the name)
jelou login
# → Profile name: production

# Add a second account
jelou login --token <staging-token> --profile staging

# List profiles
jelou auth list
#   Profile     Identity       Type  Active
#   production  token "prod"   PAT   ✓
#   staging     jelou:42       API Key

# Switch active profile
jelou auth switch staging

# One-shot override (does not change active profile)
jelou functions deploy --profile production

# Remove a profile
jelou auth remove staging

Credential Resolution

When resolving which credentials to use, the CLI checks (highest priority first):

1. JELOU_TOKEN environment variable
2. --profile <name> flag (one-shot, does not persist)
3. JELOU_PROFILE environment variable
4. activeProfile in ~/.jelou/credentials.json

Migration from Single-Account

Existing ~/.jelou/credentials.json files are automatically migrated to the multi-profile format on first access. A .bak backup is created. No action required.

CI / Non-Interactive Mode

Every command works headlessly in CI pipelines.

export JELOU_TOKEN=sk_your_token_here

jelou functions deploy --no-confirm --json | jq '.data.url'

• --no-input disables all prompts (auto-detected when CI=true or stdin is not a TTY)
• --json outputs { "ok": true, "data": ... } to stdout

See the full CI reference for per-command flags and GitHub Actions examples.

Configuration

See the full configuration reference for details.

Documentation

• CLI Reference — full command docs, flags, CI usage, troubleshooting
• SDK Guide — define() API, context, validation, testing

License

Copyright 2026 Jelou Inc. All rights reserved.

See LICENSE for details.