ChatDev 2.0 (DevAll) is a zero-code multi-agent orchestration platform for building and executing graph-based AI workflows. Users define directed acyclic or cyclic graphs in YAML, composing agent nodes (with LLM providers, memory, tools, thinking modes), human-in-the-loop nodes, Python executors, subgraphs, and control-flow edges with conditions and data transformations. The system supports dynamic parallel execution patterns (Map/Tree), multiple memory stores (simple, file-based FAISS, cloud Mem0), and extensible tooling via local Python functions or MCP servers. The architecture is a full-stack application: a FastAPI backend with REST and WebSocket endpoints for workflow execution, batch runs, artifact streaming, and session management; a Vue 3 frontend with a visual workflow editor (VueFlow), dynamic schema-driven forms, and real-time execution monitoring; a CLI entry point (`run.py`); and a Python SDK (`runtime/sdk.py`) for programmatic use. The codebase is well-structured with registry patterns for extensibility, declarative configuration dataclasses with auto-generated UI forms, and a modular runtime with pluggable node executors, edge conditions, and memory stores. While primarily an application, the project has strong research roots (OpenBMB lab, Tsinghua NLP) and includes academic references (ChatDev, Co-Learning, MacNet). It serves as both a production-grade tool for multi-agent automation and a research platform for experimenting with agent architectures, memory systems, and collaborative workflows. The repository includes 20+ example workflows demonstrating diverse use cases from software development and data visualization to 3D scene generation and deep research.
PyCaret 4.0 is a full-stack MLOps platform combining a low-code Python AutoML engine, a FastAPI control plane server, and a React web UI into a single deployable system. The engine provides OOP Experiment classes for classification, regression, clustering, anomaly detection, and time series, with native sklearn pipeline implementations and typed result dataclasses. The server adds multi-user workspace management, experiment tracking, model registry, deployment serving, drift monitoring, LLM-powered advisory copilots, scheduling, webhooks, and audit logging. The React frontend offers a rich SPA with real-time event streaming, interactive plots (Plotly), and data-driven forms generated from engine introspection. The architecture is well-structured with protocol-based abstractions for storage (local-fs/S3), data sources (CSV/Postgres), LLM providers (Anthropic/OpenAI/fake), and notebook backends. This is primarily an application (ML platform) but has strong data/research characteristics due to the engine's statistical analyses, dataset profiling, and time-series utilities. The codebase is under active development with a systematic migration from legacy functional APIs to the new OOP architecture, and many components are genuinely reusable.
YouDub WebUI is a full-stack video localization platform that enables users to import videos, transcribe speech via Whisper, translate via OpenAI-compatible APIs, clone voices with VoxCPM2, separate audio with Demucs, align subtitles with Qwen3 Forced Aligner, and export dubbed videos or subtitles. The architecture is plugin-based (Cordis framework) with a Node.js/TypeScript host orchestrating Python subprocesses for ML inference, a Next.js web frontend, and native desktop apps for macOS (Swift) and Windows (C#). The system features a task engine with queuing, cancellation, retry, and partial rerun; a worker protocol using NDJSON over stdin/stdout; and a comprehensive setup service that downloads and verifies model weights. While primarily an application, it includes research-grade model consumption and detailed validation records documenting real-media runs with SHA-256 hashes and human listening feedback. The codebase is actively maintained with recent commits, CI/CD pipelines, and extensive unit tests for contracts, protocols, and permissions.
This is a full-stack cultivation world simulator game (xianxia RPG) with a Python backend (FastAPI + asyncio) and a Vue 3 + TypeScript + PixiJS frontend, supported by an optional Electron desktop shell for Epic Games Store distribution. The simulation engine runs a month-by-month tick system orchestrating ~29 phases (lifecycle, actions, social, war, world events, etc.) producing emergent narratives driven by LLM calls (OpenAI/Anthropic compatible) for character decisions, story generation, world lore rewriting, and roleplay interactions. The codebase is heavily data-driven with static game configurations (sects, techniques, items, regions) loaded from CSV files and multi-language localization via gettext PO files. It exposes a public REST API (query/command) and WebSocket for real-time state updates, supports save/load with JSON snapshots and SQLite event storage, and includes comprehensive test coverage (pytest, vitest, Playwright) and CI/CD workflows. While the architecture shows strong engineering patterns (effect system, action registry, single-choice decision framework, phased simulation pipeline), it carries risks from tight coupling of global singleton registries, LLM dependency, and use of `eval` in effect conditions.
Onyx is a full-stack AI enterprise search and chat platform. The backend is a Python/FastAPI service with Celery workers, PostgreSQL, Redis, and a vector search engine (Vespa/OpenSearch). It ingests documents from 50+ external connectors (Google Drive, Slack, Confluence, Jira, SharePoint, etc.), runs a chunking/embedding/indexing pipeline, and serves RAG chat and search to multiple frontends: Next.js web app, React Native/Expo mobile app, Tauri desktop wrapper, Go CLI, an embeddable web widget, and a Terraform provider. It also includes an MCP server, deep research flows, sandboxed code-execution sessions (Craft), prompt caching, SSO/OAuth/SCIM multi-tenancy, rate limiting, and an admin analytics console. The repository has a hybrid character because it contains substantial data-engineering machinery (indexing pipelines, chunkers, embedding providers, evals) but the dominant identity is a production application rather than a research project.
Jupyverse is a modular Jupyter server implementation built on the FPS (FastAPI Plugins System) framework. It provides a customizable backend for Jupyter interfaces (JupyterLab, Notebook) through interchangeable plugins handling authentication, file contents, kernel management, terminals, real-time collaboration, and more. The system uses FastAPI for HTTP/WebSocket endpoints and anyio for async operations, with a core API defining interfaces that plugins implement. Entry points include a CLI command and composed plugin modules. Key data flows involve routing requests to appropriate plugins (e.g., contents API for file operations, kernel plugin for code execution) and leveraging WebSockets for real-time features like collaboration and terminal communication. External dependencies include FPS, Jupyter libraries, Yjs for CRDTs, and various auth providers.
Odysseus is a self-hosted, full-stack AI assistant platform built with FastAPI (Python) and vanilla JavaScript. It provides a unified workspace for chat with multiple LLM providers (OpenAI, Anthropic, Ollama, local models), deep research with multi-step web analysis, RAG-based memory and document indexing, email/calendar/contacts management via IMAP/CalDAV/CardDAV, an image editor with layers and AI tools, task scheduling, web search, and MCP (Model Context Protocol) server integration. The architecture follows a modular route-per-domain pattern with backward-compatibility shims, a shared SQLite database via SQLAlchemy, and ChromaDB for vector storage. The frontend is a single-page application with streaming markdown rendering, live thinking display, and extensive keyboard shortcuts. The system is designed for multi-user operation with owner-scoped data isolation, atomic file writes for state persistence, and comprehensive security measures including SSRF protection, prompt injection hardening, and secret encryption. It includes a hardware-fit recommendation engine (cookbook) for selecting optimal LLM inference backends (llama.cpp, vLLM, diffusers) based on local GPU capabilities. While primarily an application, it incorporates significant data engineering patterns: embedding lanes with fallback, search result ranking, memory consolidation with near-duplicate removal, and deep research synthesis pipelines. The codebase demonstrates strong engineering practices with extensive regression testing (over 400 test files), CI/CD pipelines, and security scanning. However, it shows signs of technical drift with duplicate code paths (e.g., search ranking in both `src/search` and `services/search`), heavy monkeypatching in tests, and some legacy migration complexity. The project is actively maintained with frequent commits and issue triage.
Onyx is a comprehensive enterprise AI platform that provides knowledge retrieval, chat, and document indexing across 50+ third-party sources. The codebase reveals a FastAPI backend with Celery workers, PostgreSQL with Alembic migrations, OpenSearch vector search, Redis caching, and a separate model server. The frontend is a Next.js application with a custom design system (opal), alongside React Native mobile app, Go CLI, Chrome extension, and an embeddable widget. The platform supports deep research, custom agents, MCP servers, sandboxed code execution (Craft), and enterprise features like SSO, SCIM, billing, and multi-tenancy. Architecture is well-structured with clean separation of concerns, but the large codebase shows some drift: platform duplication across web/mobile/CLI, extensive Alembic migration history, and lint debt. The connector framework and design system are high-quality reusable components.
Cognee is an open-source AI memory platform that enables agents and applications to build, store, and query persistent knowledge graphs from documents, code, and conversations. The system provides a Python SDK, a FastAPI REST API, a CLI, a Next.js frontend, and an MCP server for agent integration. Core operations include ingesting data (remember), extracting entities and relationships via LLMs or GLiNER (cognify), retrieving context (recall), and self-improvement loops (improve). The architecture is modular with adapter/registry patterns for graph databases (Ladybug, Neo4j, Turso), vector stores (LanceDB, PGVector), LLM providers (LiteLLM, OpenAI, Anthropic, Ollama), and integrations (Slack, GitHub, Google Drive). The frontend provides a dashboard for dataset management, knowledge graph visualization, and business analytics. The project also includes an evaluation framework for benchmarking retrieval strategies against standard datasets like HotpotQA and BEAM. While production-grade in many areas, some components are marked as demo-quality or have cloud-only stubs.
MemoryBear is a production-oriented, multi-tenant AI agent platform whose core differentiator is a cognitive-inspired persistent memory system for LLM applications. The code — not the README — shows a full SaaS stack: a FastAPI backend (~60 domain controllers), a React/TypeScript admin console, an identity/auth service, an API gateway, a dedicated RAG knowledge service, and a Rust seccomp sandbox for code execution. The memory subsystem is the heart: pipelines extract statements, triplets, entities, emotions, preferences, and implicit habits from conversations into a Neo4j knowledge graph (projected to Elasticsearch through a transactional outbox), with ACT-R-inspired forgetting/reinforcement scheduling, LLM reflection/dedup, BERT scene-boundary detection, and hybrid retrieval at query time. This is an application, not a data-research repo, although the memory-science algorithms (forgetting curves, emotion classification, value ranking) are shipped as product features rather than research artifacts.
This is a full-stack, self-hosted satellite ground station, not a data-research repository, though it contains substantial orbital-data ingestion, telemetry parsing, and signal-processing components. The application connects software-defined radios (RTL-SDR, Airspy, UHD, SoapySDR, SDRplay) to a real-time web UI for satellite tracking, hardware control, IQ/waterfall visualization, demodulation, decoding, recording, and observation scheduling. The backend is Python with FastAPI/Socket.IO, SQLAlchemy/Alembic, multiprocessing workers, and pub/sub broadcaster components; the frontend is React/Redux Toolkit/Material-UI. The user-facing system manages rotators and rigs via Hamlib, propagates TLE/OMM orbital elements, predicts passes, applies Doppler correction, schedules automated observations, and exposes file browsing, telemetry analysis, and audio transcription through external AI providers.
KonomiTV is a modern, full-stack online PVR/streaming server tailored for Japanese digital television (GR, BS, CS, BS4K). In production, it serves as a live TV player with hardware-accelerated transcoding (QSV, NVENC, VCE, FFmpeg), a complete EPG and recording scheduler, and deep social media integration (Twitter/X, Bluesky, Niconico Jikkyo). The system acts as a modern web frontend for the traditional EDCB and Mirakurun TV middleware. The backend is a Python FastAPI application executing complex pipelines for MPEG-TS parsing, live encoding, and metadata analysis. The frontend is a Vue 3/TypeScript Progressive Web App with offline storage via Service Workers. The codebase exhibits high craftsmanship in its low-level protocol interactions: it contains a complete reverse-engineered binary protocol parser for EDCB, an undocumented Twitter GraphQL scraper, and zero-dependency keyframe seekers for MPEG-TS and MP4 containers. While primarily an application, it incorporates significant reverse-engineering and data processing research, including automatic CM detection, computer vision-based thumbnail scoring, and BML data broadcasting support. The architecture is well-structured but heavily coupled to the Japanese TV ecosystem and multiple fragile third-party dependencies (custom binary forks, hardware-specific drivers, browser automation for social feeds). These dependencies introduce medium technical drift, but the project is actively maintained with thorough CI/CD and regular third-party updates.
Sunone Aimbot is an AI-powered aimbot for first-person shooter games that uses YOLO models to detect players and heads in real-time screen captures. The system captures frames via MSS, BetterCam, or OBS, processes them with Ultralytics YOLO, identifies targets (prioritizing heads unless disabled), calculates mouse movement to aim at targets, and optionally shoots automatically. It features a modular architecture with separate threads for capture, visualization, overlay, shooting, and hotkey monitoring. A helper API and React-based UI provide configuration management, model training/exporting, and testing capabilities. The aimbot supports multiple input methods including standard mouse, GHUB, Razer, and Arduino devices.
This repository provides a production-ready, full-stack Retrieval-Augmented Generation (RAG) chat application built with Python FastAPI and React TypeScript. It demonstrates how to use Azure OpenAI (or OpenAI.com, or Ollama) to answer questions about data stored in Azure Database for PostgreSQL with the pgvector extension. The system supports both a simple RAG flow (embedding + direct search) and an advanced flow that uses OpenAI function calling to rewrite queries and apply column filters (brand, price). It features hybrid search combining full-text search and vector similarity via Reciprocal Rank Fusion. The backend is a monolith serving API endpoints and a React frontend, designed for deployment to Azure Container Apps using the Azure Developer CLI. The codebase includes comprehensive unit tests, end-to-end tests with Playwright, evaluation scripts, load testing with locust, and safety evaluation using Azure AI Red Teaming. The architecture is cleanly separated into reusable modules, making it a solid reference architecture for building RAG applications on Azure.
This repository is a reverse-proxy that translates ChatGPT's proprietary web API into OpenAI-compatible REST endpoints, enabling standard OpenAI SDK clients to generate images, edit images, have chat conversations, and search using ChatGPT's backend. It manages a pool of ChatGPT accounts, handles token refresh, proxy rotation, Cloudflare clearance (FlareSolverr, WARP), and provides a Next.js web dashboard for account management, image generation, settings, and backup. The backend is built with FastAPI and uses curl_cffi for HTTP impersonation, while the frontend is a modern React application with shadcn/ui components. The architecture is modular: protocol adapters in `services/protocol/` convert between OpenAI/Anthropic formats and ChatGPT's internal API, storage backends (JSON, SQLite, PostgreSQL, Git) abstract persistence, and services handle account lifecycle, image processing, and proxy configuration. The system is designed for self-hosted deployment via Docker Compose and supports advanced features like content filtering, chat completion caching, and editable file generation (PPT/PSD). Despite its strong engineering and active maintenance, the codebase is heavily dependent on reverse-engineering of ChatGPT's private API, making it fragile to upstream changes. The large single-file `OpenAIBackendAPI` class and limited test coverage are areas of concern, but the separation of concerns in storage, protocol, and service layers offers good reusability.
This repository is a Python library and framework for building and deploying multi-agent AI systems. It provides a structured way to define agents with specific roles, instructions, tools, and communication flows, orchestrated by an Agency. The framework extends the OpenAI Agents SDK with production-grade features: FastAPI web serving with streaming SSE endpoints, realtime voice support via WebSocket and Twilio, MCP (Model Context Protocol) server integration with OAuth authentication, persistent conversation state with load/save callbacks, system reminders for prompt engineering, input/output guardrails, and observability hooks for Langfuse/AgentOps. It also includes CLI tools for scaffolding agents and migrating from OpenAI Assistant configurations. Architecturally, the system is a library that can be used programmatically (create Agent and Agency instances, call get_response) or deployed as a FastAPI application via run_fastapi(). The core data flow involves user messages flowing through an agent's execution pipeline, which may invoke tools (built-in, MCP, OpenAPI, LangChain), hand off to other agents via SendMessage/Handoff, and stream responses back. The ThreadManager provides flat message storage with agent/caller metadata, supporting thread isolation and persistence. The tool system uses Pydantic models for schema generation and supports concurrency control. Key entry points include the Agent and Agency classes for programmatic use, run_fastapi() for web deployment, run_realtime() for voice, run_mcp() for MCP server, and CLI commands (create-agent-template, migrate-agent, import-tool). External dependencies include the OpenAI Agents SDK (pinned), FastAPI, Pydantic, and optional integrations like LiteLLM, LangChain, and MCP SDK. The codebase demonstrates strong engineering practices with extensive test coverage (unit, integration, live API), modular design, and reusable patterns such as the BaseTool class, ToolFactory adapter, ThreadManager message store, and OAuth flow for MCP. However, it has tight coupling to the OpenAI Agents SDK internals, requiring careful maintenance as the SDK evolves.
Yeti is a threat intelligence platform that ingests, enriches, correlates, and stores cyber threat observables, entities, indicators (YARA, Sigma, Suricata, regex, forensic artifacts), and DFIQ investigative questions. It provides a FastAPI-based REST API for CRUD operations, graph traversal, semantic search (via ChromaDB), and RBAC. The system uses ArangoDB as its primary graph/document database, Redis for message brokering, and Celery for background task scheduling. It includes a plugin architecture for feeds (30+ public sources like MITRE ATT&CK, CISA KEV, MISP, AbuseIPDB) and analytics (Shodan, Censys, VirusTotal, etc.). The codebase is well-structured with clean abstractions (ArangoYetiConnector, event system, polymorphic schemas, migration framework) but contains deprecated plugins and some configuration drift. It is primarily an application, not a data research project.
AI Vocabulary Builder is a full-stack web application (FastAPI backend, Vue.js frontend) that uses LLM APIs (OpenAI, Gemini, Anthropic, DeepSeek) to help users build and learn English vocabulary. The backend exposes REST APIs for translating text, extracting rare words, managing a vocabulary store (TinyDB), generating stories and quizzes from learned words, and exporting to Anki/CSV. The frontend provides an intuitive single-page interface with build, learn (words list, quiz, story) and settings views. The architecture follows a modular monolith with clear separation of concerns: `builder` for vocabulary extraction, `learn` for quiz/story features, `system` for settings and model configuration, and `infras` for persistence and AI model abstraction. The codebase is well-structured with comprehensive unit tests, CI/CD via GitHub Actions, and rigorous linting/formatting (ruff, mypy).
MoneyPrinterTurbo is a production short-video generation platform. Given a topic or script, it orchestrates LLM-based script/keyword generation, multi-provider TTS (Edge, Azure, Gemini, ElevenLabs, etc.), video material sourcing (Pexels, Pixabay, Coverr, several AI video generators), subtitle generation (Whisper or TTS timestamps), background music, and final video composition via moviepy/FFmpeg. It exposes three consistent interfaces: a FastAPI REST API, a Streamlit WebUI, and a CLI. All three share the same underlying task pipeline in `app/services/task.py`, which manages state, progress, and cross-posting to YouTube/TikTok/Instagram. The architecture is a service-oriented monolith: the core pipeline is a linear sequence of stages (script → terms → audio → subtitles → materials → video → optional BGM/cross-post). External integrations are abstracted behind provider-specific modules (e.g., `voice.py`, `material.py`, `bgm.py`). A Redis-backed or in-memory state manager tracks task progress. The configuration is runtime-editable and stored in a TOML file. The WebUI is a large Streamlit single-page application with dozens of provider-specific controls, billing confirmations, and i18n support for 12+ languages. The codebase demonstrates strong engineering practices: extensive test coverage (200+ test files), structured error handling with per-provider error classes, atomic file writes, path traversal protection, and security-conscious API key handling. However, it also shows signs of rapid growth: the WebUI is a monolithic 1300+ line script, provider integration logic is occasionally duplicated, and the dependency list is large (many third-party APIs). The repository is actively maintained with recent commits and good issue triage. It is not a research project; there are no datasets, model training, or analytical queries.
ChatTTS is a generative speech model application designed specifically for dialogue scenarios, functioning as a Text-to-Speech (TTS) library with integrated serving infrastructure. The core logic resides in the ChatTTS package, where `ChatTTS/core.py` defines the main inference interface. The architecture combines a GPT-based language model (`ChatTTS/model/gpt.py`) for token generation, a DVAE (`ChatTTS/model/dvae.py`) for audio compression, and Vocos as a vocoder. The system supports multiple speakers, prosodic control (laughter, pauses), and text normalization for Chinese and English. Deployment is handled through multiple entry points: a FastAPI-based API server (`examples/api/main.py`), a Gradio WebUI (`examples/web/webui.py`), and CLI tools (`examples/cmd/run.py`). A significant engineering highlight is the integration of vLLM (`ChatTTS/model/velocity/`) to optimize inference throughput for the GPT component. The repository includes robust asset management (`ChatTTS/utils/dl.py`) for model weights with SHA256 verification and ONNX export capabilities (`examples/onnx/exporter.py`) for cross-platform deployment. While the underlying model is research-grade (trained on 100k+ hours of audio), the repository structure prioritizes application delivery over experimental research. It provides a stable library interface with clear separation between model logic, audio processing (`tools/audio/`), and serving layers. The codebase demonstrates high craftsmanship in handling stochastic generation reproducibility (`tools/seeder/ctx.py`) and speaker embedding management (`ChatTTS/model/speaker.py`), making it a production-ready TTS solution rather than a raw research notebook collection.