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

@blazfoxx/blazecli

v1.0.6

Published

Full-featured AI coding CLI tool with BlazeAPI integration

Readme

BlazeCLI

A full-featured AI coding CLI tool that integrates with BlazeAPI — an AI gateway supporting multiple models, streaming, embeddings, image generation, and more.

npm version License: MIT

Features

  • 🤖 Multi-model support — Access any model via BlazeAPI (Claude, GPT-4, Gemini, and more)
  • 💬 Interactive REPL — Full-featured interactive session with history and context management
  • 🛠️ Rich tool system — File read/write, bash execution, web search, and 40+ built-in tools
  • Streaming responses — Real-time streaming with Server-Sent Events
  • 🔐 Device code auth — OAuth2 device code flow for secure authentication
  • 📦 MCP support — Model Context Protocol client for extending capabilities
  • 🧠 Session memory — Persistent conversation history with context compaction
  • 🎨 Beautiful TUI — React/Ink-based terminal UI with themes
  • 🔌 Plugin system — Extend BlazeCLI with plugins

Installation

npm install -g @blazfoxx/blazecli

For detailed installation instructions, see INSTALL.md.

Quick Install

# Using npm
npm install -g @blazfoxx/blazecli

# Using yarn
yarn global add @blazfoxx/blazecli

# Using pnpm
pnpm add -g @blazfoxx/blazecli

Quick Start

# Login with BlazeAPI
blaze login

# Start interactive session
blaze

# Run a single prompt
blaze "Explain this codebase"

# Start with a specific model
blaze --model claude-3-5-sonnet-20241022

# Run in non-interactive mode
blaze --print "List all TypeScript files"

Commands

Interactive Commands

| Command | Description | |---------|-------------| | /help | Show help information | | /session | Manage sessions | | /model | Switch AI model | | /config | View/edit configuration | | /mcp | Manage MCP servers | | /clear | Clear conversation | | /exit | Exit BlazeCLI |

CLI Flags

| Flag | Description | |------|-------------| | --version | Show version number | | --model <name> | Specify model to use | | --print | Non-interactive mode, print output | | --stream | Enable/disable streaming | | --help | Show help |

Usage Examples

Basic Chat

# Interactive mode
blaze
> What is the difference between let and const in JavaScript?
> Can you show me an example?
> /exit

# Single prompt
blaze "Explain async/await in JavaScript"

Code Generation

blaze "Create a Node.js Express server with:
- Health check endpoint
- User CRUD endpoints
- JWT authentication
- Error handling middleware"

File Operations

# In interactive mode
> Read the package.json file and explain its dependencies
> Create a new file called utils.js with helper functions
> Update the README with installation instructions

Code Review

blaze "Review the code in src/api/client.ts and suggest improvements for:
- Error handling
- Performance
- Security"

Debugging

blaze "I'm getting a 'Cannot read property of undefined' error. 
Here's my code:
const user = data.users[0].profile.name;
What could be wrong?"

Git Operations

# In interactive mode
> Run `git status` and explain what files changed
> Run `git diff` and summarize the changes
> Create a commit message for these changes

Configuration

BlazeCLI uses two configuration locations:

  • Global: ~/.blaze/config.json — User-level settings
  • Project: .blaze/config.json — Project-level overrides

Configuration Options

{
  "model": "claude-3-5-sonnet-20241022",
  "apiUrl": "https://api.blazeapi.app",
  "outputStyle": "markdown",
  "theme": "dark",
  "streaming": true,
  "timeout": 120000
}

Environment Variables

| Variable | Description | Default | |----------|-------------|---------| | BLAZE_API_KEY | API key for BlazeAPI | - | | BLAZE_API_URL | Custom API base URL | https://api.blazeapi.app | | BLAZE_MODEL | Default model to use | claude-3-5-sonnet-20241022 | | BLAZE_TIMEOUT | Request timeout in milliseconds | 120000 |

Setting Configuration

# View current configuration
blaze /config

# Set a configuration value
blaze /config set model gpt-4o
blaze /config set theme light
blaze /config set outputStyle json

# Reset to defaults
blaze /config reset

Session Management

Listing Sessions

blaze /session list

Resuming a Session

blaze /session resume <session-id>

Exporting Sessions

blaze /session export session.json

Clearing Current Session

blaze /clear

MCP (Model Context Protocol)

BlazeCLI supports MCP servers for extended capabilities.

Adding an MCP Server

blaze /mcp add filesystem --command "npx -y @modelcontextprotocol/server-filesystem /path/to/dir"

Listing MCP Servers

blaze /mcp list

Connecting to an MCP Server

blaze /mcp connect filesystem

Development

Prerequisites

  • Node.js 18+
  • npm 8+

Setup

# Clone the repository
git clone https://github.com/blazfoxx/blazecli.git
cd blazecli

# Install dependencies
npm install

# Run in development mode
npm run dev

# Build for production
npm run build

# Run tests
npm test

# Type checking
npm run typecheck

# Linting
npm run lint

Project Structure

blazecli/
├── bin/              # CLI entry points
├── src/
│   ├── api/          # API client and communication
│   ├── auth/         # Authentication handling
│   ├── commands/     # CLI commands
│   ├── config/       # Configuration management
│   ├── mcp/          # MCP client implementation
│   ├── session/      # Session management
│   ├── tools/        # Built-in tools
│   ├── ui/           # Terminal UI components
│   └── utils/        # Utility functions
├── dist/             # Compiled JavaScript
└── tests/            # Test files

For detailed architecture, see ARCHITECTURE.md.

Testing

For comprehensive testing procedures, see TESTING.md.

Quick Tests

# Run unit tests
npm run test:unit

# Run integration tests
npm run test:integration

# Run with coverage
npm run test:coverage

Troubleshooting

Common Issues

"command not found: blaze"

Ensure npm global bin directory is in your PATH:

export PATH="$(npm config get prefix)/bin:$PATH"

Authentication Issues

Re-authenticate:

rm -rf ~/.blaze/.auth
blaze login

Connection Issues

Check API URL and connectivity:

blaze /config get apiUrl
curl -I https://api.blazeapi.app/health

For more troubleshooting, see INSTALL.md.

Contributing

We welcome contributions! Please follow these steps:

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Development Guidelines

  • Follow the existing code style
  • Write tests for new features
  • Update documentation for API changes
  • Run npm run lint before committing
  • Ensure all tests pass (npm test)

License

MIT — See LICENSE for details.

Links

Support


Made with ❤️ by the BlazeAPI Team