CC Switch is a desktop application built with Tauri (Rust backend + React/TypeScript frontend) that serves as a unified management hub for multiple AI coding assistants, including Claude Code, Claude Desktop, Codex, Gemini CLI, Grok Build, OpenCode, OpenClaw, and Hermes Agent. Its core function is provider switching: it manages configurations, API keys, OAuth tokens, and MCP servers across these tools, and provides a local HTTP proxy that routes API requests to different AI providers with failover, circuit breaking, and usage tracking. The application also includes session management, skills/prompts synchronization, cloud sync (S3/WebDAV), deep link import/export, and a usage dashboard with cost tracking. The architecture follows a command-service-DAO pattern in Rust, with a React frontend using TanStack Query for state management, react-hook-form for forms, and shadcn/ui components. The proxy subsystem is particularly sophisticated, implementing format conversion bridges between different AI API protocols (Anthropic Messages, OpenAI Chat/Responses, Gemini), streaming transforms, thinking budget optimization, cache injection, and content encoding handling with bomb protection. The frontend is organized around per-app provider forms, a universal provider panel, and settings pages for proxy, MCP, skills, and usage. Key features include: 50+ provider presets for third-party API relay services, one-click provider switching with live config backup/restore, a local proxy with auto-failover and circuit breaker, session history browsing across supported apps, skills installation from GitHub repos, prompt management with per-app sync, and usage statistics with custom pricing. The application supports i18n (English, Japanese, Chinese) and runs on Windows, macOS, and Linux.
This repository implements a deep research assistant web application that combines large language models (LLMs) with web search capabilities to generate comprehensive research reports. Built with Next.js 15, React, and Tailwind CSS, it features a client-side interface for topic input and research workflow management, backed by API routes that proxy requests to external AI and search services to protect API keys. The system orchestrates an iterative research process: planning sub-queries, executing parallel searches across multiple providers (Tavily, Firecrawl, Exa, etc.), analyzing results with auto-review cycles, and generating cited final reports. Key architectural elements include Zustand-based state management with localForage persistence, a Model Context Protocol (MCP) server for standardized tool/resource exposure, PWA support for offline installation, and modular components for knowledge base management, file parsing, and real-time progress streaming via Server-Sent Events (SSE).
This repository is a curated, multi-vendor collection of leaked system prompts from major AI chatbots (ChatGPT, Claude, Gemini, Grok, Perplexity, DeepSeek, etc.), captured verbatim from production systems. It serves as a reference corpus for studying AI behavior instructions, safety guardrails, tool definitions, and product positioning across model versions and vendors. The repository also includes Claude Code bundled skills (code review, design-sync, dataviz, deep research) and Claude Design starter components, which are supplementary tooling. While primarily a documentation archive, it contains some well-crafted reusable components such as color palette validation scripts, a design system build/diff pipeline, and a deep research workflow script. The prompts are organized by vendor with version tracking, and the repository is actively maintained with recent updates. However, the tooling scripts lack dependency pinning, and the prompts are time-sensitive snapshots that will drift as products evolve.
AIClient2API (A2) is a production-grade API proxy/gateway that converts proprietary AI provider APIs (Gemini, Claude/Kiro, Qwen, Codex, Grok, OpenAI, and more) into standard OpenAI-compatible endpoints (`/v1/chat/completions`, `/v1/messages`, `/v1beta/models`). It supports multi-account OAuth credential pools with automatic token refresh, health checks, and fallback routing, enabling clients to break free-tier restrictions. The server is built on Node.js with a master-worker architecture for process management, a plugin system for extensibility (authentication, monitoring, usage statistics, API key sharing), and a Go-based TLS sidecar for JA3/JA4 bypass. A full web management console (static HTML/CSS/JS) provides configuration, provider management, credential file upload, interactive playground, and usage monitoring. The codebase demonstrates strong patterns (strategy, factory, adapter, converter) but suffers from some monolithic utility files, hardcoded provider mappings, and high maintenance overhead from multiple OAuth implementations.
CtxPort is a browser extension and companion documentation website that lets users copy AI conversations (from ChatGPT, Claude, Gemini, DeepSeek, Grok, Doubao, GitHub) as structured Markdown Context Bundles. It solves 'context rot' by enabling portable, lossless migration of conversations between AI tools without uploading data to third parties. The architecture is a modern monorepo using pnpm workspaces and Turborepo, with separate packages for schema validation (Zod), markdown serialization, plugin-based extraction, and shared UI components. The browser extension (Manifest V3, WXT, React 19, Tailwind CSS 4) injects copy buttons and sidebar list icons into supported platforms, while the documentation website (Next.js + Nextra) provides multilingual (en/zh) user guides and feature descriptions. All processing is client-side; no data is uploaded. The codebase demonstrates strong engineering practices including a plugin system for extensibility, a strategy pattern for content flatteners, clean separation of concerns, and comprehensive CI/CD pipelines. Some fragility exists in DOM selectors and platform APIs, but the architecture is well-structured for adaptation.
The repository serves as the official website and resource hub for the Noi desktop application. It contains the documentation site built with Docusaurus and Tailwind CSS, localization files for the application's UI, a prompt library for AI-assisted workflows, and example configuration files. While the core desktop application source is not present in this repository, the provided resources demonstrate good practices in internationalization, configuration-driven design, and prompt management. The documentation site is a well-crafted web application that effectively communicates the features and usage of the Noi desktop app.
This repository contains demonstration scripts and documentation for the GPT_API_free service, a forwarding proxy that provides free access to various large language models including GPT, DeepSeek, Claude, Gemini, and others. The actual forwarding server is not included; instead, the repository offers Python examples using the OpenAI library and standard HTTP requests to illustrate how to interact with the service's API endpoints for chat completions, image generation/editing, audio transcription, speech synthesis, and file analysis. The code is minimal and educational, focusing on replacing the base URL and authentication header to route requests through the proxy. The codebase is primarily a collection of usage examples tightly coupled to the external service's address and API key format. There is no production logic, no tests, and no independent reusable components. The demos follow standard patterns for calling OpenAI-compatible APIs and serve as a quick-start guide for developers integrating the service. As such, the repository does not represent a standalone application but rather a documentation supplement for the GPT_API_free project.
CL4R1T4S is a repository that functions as a curated archive of extracted system prompts, tool definitions, and behavioral instructions from major AI models and agent platforms. It contains no executable code, data pipelines, or analytical scripts. The entire repository consists of flat text and markdown files organized by vendor (e.g., OPENAI, ANTHROPIC, XAI, CURSOR, REPLIT), each containing what are claimed to be verbatim system prompts for models like ChatGPT, Claude, Grok, Gemini, and various coding agents like Devin, Cursor, Windsurf, and Replit. The repository's stated purpose is transparency — making visible the hidden instructions that shape AI behavior. However, from a data engineering or software architecture perspective, there is no data lineage to trace, no transformation logic to evaluate, and no code to assess for craftsmanship. The files are static documents with no programmatic relationship between them. There are no tests, no dependency manifests, no environment definitions, and no data processing logic of any kind. The collection has some research value as a comparative corpus for prompt analysis, but it is entirely unstructured as data. There are no schemas, no metadata standards, no versioning discipline, and no way to verify the authenticity or currency of the extracted prompts. The README itself contains signs of prompt injection attempts and unprofessional editorializing that undermine the project's credibility as a serious transparency effort. There are no reusable components, no engineering patterns, and no data operations present.
The ZeroClaw-Android repository is an archived Android application project that was intended as an experiment to create a home for AI agents on Android. The README explicitly states the project is archived due to scope concerns and safety issues with the largely AI-generated codebase. No actual source code is visible in the provided file tree beyond the README and a ZIP archive (ZeroClaw-Android-main.zip) whose contents cannot be inspected. The repository consists almost entirely of Git metadata, indicating the source code is not directly accessible for analysis. Without access to the application code, it is impossible to assess architecture, functionality, or code quality. The project is marked as abandoned with no maintenance activity.