Reactive Resume is a full-stack, open-source resume builder and job application tracker. It provides a rich web interface for creating, editing, and managing resumes with real-time preview, multi-format export (PDF, DOCX, Markdown, JSON), and ATS compatibility analysis. The system includes an AI-powered assistant for resume tailoring and cover letter drafting, an MCP server for LLM integration, and a semantic CSS stylesheet system for fine-grained PDF styling. The architecture is a monorepo with a React frontend (TanStack Router, Zustand, Lingui i18n), a Node.js API layer (oRPC, Drizzle ORM, PostgreSQL), and dedicated packages for PDF generation, DOCX export, authentication, and UI components. Key entry points include the resume builder interface, public resume sharing pages, an AI agent chat, and a job application board with stage tracking and CSV import/export. External dependencies include PostgreSQL, Redis, AI provider APIs (OpenAI, Anthropic, Gemini), and cloud storage (Vercel Blob or S3). The codebase is well-structured with extensive unit and integration tests, a reusable UI component library, and a modular package architecture that supports self-hosting via Docker or Vercel.
Reasonix is a local AI coding agent engine written in Go, providing a terminal UI, desktop application (Electron + React), and HTTP server for interacting with large language models (OpenAI, Anthropic, DeepSeek, etc.) to automate software engineering tasks. The kernel manages sessions, context windows, planning, sub-agent delegation, tool execution (file operations, shell, browser, MCP servers), and a sophisticated safety sandbox. It persists conversation history with checkpoints for undo/rewind, tracks token usage, and maintains an evidence ledger for auditing tool effects. The architecture is a monolithic Go binary with multiple frontends: a CLI/TUI, a desktop host that communicates via SSE/JSON, and a REST API server. A plugin system using the Model Context Protocol (MCP) allows extension. Separate Cloudflare Workers handle account management, forum, and crash reporting. The codebase is well-structured with a clean layered architecture (base utilities, domain contracts, state persistence, runtime agent, assembly wiring, frontends), extensive test coverage, and internal linters enforcing quality. It is actively maintained with frequent commits and professional CI/CD pipelines.
The Front-End Checklist is a comprehensive, open-source platform for front-end quality assurance, targeting both human developers and AI agents. It delivers a curated corpus of 386+ best-practice rules across 11 categories (HTML, CSS, JavaScript, Performance, Accessibility, SEO, Security, Images, Testing, Privacy, i18n) via a Next.js web application, a Model Context Protocol (MCP) server, and a standalone CLI. The architecture is a pnpm monorepo with shared packages for authentication (Better Auth + Prisma), design system (Radix UI), analytics (OpenPanel), state management (Zustand), search (FlexSearch), storage (IndexedDB), and validation. The MCP server exposes 11 tools (audit_url, review_code, search_rules, etc.) for AI-assisted code review and URL auditing, while the CLI provides offline audit capabilities. The web app offers rule browsing, user checklists with progress tracking, guides, and public profiles. The system is production-deployed on Vercel with PostgreSQL, Sentry error tracking, and Upstash rate limiting.
CareerOps is a local-first, AI-assisted job search automation platform. It scans 100+ ATS job boards and aggregators (Greenhouse, Lever, Ashby, Workday, iCIMS, PeopleSoft, 55+ providers) through a standardized provider abstraction, evaluates each posting against the user's CV by delegating to AI coding CLIs (Claude Code, Codex, Gemini, OpenCode, etc.), emits structured A–H evaluation reports with 1–5 fit scores, generates ATS-optimized CV PDFs and cover letters, and tracks the full application lifecycle in a Markdown/TSV data store. It ships three surfaces: a Node.js CLI core (~150 .mjs modules), a Next.js 16 web dashboard, and a Go Bubble Tea TUI. All data remains on the user's machine; nothing is ever auto-submitted—a human presses send. The evaluation, scoring, and pattern-analysis features (funnel velocity, repost detection, calibration against outcomes) are product features, not research artifacts, so the repo is classified as an application despite these analytical components. Architecturally, this is a monorepo spanning three runtimes that share a flat-file data layer coordinated by cross-process file locks (SHA256-derived lock directories compatible between Go and Node). Its standout engineering includes a provider registry pattern for ATS integrations, a plugin engine with mandatory human-in-the-loop enforcement, capability-fenced CLI spawning for AI agents (read-only/web-search-only modes with per-CLI fencing probes), atomic write-with-backup for every user-layer file, and a 400+ file test suite including byte-level parity tests that keep web-side algorithm mirrors aligned with core logic, SSRF-hardening tests across all providers, and cross-platform contention tests. The repo also demonstrates unusually mature governance: plugin registration with pinned SHAs, direction gates in CI, localization drift checks for 16 languages, and a self-updater with rollback. Weaknesses: the Go/Node split duplicates tracker parsing logic (mitigated by shared header-alias tables but still a maintenance burden), parsing is regex-heavy over markdown tables with many special-case bugs, and rapid feature expansion has produced visible bloat—dozens of AI-provider-specific eval scripts, many localized mode trees, and extensive one-off migration scripts. The external ecosystem (ATS site markup, AI CLI permission models) shifts constantly, requiring the active dead-board pruning and fencing probes visible in the codebase. Overall this is a well-crafted, heavily tested local-first application with several genuinely reusable security and concurrency patterns, held back from exceptional by its dual-runtime duplication and feature sprawl.
Invisible Dots is a self-hosted, open-source platform for deploying and managing persistent AI agents ('Dots'). Each Dot operates within its own dedicated QEMU virtual machine, providing a secure, isolated environment with a full Linux desktop, browser, and file system. The platform is designed for undetectability and long-running autonomy, serving as an open-source alternative to proprietary agent services. The system is a polyglot monorepo with a strict separation between the host control plane (TypeScript) and the guest agent (Go) and engine (Python). The host manages VM lifecycle, scheduling, a web UI, CLI, and messaging channels (Telegram/WhatsApp). The guest runs a Go daemon for low-level system access and a Python engine (forked from nanobot) that orchestrates LLM calls, tool execution, and permissions. Key features include a granular permission system with approval workflows, a cron-like task/automation system, cost capping per task, and a comprehensive benchmark suite for evaluating agent capabilities. The codebase demonstrates exceptional engineering craftsmanship with clean abstractions (Database, Channels, Computer), robust testing strategies (contract tests, fakes, e2e), and reusable utility libraries (ISO writer, SSE parser, atomic file operations). While primarily an application, the project includes a significant research-oriented benchmark suite (tests/bench) and the engine itself is a research fork (nanobot), giving it a hybrid character. The core value, however, is as a production-grade application platform.
Decepticon is an autonomous AI-powered red team agent platform for offensive security engagements. It orchestrates multiple LLM-based agents (recon, exploit, AD, cloud, etc.) via LangGraph to execute complex, realistic attack chains against targets, with strict Rules of Engagement (RoE) enforcement, sandboxed execution, and human-in-the-loop approval. The system provides a web dashboard (Next.js), CLI (Ink), and MCP server for control and monitoring, and includes a plugin system for extensibility. It also features comprehensive benchmark frameworks for evaluating agent performance on security challenges. The architecture is a multi-service Docker Compose deployment with Python backend services, a Go launcher, Neo4j knowledge graph, and high isolation between management and sandbox networks. This is primarily a software application (automated red team orchestrator) with strong data/research elements such as knowledge graph persistence, benchmarking pipelines, and telemetry collection. The codebase demonstrates high craftsmanship with protocol-based plugin contracts, a well-structured middleware stack, and thorough testing, though the polyglot nature and dual client maintenance add complexity.
Nanobot is a self-hosted, open-source personal AI assistant framework that operates as a full-stack application. The Python backend provides an agent loop with tool execution, session management, multi-provider LLM orchestration (OpenAI, Anthropic, etc.), and a plugin system for 18+ messaging channels (Telegram, Discord, Slack, WeChat, Feishu, etc.). It exposes a WebSocket-based gateway, an OpenAI-compatible API, and a CLI. Two frontends exist: a rich WebUI built with React/TypeScript/Vite/Tailwind and a terminal TUI built with Bun/OpenTUI. The architecture is event-driven via a message bus, with decoupled channel adapters, provider abstraction, and a config system supporting hot-reload. It includes security features like workspace sandboxing, credential redaction, and SSRF protection. The codebase is extensively tested (hundreds of unit/integration tests) and demonstrates strong engineering practices with clean abstractions, though its large dependency surface and multiple frontends introduce some maintenance surface area.
Qwen Code (formerly Gemini CLI) is an open-source, multi-platform AI coding assistant designed to operate in the terminal, web shell, desktop (Tauri), VS Code, JetBrains, and chat channels (DingTalk, WeChat, Slack, etc.). The architecture is a monorepo with ~30+ packages centered around a core library (`packages/core`) that provides agent runtime, tool orchestration, memory, MCP support, and telemetry. The primary entry points are the CLI (`packages/cli` with an Ink-based TUI), the web shell (`packages/web-shell`), and a daemon server (`packages/cli/src/serve/`) that exposes REST/SSE endpoints for session management, file editing, and sandboxed shell execution. The system supports multiple LLM providers (OpenAI, Anthropic, Gemini, DeepSeek, etc.) and features sub-agents, goal-oriented workflows, approval modes, browser automation (CUA driver in Rust), and a Java managed-agent server for enterprise deployments. Data flows are user-to-agent: user input enters via a client (CLI, web, IDE), is processed by the core agent loop, which invokes tools (shell, file system, LSP, MCP servers) and streams responses back. External dependencies include Node.js v22+, pnpm, and platform-specific native binaries (Rust CUA driver, Electron desktop). The codebase is actively maintained with daily commits, extensive integration tests, and CI/CD pipelines. While it is a software application, it includes telemetry modules and a few Python scripts for benchmark analysis, but no research-grade data pipelines or ML training code.
Engram is a persistent memory system for AI coding agents, written in Go. It provides a local-first knowledge store using SQLite with FTS5, exposed via CLI, HTTP API, MCP server, and terminal UI. Agents can save observations (notes), search memories, manage sessions, and consolidate related knowledge. The system supports multiple AI agents (Claude Code, Codex, Pi, OpenCode) through plugin hooks and MCP tools. Optional cloud sync enables multi-device persistence via a self-hosted Postgres backend with authentication, project controls, and a dashboard. The codebase demonstrates strong engineering practices with extensive test coverage, platform-specific handling, and reusable patterns like generation fencing and migration locking.
Agent Reach is a Python CLI tool that serves as a capability layer for AI agents, giving them one-click access to ~15 internet platforms (Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu, LinkedIn, etc.) without requiring manual setup. It does not wrap these platforms itself; instead, it selects, installs, health-checks, and routes to the most reliable upstream CLI tools (e.g., twitter-cli, yt-dlp, gh CLI, OpenCLI, mcporter) for each platform. The architecture is built around a multi-backend channel pattern: each platform has an ordered list of backends (primary + fallbacks), and the `doctor` command probes each candidate in order to determine the active backend. This design handles upstream tool instability gracefully by allowing fallback routing without code changes. The codebase demonstrates strong engineering practices: a clean Channel ABC with `check()` and `can_handle()` contracts, a robust probe system that distinguishes missing/broken/timeout/error by actual execution, security-hardened file operations (atomic private writes, symlink rejection, bounded reads), and SSRF protection in URL normalization. The CLI provides commands for installation (safe-by-default, read-only mode), diagnostics, configuration, and skill registration for agent environments (Claude Code, OpenClaw, Cursor, OpenCode). An optional MCP server exposes read-only status. Agent Reach is purely an application — there are no notebooks, data pipelines, or ML components. Its value lies in reducing the friction of giving agents internet access, with a focus on zero-config defaults for public platforms and cookie-based auth for login-required ones. The project is actively maintained, with documented responses to upstream API changes (e.g., Bilibili blocking yt-dlp, Twitter API pay-per-use).
Codewhale is an open-source, terminal-native AI coding agent that operates as a TUI (ratatui), CLI, headless runtime, MCP server, and a web frontend. It manages full development workflows: reading repositories, editing files, running commands, reviewing changes, and orchestrating multi-agent fleets. The codebase is a Rust monorepo with ~52 crates, a Next.js website with 18+ locales, a VS Code extension, packaging for npm/Homebrew/Arch/Windows, and companion pet apps. The architecture is event-driven with a pluggable tool system, model-agnostic provider routing, session-based journaling, and a contract-based command framework. It supports dozens of LLM providers (DeepSeek, OpenAI, Anthropic, Ollama, etc.) and features sandboxed execution, telemetry with a strict no-IP privacy contract, and a plugin marketplace. The project is heavily tested with unit, integration, PTY/Cucumber, and hermetic bash tests, and enforces budgets for dead code and blocking calls.
Mediary Scout is a self-hosted media acquisition system that automates the discovery, transfer, and organization of media files from various cloud storage providers (such as 115, Quark, Tianyi, etc.) into the user's own storage. It features an agent-driven workflow powered by LLMs to decide acquisition steps, a web interface (Next.js) and desktop client (Electron) for management, and background workers for processing tasks. The system includes remote access via Cloudflare Tunnels (through the scout-connect service) with subscription management (Alipay payments), and supports both single-user and multi-user modes with a demo option for demonstration.
mcp-logseq is a Model Context Protocol (MCP) server that bridges AI agents (like Claude) to Logseq knowledge bases. It exposes Logseq's local HTTP API through 15+ tools for reading, creating, updating, and deleting pages and blocks, along with search, DSL queries, and optional semantic vector search via LanceDB. The server supports both stdio and HTTP/SSE transports with security features including namespace/tag-based access control, read-only mode, TLS, and bearer token authentication. The vector database is managed by a separate sync process (logseq-sync) to enforce a single-writer pattern. The codebase is well-architected with clean separation of concerns: a declarative access control system, a pure namespace matching utility, a stateful markdown parser, and an embedder abstraction with Ollama/OpenAI adapters. Configuration is lazy-cached from environment variables and a JSON config file, with no import-time side effects. The test suite is comprehensive with over 50 unit tests and integration tests for HTTP serving. While the project is still in beta, it demonstrates strong engineering practices and provides several reusable components for other MCP server implementations or Logseq integration tools.
Flowcraft is a workflow orchestration framework for building, executing, and monitoring durable workflows. It provides a type-safe, composable API for defining workflows as directed graphs of nodes and edges, supporting both programmatic (fluent) and declarative (JSON) definitions. The framework enables progressive scaling from in-memory execution to distributed systems via adapters for message queues and cloud services, with built-in support for patterns like retries, timeouts, human-in-the-loop, batch processing, and subflows. Key architectural pieces include a dependency-free core runtime, a sophisticated context tracking system for efficient state persistence, a plugin-based adapter architecture for distributed execution, and LLM tooling for workflow introspection and control via natural language.
This repository is a production-grade, AI-powered stock analysis platform for CN, HK, US, JP, KR, and TW markets. In production it runs a scheduled analysis pipeline that fetches market data from multiple providers (akshare, yfinance, tushare, efinance, futu, etc.) with priority-based fallback, feeds the data to LLM backends via LiteLLM, generates structured decision reports, and pushes them through 15+ notification channels (WeChat, Feishu, DingTalk, Telegram, email, Discord, Slack, etc.). It also exposes a FastAPI REST API, a React/TypeScript web dashboard, an Electron desktop client, and bot integrations for Feishu/DingTalk/Discord. The system includes agent-based chat with tool use, screening, backtesting, alerts, portfolio management, decision-signal tracking, and market review capabilities.
gws is a production-grade Rust CLI for driving Google Workspace APIs (Gmail, Drive, Calendar, Sheets, Docs, Chat, Tasks, Classroom, Admin, and more). Its defining architectural bet is dynamic command generation: instead of shipping generated API client crates, it fetches Google's Discovery Service JSON at runtime, builds a clap command tree from the schema, and executes generic HTTP calls against resolved endpoints. A two-phase argument parse extracts the service name first, then re-parses with the dynamically constructed command set, keeping the entire Google API surface reachable without codegen. The repo is a Cargo workspace split into a reusable library crate (google-workspace: discovery models, validation, HTTP client) and the CLI binary crate, and is distributed via crates.io, npm (binary downloader), GitHub Releases, and Nix. Beyond raw API calls, a helper-command system (`+send`, `+upload`, `+agenda`, `+triage`) is implemented through a `Helper` trait that injects subcommands for multi-step workflows — MIME construction for Gmail, streaming multipart uploads for Drive, calendar agenda assembly, and cross-service orchestrations. Authentication supports interactive OAuth2 login, service accounts, pre-obtained tokens, and Application Default Credentials, with credentials encrypted at rest (AES-256-GCM) in an OS keyring or file fallback. A ratatui-based interactive setup wizard bootstraps a GCP project, enables APIs, and configures OAuth consent via gcloud. Output is structured (JSON/table/YAML/CSV/NDJSON) with stable, documented exit codes, making it suitable for both shell scripting and LLM tool calling. The repository also functions as an AI-agent integration layer: it ships 100+ SKILL.md files (per-service references, multi-step recipes, role-based personas) plus TOML registries defining personas and recipes, with a generator that produces skill documentation from CLI metadata. An experimental Model Armor integration sanitizes prompts and responses for prompt-injection attacks. Engineering quality is high throughout: extensive unit tests (several hundred cases, including security-focused edge cases), CI covering 7 build targets with real-credential API smoke tests, cargo-deny dependency auditing, changeset-based automated releases, and a Nix flake for reproducible builds. Notable risks: the entire command surface depends on Google's Discovery Documents staying available and compatible; the Gmail helper module is ~3000 lines and approaching a maintainability ceiling; two divergent OAuth implementations (yup-oauth2 fast path vs proxy-aware reqwest fallback) add maintenance burden; 15+ environment variables increase configuration complexity; and hardcoded API lists in setup tooling must be manually updated as Google adds services. These are real but moderate concerns in an otherwise well-architected, actively maintained codebase.
Palmier Pro is a professional macOS video editing application (NLE) built with SwiftUI, AppKit, and AVFoundation. It provides a full timeline editor with multi-track support, keyframe animation, compositing via Core Image and custom Metal kernels, and export to H.264/H.265/ProRes/XML/FCPXML. The application is distinguished by deep AI integration: an in-app agent and MCP server allow external AI assistants (Claude, Cursor, Codex) to edit timelines, apply effects, generate media, and manage projects via structured tools. On-device ML models provide beat detection (Beat This) and semantic visual search (SigLIP2), while cloud backends (Convex, Clerk) handle AI generation, transcription, and account/credit management. The codebase is well-structured with extensive test coverage, reusable utilities (DiskCache, AsyncSemaphore, EffectRegistry), and a clean separation of concerns in the compositing and audio analysis pipelines. It is a commercial product with localization in 20+ languages, Sparkle auto-updates, and Sentry telemetry.
VidBee is a multi-platform media downloader and transcript workspace. The primary product is an Electron desktop app that downloads video/audio from 1000+ sites via yt-dlp, runs local speech-to-text transcription (sherpa-onnx Whisper/SenseVoice/Qwen3/Parakeet families) with speaker diarization in an isolated worker process, and provides an AI agent chat, summarization, translation, and FAQ layer over the resulting transcripts. It also ships a self-hosted Fastify API with a TanStack Start web client, a CLI wrapper around yt-dlp that can run fully in-process or connect to the desktop/API, and a browser extension (WXT) that hands video URLs to the desktop app via a token-authenticated loopback HTTP bridge. An RSS subscription engine with SQLite CAS leader election supports feed auto-download. Architecturally this is a pnpm monorepo built around host-neutral packages: packages/task-queue (FSM-driven job queue with priority scheduler, retry backoff, watchdog, and SQLite/memory persistence adapters), packages/transcription (ASR pipeline, caption parsing, speaker clustering, chunk manifests), packages/downloader-core (yt-dlp args, format selection, cookie handling, oRPC contracts), packages/subscriptions-core (feed parsing, scheduler, leader election), plus packages/ui, packages/i18n, packages/db, and packages/logger. The desktop, API, CLI, and web hosts share these packages, and oRPC contract schemas are explicitly kept byte-equal across hosts. The desktop renderer uses React 19, TanStack Router, Jotai, and Tailwind 4; the main process uses an IPC-decorator pattern with roughly fifteen typed services. Engineering quality is consistently above average: shared contracts with zod validation, swappable persistence adapters, a pure-function task FSM, security-conscious extension token auth, and an SSRF-guarded remote image proxy. The main weaknesses are duplication and sync fragility: near-identical download UI components exist in both desktop and web apps, several overlapping error classifiers must be kept manually in sync, the API hardcodes APP_VERSION separately from package versions, and legacy migration/back-compat paths (task-queue projection to legacy DownloadItem shapes, migrate-history scripts) accumulate complexity. This is an application repository, not data research: the ASR and speaker-clustering code is product engineering rather than a research artifact, though the transcription package is a genuinely reusable pipeline.
Ralph for Claude Code is a CLI automation framework written entirely in Bash (with one Python helper for E2B sandbox transport) that orchestrates repeated Claude Code CLI invocations in an autonomous loop. The core system parses output from Claude to detect completion, test saturation, permission denials, and stuck loops, using a dual-condition exit strategy. It includes a circuit breaker (CLOSED/HALF_OPEN/OPEN) for stagnation protection, dual rate limiting (calls and tokens per hour), sandbox execution via Docker or E2B cloud, session continuity with expiry, and backup/rollback via git branches. The system manages GitHub issue lifecycles (progress comments, auto-close, PR creation, follow-up issues) and provides a persistent queue for batch processing with dependency resolution and priority ordering. All state is maintained as JSON files in a .ralph directory with atomic writes. The repository also includes extensive test infrastructure (276 BATS tests) with mock binaries for gh, claude, docker, and e2b-python, a full E2E subprocess-level harness, and 24 unit test files plus integration and E2E tests. The project is not a hybrid data/research repository; it is purely an application for automating AI-assisted software development.
Notte is a full-stack web AI agent framework and browser automation SDK. The implementation is a multi-package Python monorepo: notte-core provides shared domain models, actions, error hierarchies, telemetry, and configuration; notte-browser implements Playwright/Patchright browser control, DOM snapshotting, scraping pipelines, and form-filling heuristics; notte-agent contains the LLM-driven agent loop, deterministic fallback, and workflow execution; notte-llm wraps LiteLLM with structured completions, retries, and a file-based prompt library; notte-sdk is the client for the hosted Notte cloud API with remote sessions, agents, vaults, personas, and serverless functions; notte-integrations adds notifiers and third-party CDP session providers. Primary entry points are `NotteClient` for cloud usage, `NotteSession` for local browser automation, and `Agent`/`AgentFallback` for autonomous and hybrid scripted-agent workflows.