CLI v0.6.22

    Use FlickClaw CLI

    Check your setup, list available agents, then configure an agent for your tool.

    This page helps you run and verify FlickClaw CLI. To configure a specific agent, open its page and choose your target tool.

    Check your setup
    $ npm exec --yes @flickclaw/cli@latest -- doctor
    Check version
    $ npm exec --yes @flickclaw/cli@latest -- version
    List available agents
    $ npm exec --yes @flickclaw/cli@latest -- list
    Optional — global install$ npm install -g @flickclaw/cli $ flickclaw doctor

    No global install required — npm exec runs directly. Use global install only if you prefer the shorter flickclaw command.

    Configure an agent

    Once the CLI is running, open an agent page, choose your target tool, and copy the generated command.

    Example — after choosing an agent$ npm exec --yes @flickclaw/cli@latest -- install product-claw --target cursor

    This installs a specific agent into a specific tool. Choose any of the 16 agents and 8 target tools.

    Supported Targets

    8 AI tools + All bundle. Each agent installs pre-configured files for its target.

    Claude Code

    project / global

    OpenClaw

    workspace / global

    Codex

    project / global

    Cursor

    project

    Windsurf

    project

    Aider

    project

    Ollama

    project

    Hermes

    workspace / global

    All

    All tools for this agent at once

    Verify the Package

    Check version
    $ npm view @flickclaw/cli version
    Verify integrity
    $ npm view @flickclaw/cli dist.integrity

    Security Model

    npm provenance

    Published with provenance attestations linking the package to its source repository and build process. Verify with npm view.

    No postinstall scripts

    The package contains no preinstall, install, or postinstall scripts. No hidden code execution during npm install.

    No Pro content embedded

    All agent packages are fetched from the authenticated FlickClaw API. The npm package only contains CLI logic — zero agent data.

    No secrets in package

    No API keys, tokens, or credentials are included. Authentication happens at runtime via FLICKCLAW_TOKEN or flickclaw login.

    Server-side access control

    Free agents install for all users. Pro agents require an active subscription. Access is verified on every API call.

    Path traversal protection

    All install paths are validated against traversal, absolute paths, and symlinks. Files are only written inside the project directory.

    Token redaction

    API tokens are never printed in logs or error messages. Authentication is handled securely with local config.

    Minimal dependencies

    The CLI has zero runtime dependencies. No supply chain surface from third-party packages.

    Ready to start?

    Browse agents, choose your tool, and install with one command.

    Browse Agents