Sachin Koli

HooCodeStart here

Quickstart

This page gets you from install to a useful first hoocode session.

Install

One command, on any platform:

# macOS and Linux
curl -fsSL https://kolisachint.github.io/hoocode/install.sh | sh
# Windows
irm https://kolisachint.github.io/hoocode/install.ps1 | iex

Already have Node 20+? npm install -g @kolisachint/hoocode-agent works too. Either way you get the hoocode (and hoo) command. Every other route – standalone archives, offline machines, containers, source – is on the Install page.

Then start hoocode in the project directory you want it to work on:

cd /path/to/project
hoocode

Authenticate

HooCode can use subscription providers through /login, or API-key providers through environment variables or the auth file.

Option 1: subscription login

Start hoocode and run:

/login

Then select a provider. Built-in subscription logins include Claude Pro/Max, ChatGPT Plus/Pro (Codex), and GitHub Copilot.

Option 2: API key

Set an API key before launching hoocode:

export ANTHROPIC_API_KEY=sk-ant-...
hoocode

You can also run /login and select an API-key provider to store the key in ~/.hoocode/auth.json.

See Providers for all supported providers, environment variables, and cloud-provider setup.

First session

Once hoocode starts, type a request and press Enter:

Summarize this repository and tell me how to run its checks.

By default, hoocode gives the model four tools:

  • read - read files
  • write - create or overwrite files
  • edit - patch files
  • bash - run shell commands

The built-in read-only SearchCodebase tool is available through tool options. HooCode runs in your current working directory and can modify files there. Use git or another checkpointing workflow if you want easy rollback.

Give hoocode project instructions

HooCode loads context files at startup. Add an AGENTS.md file to tell it how to work in a project:

# Project Instructions

- Run `npm run check` after code changes.
- Do not run production migrations locally.
- Keep responses concise.

HooCode loads:

  • ~/.hoocode/AGENTS.md for global instructions
  • AGENTS.md or CLAUDE.md from parent directories and the current directory

Restart hoocode, or run /reload, after changing context files.

Common things to try

Reference files

Type @ in the editor to fuzzy-search files, or pass files on the command line:

hoocode @README.md "Summarize this"
hoocode @src/app.ts @src/app.test.ts "Review these together"

Images can be pasted with Ctrl+V (Alt+V on Windows) or dragged into supported terminals.

Run shell commands

In interactive mode:

!npm run lint

The command output is sent to the model. Use !!command to run a command without adding its output to the model context.

Switch models

Use /model or Ctrl+L to choose a model. Use Shift+Tab to cycle thinking level. Use Ctrl+P / Shift+Ctrl+P to cycle through scoped models.

Continue later

Sessions are saved automatically:

hoocode -c                  # Continue most recent session
hoocode -r                  # Browse previous sessions
hoocode --session <path|id> # Open a specific session

Inside hoocode, use /resume, /new, /tree, /fork, and /clone to manage sessions.

Non-interactive mode

For one-shot prompts:

hoocode -p "Summarize this codebase"
cat README.md | hoocode -p "Summarize this text"
hoocode -p @screenshot.png "What's in this image?"

Use --mode json for JSON event output or --mode rpc for process integration.

Next steps

  • Using HooCode - interactive mode, slash commands, sessions, context files, and CLI reference.
  • Providers - authentication and model setup.
  • Settings - global and project configuration.
  • Keybindings - shortcuts and customization.
  • HooCode Packages - install shared extensions, skills, prompts, and themes.

Platform notes: Windows, Termux, tmux, Terminal setup, Shell aliases.