npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@bluehawks/cli

v1.0.52

Published

A production-ready multi-agent AI CLI assistant

Readme

Bluehawks CLI 🦅

License Node TypeScript

A powerful, production-ready multi-agent AI CLI assistant for terminal-based coding assistance. Built with TypeScript, featuring an extensible plugin architecture, hooks system, and MCP integration.

✨ Features

  • 🤖 Multi-Agent Architecture - Specialized agents for coding, research, and shell tasks
  • 💬 Interactive & Headless Modes - Use interactively or in scripts/CI
  • 🔌 Plugin System - Extend with custom commands, tools, and agents
  • 🪝 Hooks System - Lifecycle hooks for tool execution and session events
  • 🔗 MCP Integration - Connect to external data sources via Model Context Protocol
  • 📝 Session Management - Resume previous conversations, named sessions
  • Streaming Responses - Real-time token streaming
  • 🛠️ Built-in Tools - File operations, shell commands, git integration

📦 Installation

From npm

npm install -g @bluehawks/cli

From Source

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

🚀 Quick Start

1. Configure API Key

Create configuration file at ~/.bluehawks/.env:

BLUEHAWKS_API_KEY=your-api-key
BLUEHAWKS_API_URL=https://api.bluehawks.ai/v1
BLUEHAWKS_MODEL=qwen-coder-32b

2. Run the CLI

Interactive Mode:

bluehawks

Headless Mode (for scripts/CI):

bluehawks -p "explain this codebase" --json

🧠 Model Configuration

Bluehawks supports any OpenAI-compatible API endpoint. You can configure the model in several ways:

Environment Variables

Set these in ~/.bluehawks/.env or your shell:

BLUEHAWKS_API_KEY=your-api-key
BLUEHAWKS_API_URL=https://api.bluehawks.ai/v1
BLUEHAWKS_MODEL=Qwen/Qwen3-8B

CLI Flag

Override the model for a single session:

bluehawks --model Qwen/Qwen3-32B

Recommended Models

| Model | Best For | Notes | |-------|----------|-------| | Qwen/Qwen3-0.6B | Quick responses, simple tasks | Fastest, but limited tool calling | | Qwen/Qwen3-8B | Recommended default | Good balance of speed and capability | | Qwen/Qwen3-32B | Complex coding tasks | Best for large refactors, multi-file changes | | Qwen/Qwen3-Coder-32B | Code-specific tasks | Optimized for coding, uses vLLM auto-tool parser |

Using Custom/Local Models

You can point Bluehawks to any OpenAI-compatible endpoint:

# Using Ollama locally
export BLUEHAWKS_API_URL=http://localhost:11434/v1
export BLUEHAWKS_MODEL=qwen3:8b
export BLUEHAWKS_API_KEY=ollama  # Ollama doesn't need real key
bluehawks

# Using a custom vLLM server
export BLUEHAWKS_API_URL=http://your-server:8000/v1
export BLUEHAWKS_MODEL=Qwen/Qwen3-32B
bluehawks

Model-Specific Tips

  • For Qwen3 models: Use Temperature=0.7, TopP=0.8 (Bluehawks uses these by default)
  • For tool-heavy workflows: Use 8B+ models for reliable function calling
  • For thinking/reasoning: Qwen3 supports enable_thinking mode—the CLI automatically strips <think> tags from output

💻 Usage

Commands

# Start interactive session
bluehawks

# Run with initial prompt
bluehawks -p "refactor the auth module"

# Continue last session
bluehawks -c

# Resume specific session
bluehawks -r my-session

# List saved sessions
bluehawks sessions

# List available tools
bluehawks tools

# Manage plugins
bluehawks plugins

CLI Flags

| Flag | Description | |------|-------------| | -p, --prompt <text> | Initial prompt to send | | -c, --continue | Continue most recent session | | -r, --resume <name> | Resume named session | | --max-turns <n> | Limit agentic iterations | | --system-prompt <text> | Override system prompt | | --append-system-prompt <text> | Append to system prompt | | --add-dir <dirs...> | Additional context directories | | --output-format <format> | Output format: text, json, stream-json | | --json | Output in JSON format | | -y, --yes | Auto-approve all tool calls (YOLO mode) |

Slash Commands

Inside the CLI, use these commands:

| Command | Description | |---------|-------------| | /help | Show available commands | | /clear | Clear conversation history | | /save [name] | Save current session | | /stats | Show session statistics | | /plan | Toggle planning mode | | /yolo | Toggle auto-approval mode | | /exit | Exit the CLI |

🔌 Plugins

Create plugins to extend functionality with custom commands, tools, and agents.

Plugin Structure

~/.bluehawks/plugins/my-plugin/
├── plugin.json          # Plugin manifest
├── commands/
│   └── greet.js        # Command handler
└── tools/
    └── custom_tool.js  # Tool handler

Plugin Manifest (plugin.json)

{
  "name": "my-plugin",
  "version": "1.0.0",
  "description": "My custom plugin",
  "commands": [
    {
      "name": "greet",
      "description": "Say hello",
      "handler": "commands/greet.js"
    }
  ],
  "tools": [
    {
      "name": "custom_tool",
      "description": "My custom tool",
      "handler": "tools/custom_tool.js",
      "parameters": {
        "type": "object",
        "properties": {
          "input": { "type": "string" }
        }
      }
    }
  ],
  "agents": [
    {
      "name": "reviewer",
      "description": "Code review agent",
      "systemPrompt": "You are an expert code reviewer..."
    }
  ]
}

🪝 Hooks

Hooks allow you to intercept and modify CLI behavior at various lifecycle events.

Available Hooks

| Event | Trigger | |-------|---------| | SessionStart | When CLI session starts | | PreToolUse | Before a tool executes (can block) | | PostToolUse | After successful tool execution | | PostToolUseFailure | After tool execution fails | | Stop | Before CLI exits |

Hook Configuration

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "run_command",
        "command": "echo 'Tool: $HOOK_INPUT' >> ~/tool.log"
      }
    ]
  }
}

🔗 MCP Integration

Connect to external data sources using the Model Context Protocol.

Configuration (.mcp.json)

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-github"]
    },
    "filesystem": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-filesystem", "/path/to/dir"]
    }
  }
}

MCP tools are automatically registered and available to the agent.

🛠️ Built-in Tools

| Tool | Description | |------|-------------| | read_file | Read file contents | | write_file | Write content to file | | search_files | Search files by pattern | | run_command | Execute shell commands | | grep_search | Search file contents | | git_status | Get git repository status | | list_directory | List directory contents |

🏗️ Architecture

src/
├── cli/                 # CLI components (Ink/React)
│   ├── app.tsx         # Main application component
│   └── commands/       # Slash command handlers
├── core/
│   ├── agents/         # Agent implementations
│   │   ├── agent.ts    # Base agent class
│   │   └── orchestrator.ts
│   ├── api/            # API client
│   ├── hooks/          # Hooks system
│   ├── mcp/            # MCP integration
│   ├── plugins/        # Plugin loader
│   ├── session/        # Session management
│   └── tools/          # Tool definitions & executor
└── config/             # Configuration constants

🧪 Development

# Build
npm run build

# Watch mode
npm run dev

# Run tests
npm test

# Lint
npm run lint

# Format
npm run format

📄 License

Apache 2.0 - See LICENSE for details.

🤝 Contributing

Contributions welcome! Please read our contributing guidelines before submitting PRs.

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Run tests and linting
  5. Submit a pull request

📞 Support


Built with ❤️ by Bluehawks AI