This project provides an "ULTRA DANGEROUS CLAUDE CODE EMULATOR" designed to make API requests identical to those made by Claude Code. It functions as an OAuth proxy server. However, the project is archived and superseded by CLIProxyAPI, which offers a more comprehensive solution supporting Claude Code, Gemini CLI, and ChatGPT Codex.

How It Works

This project is an OAuth proxy server built using Hono and Bun. It exposes an OpenAPI-documented Messages API that includes built-in token management and streaming capabilities. The core design focuses on intercepting and replicating API request patterns to achieve Claude Code compatibility.

Quick Start & Requirements

• Installation: Installation is recommended via the published npm package: npm install -g not-claude-code-emulator, followed by not-claude-code-emulator install. The README explicitly advises against using a source checkout for installation.
• Prerequisites: The essential dependencies are Bun and GitHub CLI.
• Links: Official documentation is accessible at http://localhost:3000/docs, and the OpenAPI specification can be found at http://localhost:3000/openapi.json.

Highlighted Details

• Features an OpenAPI-documented Messages API for clear interface definition.
• Includes integrated token management and streaming support for API interactions.
• Offers key server endpoints for documentation (/docs), API specification (/openapi.json), core messaging (/v1/messages), and health checks (/health).

Maintenance & Community

This project is marked as archived, indicating it is no longer under active development or maintenance. The README directs users to CLIProxyAPI as a successor for more extensive functionality. No specific community channels or contributor information is detailed.

Licensing & Compatibility

The provided README does not specify a software license. Consequently, the terms for commercial use, closed-source linking, or redistribution remain undetermined.

Limitations & Caveats

The most significant limitation is the project's archived status, meaning it is not actively maintained. Users seeking broader compatibility or ongoing support should refer to the recommended successor, CLIProxyAPI, which supports a wider array of code models.