Summary

goehou/tabbit-toy offers a local service (Tabbit2API) exposing Tabbit browser's AI models (Claude, GPT, Gemini) via an OpenAI-compatible API. It targets developers and researchers needing programmatic access, simplifying local integration and experimentation without the Tabbit UI.

How It Works

This project reverse-engineers Tabbit's protocols to act as a local proxy. It captures Tabbit's authentication (via exported cookies) and model interaction logic, translating requests into an OpenAI-compatible format. A Node.js server forwards these to Tabbit's backend, processes SSE stream responses, and returns them, bypassing the Tabbit browser UI for inference.

Quick Start & Requirements

• Primary install/run command: node src/server.mjs
• Prerequisites: Tabbit browser (tabbit.ai), Node.js 18+, Chrome extension. Tabbit Pro membership (set Tabbit as default browser) needed for premium models.
• Setup: Install Tabbit, load cookie-helper-extension, export cookies, get Tabbit version via console, configure .env, run server.
• Links: Tabbit Browser: https://web.tabbit.ai/, Docs: docs/逆向流程与协议.md, Roadmap: docs/实现路线图.md.

Highlighted Details

• OpenAI-compatible API (/v1/chat/completions, /v1/models).
• Supports numerous free/Pro AI models (Claude, GPT, Gemini, DeepSeek, Qwen, etc.).
• Includes Chrome extension for simplified cookie export.
• Handles Tabbit-specific authentication, signing, and streaming.

Maintenance & Community

Relies on reverse engineering Tabbit's protocols, making it prone to breakage with Tabbit updates. No explicit community channels or contributor information are provided. A roadmap is available in docs/.

Licensing & Compatibility

No formal license. Explicitly stated for "personal learning and research only," prohibiting commercial use, high concurrency, and account redistribution, severely restricting commercial adoption.

Limitations & Caveats

• Non-Commercial Use Only: Strictly personal learning/research; commercial use prohibited.
• Tabbit Dependency: Requires Tabbit browser installation and operation.
• Fragility: Reverse-engineered nature means Tabbit updates can break functionality.
• Cookie Expiration: Auth tokens expire (approx. 7 days), requiring periodic re-export.
• Session Issues: chat_session_id invalidation can affect service availability.