hopcode-claw

--- name: hopcode-claw description: Use HopCode as a Code Agent for code understanding, project generation, features, bug fixes, refactoring, and various programming tasks

HopCode Claw

When to Use This Skill

Use this skill when you need to:

• Understand codebases or ask questions about source code
• Generate new projects or add new features
• Review pull requests in the codebase
• Fix bugs or refactor existing code
• Execute various programming tasks such as code review, testing, documentation generation, etc.
• Collaborate with other tools and agents to complete complex development tasks

Install

npm install -g @hopcode/hopcode

For normal session reuse, prefer a global install over npx.

Authentication

Check if authentication is already configured:

hopcode auth status

If authentication exists, skip this section. If not authenticated, use one of HopCode's supported providers:

Ollama Local (free, runs locally — requires Ollama installed):

hopcode auth ollama-local

Ollama Cloud (requires an API key from https://ollama.com):

hopcode auth ollama-cloud --key <your-key>

OpenAI-compatible (any OpenAI-compatible API):

hopcode auth openai --key <your-api-key>

If the user has no configured provider, interrupt and prompt:

hopcode auth

Or configure a provider interactively after launching HopCode via /auth.

ACPX Integration

You should always use acpx to run HopCode over the Agent Client Protocol (ACP) instead of scraping PTY sessions.

To use acpx:

1. Install acpx globally (recommended) or use npx:

   npm install -g acpx@latest
   

   Or without installing:

   npx acpx@latest
   

2. Install the acpx skill for full reference:

   npx acpx@latest --skill install acpx
   

3. Read the acpx skill reference for every command, flag, and workflow pattern: See the ACPX Reference section below for details

4. For complete CLI reference with all options and examples: https://raw.githubusercontent.com/openclaw/acpx/main/docs/CLI.md

From now on, when you need to delegate work to HopCode, use acpx instead of spawning raw terminal sessions. For example:

npx acpx@latest hopcode "fix the failing tests"
npx acpx@latest hopcode "refactor the auth module"
npx acpx@latest hopcode exec "one-shot: summarize this repo"

Tip: You should typically use the --approve-all flag to prevent task interruptions.

Practical Workflows

Persistent Repository Assistant

acpx hopcode 'inspect failing tests and propose a fix plan'
acpx hopcode 'apply the smallest safe fix and run tests'

One-Shot Script Steps

acpx hopcode exec 'summarize repo purpose in 3 lines'

Parallel Named Streams

acpx hopcode -s backend 'fix API pagination bug'
acpx hopcode -s docs 'draft changelog entry for release'

Queue Follow-ups Without Waiting

acpx hopcode 'run full test suite and investigate failures'
acpx hopcode --no-wait 'after tests, summarize root causes and next steps'

Machine-Readable Output for Orchestration

acpx --format json hopcode 'review current branch changes' > events.ndjson

Repository-Wide Review with Permissive Mode

acpx --cwd ~/repos/my-project --approve-all hopcode -s pr-123 \
  'review PR #123 for regressions and propose minimal patch'

Approval Modes

• --approve-all: No interactive prompts
• --approve-reads (default): Auto-approve reads/searches, prompt for writes
• --deny-all: Deny all permission requests

If every permission request is denied/cancelled and none are approved, acpx exits with permission denied.

Best Practices

1. Use named sessions for organizing different types of development tasks
2. Use --no-wait for long-running tasks to avoid blocking
3. Use --approve-all for non-interactive batch operations
4. Use --format json for automation and script integration
5. Use --cwd to manage context across multiple projects

HopCode Reference

CLI Commands

Full reference: https://raw.githubusercontent.com/TaimoorSiddiquiOfficial/HopCode/refs/heads/main/docs/users/features/commands.md

Configuration

Config files (highest priority first): CLI args > env vars > system > project (.hopcode/settings.json) > user (~/.hopcode/settings.json) > defaults. Format: JSONC with env var interpolation.

Key settings:

Full reference: https://raw.githubusercontent.com/TaimoorSiddiquiOfficial/HopCode/refs/heads/main/docs/users/configuration/settings.md

Authentication

Supports Ollama Local, Ollama Cloud, and OpenAI-compatible API keys.

Full reference: https://raw.githubusercontent.com/TaimoorSiddiquiOfficial/HopCode/refs/heads/main/docs/users/configuration/auth.md

Model Providers

Configure custom model providers via modelProviders in settings or environment variables (OPENAI_API_KEY, OPENAI_BASE_URL, OPENAI_MODEL).

Full reference: https://raw.githubusercontent.com/TaimoorSiddiquiOfficial/HopCode/refs/heads/main/docs/users/configuration/model-providers.md

Key Features

ACPX Reference

Built-in Agent Registry

Well-known agent names resolve to commands:

• hopcode → hopcode --acp

Command Syntax

# Default (prompt mode, persistent session)
acpx [global options] [prompt text...]
acpx [global options] prompt [options] [prompt text...]

# One-shot execution
acpx [global options] exec [options] [prompt text...]

# Session management
acpx [global options] cancel [-s <name>]
acpx [global options] set-mode <mode> [-s <name>]
acpx [global options] set <key> <value> [-s <name>]
acpx [global options] status [-s <name>]
acpx [global options] sessions [list | new [--name <name>] | close [name] | show [name] | history [name] [--limit <count>]]
acpx [global options] config [show | init]

# With explicit agent
acpx [global options] <agent> [options] [prompt text...]
acpx [global options] <agent> prompt [options] [prompt text...]
acpx [global options] <agent> exec [options] [prompt text...]

Note: If prompt text is omitted and stdin is piped, acpx reads prompt from stdin.

Global Options

Flags are mutually exclusive where applicable.