Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (hilla) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Hilla CLI

AI co-founder in your terminal. Plan on canvas at hilla.ai, execute in CLI.

  ▄▄▄        ▄▄▄▄     ▄▄▄▄▄
▄█████▄    ▄██████▄ ▄████████▄
████████▄▄▄█████████████████████
 ▀█████████████████████▀▀   ▀██▀
    ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

hilla.ai is the brain — you sketch your project there: goals, stages, features, tech stack. hilla CLI is the hands — it takes that plan, sets up a sandbox, and writes real code into it.

Install

npm install -g hilla

Requires Node 18+.

Quick start

# 1. Launch the TUI
hilla

# 2. Connect your Hilla account (create a token at hilla.ai/settings/tokens)
/login

# 3. Pull a project from your canvas
/pull            # lists your projects
/pull 7          # or /pull <keyword>

# 4. Let the agent start building it
/run             # ask mode — you approve each file write / shell op

# Or launch directly in autonomous mode:
hilla --all-in

Every project gets its own sandbox at ~/hilla/<project-id>/. The agent only reads and writes inside this directory. Metadata (canvas context, history, plan) lives in ~/hilla/<project-id>/.hilla/.

Agent modes

Ask mode (default): every write_file, edit_file, and bash call prompts you for y/n. Destructive commands (rm -rf, sudo, etc.) always prompt regardless of mode.
Autonomous mode (hilla --all-in): non-destructive operations run without prompting. Ctrl+C cancels at any time.

Commands

Command	Description
`/login`	Connect your Hilla account
`/logout`	Sign out, remove local credentials
`/whoami`	Show current user
`/projects [n\|keyword]`	List or select a project
`/pull [n\|keyword]`	Pull project into sandbox (creates `~/hilla/<id>/`)
`/run [instruction]`	Start agent loop on current project. Bare `/run` picks the next step.
`/ask <question>`	One-off chat question (no tools)
`/cd`	Show the current project's sandbox path
`/status`	Current project summary
`/tasks`	Show tasks of loaded project
`/model [list\|n\|name]`	Show or switch AI model
`/credits`	Credit balance and plan
`/history`	Last 20 commands
`/config`	Show current settings
`/exec <cmd>`	Run shell command in cwd
`/diff`	Changes since last scaffold
`/sync`	Sync tasks to Linear/GitHub
`/clear`	Clear the chat
`/quit`	Exit

Agent tools

Inside /run, the model has access to:

read_file(path) — read inside the sandbox
write_file(path, content) — create/overwrite (asks approval)
edit_file(path, search, replace) — surgical diff edits
list_dir(path) — list files
bash(command, reason) — run shell inside sandbox (asks approval)
task_done(summary) — mark the task complete
ask_user(question) — pause and ask for clarification

Paths are relative to the project sandbox. Any attempt to write outside ~/hilla/<id>/ is rejected.

Keyboard

Tab — switch view, or complete slash commands
↑ / ↓ — command history
Ctrl+S — toggle sidebar
Ctrl+L — clear the chat
Ctrl+C — cancel agent turn / approval prompt

AI models

/model list to see available models. Switch with /model <n|name>.

sonnet-4.6 — coding (3 credits/msg)
kimi-k2.5 — writing / Turkish (2 credits/msg)
gemini-3.1-pro — planning (4 credits/msg)
minimax-m2.7 — research (2 credits/msg)

All models are proxied through Hilla's backend — your account token is the only credential.

Config

~/.hilla/config.json:

{
  "defaultModel": "sonnet-4.6"
}

~/.hilla/auth.json holds your PAT (chmod 600).

Environment overrides: HILLA_API_URL, HILLA_PUBLISHABLE_KEY.

Develop

git clone https://github.com/Plaaayground/hilla-cli.git
cd hilla-cli
npm install
npm run build
npm link
hilla

hilla