Aihubmix SDK

Project Introduction

One Gateway, Infinite Models；one-stop request: OpenAI, Claude, Gemini, DeepSeek, Qwen, and over 500 AI models.

Features

@aihubmix/claude-code

Claude Code Router Package - Claude Code routing service

• Features：

  • Simplified configuration management
  • Automatic routing to different AI models
  • Quick start and shutdown
  • Easy configuration
  • Support for multiple routing rules
  • Long context processing
  • Web search support
  • Background task processing

• Use Cases：

  • Claude Code tool integration
  • Development tool integration
  • Code editor plugins
  • Automated code generation
  • Intelligent task routing

📖 View Detailed Documentation | 📦 npm package

@aihubmix/ai-sdk-provider

AI SDK Provider Package - Provides unified model access interface for Vercel AI SDK

v1.0.1 - Compatible with AI SDK v6

• Features：

  • Support for 500+ AI models unified access
  • Compatible with Vercel AI SDK v6 interface
  • Automatic model routing and load balancing
  • Unified error handling and retry mechanisms
  • TypeScript type support
  • Text generation, streaming text, image generation
  • Embedding vectors, structured data generation
  • Speech synthesis, speech-to-text
  • Tool support (such as web search)

• Use Cases：

  • Next.js application integration
  • Vercel AI SDK projects
  • AI applications requiring multi-model support
  • Text generation and processing
  • Image generation applications
  • Speech processing applications

📖 View Detailed Documentation | 📦 npm package

@aihubmix/mcp

MCP (Model Context Protocol) Package - Model Context Protocol implementation

• Features：

  • MCP protocol standard implementation
  • Tool and resource management
  • File operation support
  • Image generation tools
  • API call tools
  • Multi-client support (Cursor, Cherry Studio, Claude Desktop)
  • Flexible configuration options

• Use Cases：

  • AI assistant integration
  • Toolchain development
  • Automated workflows
  • Code editor extensions
  • Desktop application integration

📖 View Detailed Documentation | 📦 npm package

PR Guidelines

Commit Message Format

Use Conventional Commits specification：

<type>[<scope>]: <description>

[optional body]

[optional footer(s)]

Type Descriptions

• feat: New feature
• fix: Bug fix
• docs: Documentation updates
• style: Code formatting changes (changes that don't affect code execution)
• refactor: Code refactoring (code changes that are neither new features nor bug fixes)
• perf: Performance optimization
• test: Testing related
• build: Build system or external dependency changes
• ci: CI/CD related changes
• chore: Build process or auxiliary tool changes
• revert: Revert to previous version

Package Name Specification

Specify package name in commit messages, format: <type>[<scope>]: <description>

Examples

feat[ai-sdk-provider]: Add Gemini model support
fix[claude-code]: Fix code generation bug
docs[mcp]: Update API documentation
refactor[ai-sdk-provider]: Refactor model routing logic
test[claude-code]: Add unit tests
chore[mcp]: Update dependency versions
perf[ai-sdk-provider]: Optimize model response speed

PR Title Guidelines

PR titles should be concise and clear, format: <type>[<scope>]: <description>

Examples

feat[ai-sdk-provider]: Add Gemini model support
fix[claude-code]: Fix multi-line code generation issue
docs[mcp]: Improve tool usage documentation
refactor[ai-sdk-provider]: Refactor model routing logic

PR Description Template

## Change Type
- [ ] New feature (feat)
- [ ] Bug fix (fix)
- [ ] Documentation (docs)
- [ ] Style (style)
- [ ] Refactor (refactor)
- [ ] Performance optimization (perf)
- [ ] Test (test)
- [ ] Build (build)
- [ ] CI/CD (ci)
- [ ] Build tools (chore)
- [ ] Revert (revert)

## Scope
- [ ] ai-sdk-provider
- [ ] claude-code
- [ ] mcp

## Change Description
Briefly describe the content and reason for this change

## Testing
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed
- [ ] Type checking passes
- [ ] Code formatting check passes

## Related Issues
Closes #<issue-number>
Fixes #<issue-number>

## Checklist
- [ ] Code follows project coding standards
- [ ] New features include corresponding tests
- [ ] Documentation updated (if API changes)
- [ ] Commit messages follow Conventional Commits specification
- [ ] All CI checks pass

Code Review Requirements

1. Feature Completeness: Ensure new features are complete and work properly
2. Test Coverage: New features should include corresponding tests, test coverage should not decrease
3. Documentation Updates: If there are API changes, update relevant documentation and type definitions
4. Type Safety: TypeScript projects should ensure type safety, no type errors
5. Performance Considerations: Avoid introducing performance issues, conduct performance testing when necessary
6. Code Quality: Follow project coding standards, code should be concise and readable
7. Backward Compatibility: Ensure changes don't break existing functionality

Merge Requirements

• At least 1 reviewer approval required
• Code coverage cannot decrease
• No major security vulnerabilities
• Commit messages comply with specifications
• Code passes all quality checks

Development Workflow

1. Fork Project: Fork the main repository to your GitHub account
2. Create Branch: Create a feature branch from the main branch

   git checkout -b feat/your-feature-name

3. Develop Feature: Develop in the corresponding package
4. Run Tests: Ensure all tests pass

   pnpm test
   pnpm lint
   pnpm type-check

5. Commit Code: Use standardized commit messages

   git commit -m "feat[package-name]: your commit message"

6. Push Branch: Push your feature branch

   git push origin feat/your-feature-name

7. Create PR: Create Pull Request on GitHub
8. Code Review: Wait for reviewer feedback and handle responses
9. Merge: Merge to main branch after review approval

Release Process

1. Create Changeset: Use pnpm changeset to record changes
2. Update Version: Use pnpm version to update version number
3. Build Project: Ensure build success

   pnpm build

4. Publish: Use pnpm release to publish to npm
5. Create Release: Create Release on GitHub

Notes

• Ensure Node.js 18+ version is used
• Use pnpm as package manager
• All packages are linked through workspace, no manual publishing required for local use
• Ensure PR guidelines are followed before submitting code