This repository implements an MCP (Model Context Protocol) server that provides semantic code search capabilities for AI assistants. It enables developers to search their codebases by meaning rather than just keywords, using local AI models to ensure privacy and avoid external API calls. The system features semantic code search using embeddings (nomic-embed-text-v1.5 with MRL), incremental indexing with file watching, efficient SQLite-based caching of embeddings, cross-platform package version checking across 20+ ecosystems, workspace switching capabilities, and resource throttling to prevent system overload during indexing. The codebase demonstrates strong engineering practices with proper error handling, modular design, and attention to user experience.
This repository implements a comprehensive toolkit for detecting and removing Google DeepMind's SynthID watermark from AI-generated images, primarily targeting Gemini models. It provides multiple bypass versions (V1–V4) that use pure signal-processing techniques—frequency-domain phase scrambling, JPEG degradation, elastic deformation, VAE round-tripping, and cross-color consensus codebook subtraction—to disrupt the embedded watermark while preserving visual fidelity. The codebase includes a drag-and-drop GUI, CLI tools, batch processing scripts, and a human-in-the-loop calibration workflow. It also contains extensive watermark investigation scripts that validated the watermark's presence in over 123,000 image pairs. While primarily an application (tool for watermark removal), it has a strong research character due to its analytical components and large-scale validation studies.
This repository is a comprehensive, production-focused AI system design guide, not a software application. It contains over 170 markdown files organized into 19 chapters covering the full lifecycle of building and operating AI systems: foundations (transformers, tokenization), model landscape (selection, pricing), training and adaptation (fine-tuning, LoRA, RLHF), inference optimization (KV cache, speculative decoding, batching), prompting and context engineering, retrieval systems (RAG, chunking, vector databases, hybrid search, GraphRAG), agentic systems (ReAct, MCP, multi-agent orchestration, durable execution), memory and state management, frameworks and tools (LangChain, LangGraph, LlamaIndex, DSPy, Semantic Kernel), document processing, infrastructure and MLOps (CI/CD, AI gateways, FinOps), security and access control, reliability and safety (guardrails, ensemble methods, governance), evaluation and observability (LLM evaluation, benchmarks), design patterns and anti-patterns, and 20+ real-world case studies. It also includes interview preparation materials (question bank, answer frameworks, whiteboard exercises, job market trends) and transition guides for engineers moving into AI roles. The content is current as of mid-2026, referencing specific model versions, pricing, and protocols (MCP 2.0, A2A). While it contains no executable code, it serves as an authoritative reference for engineers designing and deploying AI systems in production.
Antigravity Manager is an Electron desktop application that serves as a multi-account manager and local API proxy gateway for AI models (Google Gemini, Claude, OpenAI-compatible). It allows users to pool multiple Google Cloud accounts, automatically rotates between them based on real-time quota and rate limits, and exposes a local proxy server that translates between OpenAI, Anthropic, and Gemini API protocols. The application handles OAuth token lifecycle, credential storage across OS keychains and encrypted files, and includes a React UI for account management, quota monitoring, and configuration. Architecturally, the app is a monolith with three major layers: an Electron main process that bootstraps a NestJS server (Fastify), a React renderer with TanStack Router and shadcn/ui, and a Python CLI for headless account operations. The proxy gateway is the most complex module, with controllers for OpenAI chat completions, Anthropic messages, Gemini models, batch jobs, file uploads, and WebSocket-based Responses API. Credential management is handled through a multi-provider master key system with migration paths, atomic file writes, and SQLite persistence via Drizzle ORM. The codebase also includes device identity profile manipulation (fingerprint spoofing) gated by environment variables, and binary patching of the agy CLI executable. The codebase demonstrates strong engineering practices with extensive Vitest unit tests (250+ test files), Playwright e2e tests, Zod schema validation at IPC boundaries, and structured error handling. However, it also carries risks: hardcoded model aliases and Google API endpoints, fragile binary patching logic, and a large surface area of credential storage strategies that may drift as OS APIs evolve. The repo is actively maintained with frequent commits and CI pipelines, but the complex fallback chains and security-sensitive code require careful ongoing maintenance.
Witsy is a feature-rich desktop AI assistant built with Electron and Vue 3. It operates as a Bring-Your-Own-Keys (BYOK) client, aggregating dozens of LLM providers (OpenAI, Anthropic, Google, Ollama, etc.) into a unified chat, agent, and automation platform. The architecture follows a standard Electron main/renderer process split, communicating via IPC, with a Vue 3 frontend and a Node.js backend. Beyond basic chat, Witsy provides a sophisticated agent system supporting multi-step workflows, A2A communication, scheduling, and webhooks. It includes a full RAG pipeline (document ingestion, chunking, embedding, vector search), a plugin system for tools (MCP, code execution, web browsing, image generation), and extensive voice capabilities (STT/TTS with multiple providers). Data is persisted locally as JSON files within workspaces, with a vector database for semantic memory and document retrieval. A key differentiator is its automation layer, which can control the desktop (text selection, pasting, app detection) via platform-specific automators (macOS, Windows, nut-js). It exposes a local HTTP API and a CLI for external integration. The MCP (Model Context Protocol) client allows it to connect to a vast ecosystem of third-party tools. While primarily an application, it contains significant data engineering components (RAG pipeline, memory manager, deep research orchestrator) that are tightly integrated into the app's workflow. The codebase is well-structured with a strong emphasis on testing, though its massive feature surface and reliance on external APIs introduce inherent complexity and maintenance challenges.
Claude Delegator is a Claude Code plugin that provides GPT (via Codex CLI) and Gemini (via Gemini CLI) as specialized expert subagents. It offers five domain experts (Architect, Plan Reviewer, Scope Analyst, Code Reviewer, Security Analyst) that can advise or implement based on task requirements. The plugin uses MCP (Model Context Protocol) to connect to external CLIs, featuring sophisticated delegation logic with proactive triggers, session management (single-shot and multi-turn), and response synthesis. A key innovation is the zero-dependency Gemini MCP bridge that wraps the Gemini CLI in a standard MCP interface.
SuperAgentX is a modular, open-source multi-agent AI framework designed for orchestrating autonomous agents that plan, act, and execute real-world workflows. It supports 100+ LLM providers (OpenAI, Azure, Gemini, Claude, Bedrock, Ollama, LiteLLM) and 10,000+ MCP tools via the Model Context Protocol. The architecture centers on `AgentXPipe` pipelines that sequence or parallelize agents, each composed of an `Engine` that wraps an LLM client and a set of tool handlers. Handlers are defined using a `@tool` decorator pattern that auto-generates LLM function schemas. The framework includes built-in human-in-the-loop approval channels (console, Slack, Teams), persistent memory with SQLite and vector stores (Chroma, OpenSearch), full observability via OpenTelemetry and SQL-based telemetry, and a CLI for project scaffolding. It also features a production-grade browser automation engine based on Playwright for tasks where APIs are unavailable.
This repository is a full-stack marketing demo application powered by Google Cloud generative AI (Vertex AI Gemini, Imagen). It provides an end-to-end workflow for generating campaign content (emails, social media posts, website copy, images), analyzing audiences via natural language to BigQuery, and managing assets across platforms. The frontend is a modern Angular 17 single-page application with Firebase authentication and hosting, while the backend is a FastAPI Python service deployed on Cloud Run. Terraform infrastructure-as-code provisions all GCP resources including BigQuery datasets, Vertex AI Search datastores, Dialogflow CX agents, and Google Drive folder templates for content export. The application showcases marketing use cases like trendspotting via GDELT news summarization, audience insights using structured and unstructured data, and interactive image editing with inpainting/outpainting. While primarily a demo application, the repository also contains several Jupyter notebooks exploring model tuning, text-to-SQL, and clustering explanations, making it a hybrid resource for both application developers and data scientists.
Androidify is a modular Android application that allows users to create personalized Android robot avatars using AI. It accepts a photo (from camera or gallery) or a text prompt, then generates a custom Android mascot image via a fine-tuned Imagen model through Firebase Vertex AI, with on-device Gemini Nano as a fallback for prompt generation and image validation. The app uses ML Kit for pose detection in the camera flow and subject segmentation for background removal. It features adaptive Jetpack Compose UIs across phones, tablets, foldables, and Android XR with shared element transitions. A companion Wear OS app enables one-tap installation of the generated avatar as a watch face, including APK creation and transfer via the Wearable Data Layer. The architecture is multi-module with custom Gradle plugins, Hilt DI, and feature flags via Firebase Remote Config. It is primarily an applied AI sample app, not a data research project, though it heavily relies on configurable AI prompts and model names.
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.
GeminiProChat is a minimal web UI for interacting with Google's Gemini Pro API. It is built as a server-side rendered application using Astro with SolidJS for interactive components. The application provides a chat interface where users can send messages and receive streaming responses from the Gemini model. It supports features like system role settings, temperature control, message history persistence, password protection, and PWA capabilities. The architecture consists of Astro pages (index, password), API endpoints (auth, generate), and SolidJS components for the chat generator, message rendering with markdown and code highlighting, and a theme toggle with view transitions. External dependencies include the Google Generative AI SDK (patched to use v1beta API), markdown-it for rendering, and Zag.js for slider components. The application can be deployed on Vercel, Netlify, Railway, Zeabur, or via Docker, with environment variables for API key, base URL, password, and model name.
This repository is an open-source terminal-based AI coding assistant built in Rust, clean-room reimplementing Anthropic's Claude Code. It provides an interactive TUI (ratatui) for multi-provider LLM conversation (Anthropic, OpenAI, Google, and 30+ OpenAI-compatible) with a rich tool ecosystem for file editing, bash execution, MCP integration, code analysis, web fetching, and agent orchestration. The architecture is modular: a provider abstraction layer (`LlmProvider` trait), plugin system, slash commands, session management, and an Agent Client Protocol (ACP) for external IDE integration. The codebase is organized into 12+ workspace crates with clear separation of concerns, but many modules are still in active refactoring (issue #232) with stubs, TODOs, and incomplete feature gates (36 experimental features). The permission system, tool budget enforcement, and streaming decoders demonstrate strong engineering, while dual feature flag systems and global mutable state introduce maintenance risk. Overall, it is a feature-rich, well-architected application with some rough edges from ongoing migration.
KEA Research is a full-stack multi-provider AI research chat application. The backend is a FastAPI service backed by SQLite/SQLAlchemy, exposing chat, admin, health, user, and TTS endpoints. The frontend is an Astro + TypeScript single-page app that stores chat history and pipeline data in IndexedDB, with a Bootstrap-based UI. Deployment is containerized via Docker Compose with nginx handling TLS and SSE-friendly proxying. The core product logic is a four-step research pipeline: initial multi-provider responses, Mixture-of-Agents refinement, peer evaluation, and a final KEA synthesis with facts, consensus, flagged claims, rankings, and confidence scores. A web admin panel manages providers, models, provider sets, users, and app settings, while the frontend supports research layers, bookmarks, notes, drafts, export, attachment ingestion, and text-to-speech via a Kokoro ONNX model.
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.
Vizra ADK is a retired Laravel package (final release v0.0.48) that provides a comprehensive framework for building AI agents with LLM orchestration, tool systems, memory, workflows, evaluations, tracing, and MCP integration. It is not a standalone application but a library designed to be installed into Laravel projects. The architecture follows Laravel package conventions: service providers, facades (Agent, Workflow), Eloquent models, Artisan commands, Livewire components, and database migrations. Key entry points include the Agent facade for running agents, the Workflow facade for orchestrating multi-agent workflows, and a set of CLI generators for scaffolding agents, tools, and evaluations. The system supports multiple LLM providers via Prism PHP, persistent memory (session, user, vector), tool chaining, sub-agent delegation, and an evaluation framework with LLM-as-a-Judge assertions. The codebase is well-structured with strong test coverage (Pest + Mockery), but the package is officially retired with no further development, leading to high technical drift as dependencies age out. Despite retirement, many components (e.g., ToolChain, VersionablePrompts, AgentVectorProxy, HasLogging) are self-contained and demonstrate reusable patterns suitable for extraction into new projects.
This repository serves as a comprehensive documentation project that provides deep-dive insights into the architecture, internals, and usage of various AI-powered CLI tools. It documents five specific tools: Claude Agent SDK, Gemini CLI, Codex CLI, OpenCode, and Pi Coding Agent, offering detailed explanations of their internal workings, features, and integration patterns. The content is derived from direct source code analysis and aims to fill the gaps in official documentation. The repository is structured with dedicated directories for each tool, following a standardized numbering convention for topics (e.g., 01-overview, 02-technical-stack). It also includes specialized extraction sections for the Claude Agent SDK, breaking down its subsystems into individually documented 'complete' files. This approach demonstrates a reproducible pattern for knowledge extraction from complex software systems. While the repository excels in organizing and presenting technical information, it relies on external source code for its content and does not include the analysis scripts or raw data used to generate the documentation. This makes reproducing the exact analysis challenging, though the documented versions of each tool are specified. The documentation faces a high risk of becoming outdated due to the rapid evolution of the underlying AI CLI tools.
The repository is a simple Flask web application demonstrating interaction with the Google Gemini API for text and multimodal chat. It provides a UI for sending text messages and uploading images, maintaining a chat session via the Gemini API and streaming responses using Server-Sent Events. The architecture is monolithic with backend logic in app.py, served frontend static files, and a single HTML template. Key endpoints include '/' for the main page, '/upload' for file handling, '/chat' for message reception, and '/stream' for response streaming. While functional for demonstration, the application relies on global variables for state management (chat session, pending message, pending image), making it unsuitable for production multi-threaded environments without modification. The code is straightforward and serves as an educational starting point for Gemini API integration, but lacks reusable components due to tight coupling and simplicity-focused design. Dependencies are current, and the repository shows recent maintenance activity.
This repository is primarily a large collection of GPT prompt templates (markdown files) designed for use with AI chat platforms like FlowGPT or gptcall.net. Each prompt file defines a specific role or task for the AI, such as a resume editor, coding tutor, fitness planner, or creative writing assistant. The repository also includes an Android application (OpenClaw and Codex) referenced in the README, along with Node.js scripts (update.mjs, db.mjs) for managing the prompt data. The prompts are structured with placeholders for user input and often request specific output formats, enabling users to import them into chat interfaces to obtain specialized AI behavior without crafting prompts from scratch. While the prompt library is extensive, it contains significant duplication, minimal-effort entries, and some policy-risking content (e.g., jailbreaks, NSFW role-play), which affects overall quality and reuse potential.
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.