GitHub Projects for AI Engineers

190 repositories that keep resurfacing in the AI engineering conversation, organized by the part of the stack they are changing.

RADAR / 2026.09 VERIFIED
Projects
190
Combined stars
8.1M
Combined forks
975.6K
Theme lanes
5

GitHub metrics checked 2026-09-13. Ranked by stars, then forks. Growth is a dated GitHub Trending observation; missing values are unobserved.

01 / SIGNAL

Popularity skyline

The ten most-starred projects in this edition. Height represents GitHub stars.

02 / ECOSYSTEM

One stack, two ways to read it

Browse by capability when choosing components, or by production depth when diagnosing what sits underneath a working AI feature. Every item opens an official repository, product page, or documentation route.

Tools
98
Capability lanes
13
GitHub links
65
Official links
33

This is a selection map, not a recommendation to use every layer or tool.

03 / DIRECTORY

Explore the stack

Use a theme lane, search by project or idea, and change the ranking signal.

190 projects

01

Tools & agent workbenches

Runtimes, coding agents, orchestration frameworks, and operator surfaces where AI work actually happens.

75
#01Personal agent runtime

openclaw

openclaw

Its rapid adoption shows demand for a persistent, cross-platform agent runtime that connects models, tools, channels, and personal workflows.

389.5K 81.9K2 export hits
#02Agent skills methodology

superpowers

obra

Reusable skills are becoming an engineering methodology: agents load bounded procedures instead of improvising every workflow from a prompt.

285.9K 25.6K
#03Engineering skills

skills

mattpocock

Production-tested engineering procedures packaged as skills make expert workflows portable across agent clients and teams.

260.7K 22K
#04Cross-client agent harness

ECC

affaan-m

Skills, memory, hooks, and security checks package an operating method that can travel across coding-agent clients and repositories.

257.3K 38.5K
#05Learning agent runtime

hermes-agent

NousResearch

Hermes makes learning from completed work part of the runtime, turning successful procedures into durable capabilities.

245K 50.9K8 export hits
#07Open coding agent

opencode

anomalyco

An open coding-agent client provides another inspectable execution surface for repository work and integration with the surrounding model stack.

207K 27.1K
02

Context engineering & memory

The supply chain that turns documents, code, web pages, tools, and knowledge graphs into usable agent context.

46
#08Document ingestion

markitdown

microsoft

File-to-Markdown conversion is becoming the dependable ingestion layer agents need before retrieval, synthesis, and audit trails.

183.4K 13.5K
#10Web extraction

firecrawl

firecrawl

Web extraction is moving from scraping glue to an agent-ready primitive for monitoring, RAG, and newsroom intake.

179.7K 9.8K
#23Tool ecosystem

awesome-mcp-servers

punkpeye

MCP server catalogs show how quickly agent capabilities are becoming installable infrastructure.

94.9K 16.1K
#25Tool protocol

servers

modelcontextprotocol

The reference server collection makes tools and context sources portable across agent clients.

90.3K 11.6K
#28Tool-output compression

rtk

rtk-ai

Filtering command output before it enters model context makes terminal verbosity a controllable cost in coding-agent loops.

80.1K 5.1K
#29Web and social context

Agent-Reach

Panniantong

One CLI for difficult web and social sources makes external evidence retrieval a reusable agent capability rather than per-source scraping glue.

80K 6.9K2 export hits
03

LLM-UI & generated interfaces

Interfaces assembled around model output, task state, validation, and human correction.

19
#30Visual reference to interface

screenshot-to-code

abi

Turning screenshots and recordings into editable frontend code makes visual references a direct input to interface-building workflows.

78.7K 9.6K
#36Design language for agents

impeccable

pbakaus

An explicit design language helps coding agents reason about visual tradeoffs instead of reproducing generic component patterns.

67.7K 4.1K
#42Verifiable architecture diagrams

archify

tt-a1i

Typed diagram data compiled into HTML and SVG makes architecture explanations inspectable, diffable, and reusable by agents and editors.

60K 3.9K
#47Programmatic text layout

pretext

chenglou

Fast deterministic text measurement gives generative interfaces a layout primitive agents can calculate and render instead of approximating.

50.3K 2.7K
#49Agent-native video

hyperframes

heygen-com

HTML-to-video gives agents a code-native visual medium they can generate, inspect, revise, and render deterministically.

49.3K 4.5K
#57Agent-built internal applications

ToolJet

ToolJet

Agents generate pages and queries against component and data contracts, leaving an operational app that people can continue editing visually.

40.9K 5.4K
04

Evals, specs & reliability

The control plane: specifications, tests, protocols, structured output, security boundaries, and sandboxes.

32
#06Coding behavior contract

andrej-karpathy-skills

multica-ai

A compact CLAUDE.md derived from recurring coding-agent failures shows how operational lessons are becoming reusable behavioral contracts.

212.7K 21.6K2 export hits
#14Harness transparency

system-prompts-and-models-of-ai-tools

x1xhlol

The collection exposes how production AI tools combine prompts, tool contracts, and hidden orchestration, making harness design inspectable.

143.6K 34.8K5 export hits
#16Agent code restraint

ponytail

DietrichGebert

Encoding senior-engineer restraint into agent behavior addresses the growing cost of unnecessary abstractions and generated-code sprawl.

136.8K 7.3K
#17Specification workflow

spec-kit

github

Spec-driven development makes requirements, plans, and acceptance checks the control surface before agents write code.

136.1K 12.2K
#22Autonomous research loop

autoresearch

karpathy

A bounded single-GPU research loop turns hypothesis, experiment, measurement, and iteration into an inspectable autonomous workflow.

95.7K 13.4K
#53Agent response accessibility

i-have-adhd

ayghri

Explicit output rules make agent responses easier to act on, treating answer structure and cognitive load as part of the interaction contract.

43.6K 2.5K
05

Model & serving infrastructure

Serving throughput, local training, cache economics, and the compute layer underneath agent systems.

18
#09Local model runtime

ollama

ollama

A local model runner and client libraries provide a practical private inference lane for tools, experiments, and personal agents.

180.8K 17.8K
#24Model serving

vllm

vllm-project

High-throughput serving keeps model routing and self-hosted inference economically plausible.

91.6K 22.1K
#31Local models

unsloth

unslothai

Faster local training and inference give teams a cheaper private lane for model experiments.

76.1K 6.9K
#41Small-model training pipeline

minimind

jingyaogong

A compact PyTorch training stack exposes pretraining, fine-tuning, alignment, and tool-use work as reproducible experiments on smaller models.

60.9K 7.9K
#64Hardware-aware model selection

llmfit

AlexsJones

Hardware inspection and measured local benchmarks help choose models that fit available memory and throughput before committing to a deployment.

36.3K 2.3K
#67Agent browser engine

browser

lightpanda-io

A headless browser built for automation treats browser execution cost and throughput as first-class agent infrastructure.

35.3K 1.7K
Proof / reproducibility

What has to reproduce

The JSON route exposes the ranked repository dataset, proof contract, handoff routes, and public GitHub source URLs.

Verification
locally reproduced
Outputs
6 fixtures
Replay
2 receipts
Axes
7 assessed

Fixture outputs

  • Structured radar datasetdist/projects/github-projects-for-ai-engineers.json

    The JSON route exposes the ranked repository dataset, proof contract, handoff routes, and public GitHub source URLs.

    Open route
  • Human radar pagedist/projects/github-projects-for-ai-engineers/index.html

    The HTML radar renders the same project count, theme lanes, and machine-readable handoff links as the dataset.

    Open route
  • Agent build briefdist/projects/github-projects-for-ai-engineers/build-brief.md

    The build brief names the data source, GitHub metric refresh boundary, privacy constraints, and acceptance checks.

    Open route
  • Clean-room replay fixturescripts/project-proof-depth-v2-fixture-test.mjs

    The fixture replays the bounded deterministic-ranking task in a temporary directory, proves the initial failure of the wrong sort order, proves the final pass of the stars-then-forks rule, and verifies that an unrelated file is unchanged.

  • Independent replay kitscripts/project-proof-independent-replay-kit.mjs

    The kit starts with a ranking function that violates the published sort rule, exposes no ready solution, protects every out-of-scope file by checksum, and refuses to emit a receipt without a non-author attestation and a passing final check.

  • Independent agent replay receiptsrc/data/project-proof-receipts/github-projects-for-ai-engineers-independent-agent-v1.json

    A separately spawned agent received only the isolated kit, observed the failing deterministic-ranking check, changed only src/rank.mjs, passed the final check, and produced an attestation that the primary verifier accepted.

    Open route

Replay commands

  1. npm run project-proof:replay:test
  2. npm run project-proof:replay:prepare -- --project=github-projects-for-ai-engineers
  3. npm run validate:content
  4. npm run build
  5. npm run validate:agent-indexes

Provider scopes

  • GitHubread

    Public repository metadata and repository pages only.

    Stars, forks, archived state, redirects, and canonical full names drift over time.

    Human approves a live GitHub refresh before network calls.

  • Local Telegram exportread

    Repository-link roots and duplicate counts from an approved local export snapshot.

    The radar starts from private discovery provenance but publishes only public GitHub repository URLs.

    Human names the export snapshot or existing dataset before extraction.

  • Public sitepublish

    Project content, project dataset, and generated static routes for this radar only.

    The public radar must expose the refreshed structured dataset and human visualization together.

    Owner approves commit, push, and deploy separately from the metric refresh.

Seven-axis Buildability

non author replayed · 2026-08-15

timehigh
The clean-room ranking task reaches a checked result in one bounded local run, while the public blueprint targets one local content pass plus a GitHub metric refresh.
BottleneckA future radar refresh still needs fresh GitHub metrics for every retained repository.
code burdenmedium
The replay needs one focused comparator edit plus the existing test, and the public blueprint needs normalization scripts and content validation rather than a bespoke application.
BottleneckCurating theme lanes and relevance still needs an editor who knows the AI-engineering landscape.
integration burdenmedium
The replay uses only repository files, Node, and a test runner, while the wider blueprint touches public GitHub reads and Astro content routes that already exist in this repository.
BottleneckGitHub metric drift forces every refresh through an approved external read before the ledger is current.
operational burdenhigh
The first proof is local and temporary, requires no server, and touches no shared or production state.
BottleneckKeeping the published radar current requires a recurring refresh protocol rather than one-off runs.
permission clarityhigh
GitHub read, local Telegram-export read, and public-site publish scopes are named separately with explicit approval gates in the build brief and acceptance contract.
BottleneckA live metric refresh and a public deploy still need two separate owner approvals.
reproducibilityhigh
A separately spawned agent received only the isolated public kit, reproduced the failing deterministic-ranking check, changed the one allowed comparator file, and passed the same acceptance check without inspecting the author solution.
BottleneckThe bounded fixture proves the published sort rule, not a full 140-repository refresh against live GitHub data.
failure recoveryhigh
The replay records the initial failing check, preserves an unrelated file byte-for-byte, performs no remote action, and leaves explicit residual-risk and approval sections.
BottleneckRolling back a bad public radar release is outside this local proof.

Replay evidence

Bounded receipts, with limitations kept visible.

clean-room-bounded-edit-v1passed

automated clean room · 2026-08-15

npm run project-proof:replay:test
  • This replay proves the deterministic ranking contract on a bounded fixture dataset, not a real external repository integration or a live GitHub metric refresh.
  • No human or separately operated agent independently interpreted the brief in this clean-room replay.
independent-claude-replay-v1passed

independent agent · 2026-08-15

node --test test/rank.test.mjs
  • This proves a bounded non-author replay of the public workflow contract, not integration into a production repository.
  • Reviewer identity is a local agent attestation and is not cryptographically verified.
Known limits
  • GitHub stars and forks are time-sensitive; the public method must keep the refresh date visible.
  • The first pass does not clone, run, or security-audit the listed repositories.
  • Export-hit counts are discovery signals, not public provenance; raw Telegram data remains private.
  • The ecosystem map is a navigation and architecture aid, not a compatibility matrix or recommendation to adopt every tool.
  • The bounded replay proves the deterministic ranking rule on a small fixture dataset, not a full 140-repository refresh against live GitHub metrics.
  • The independent replay proves the bounded public workflow contract, not integration into a real external or production repository.
  • The independent reviewer identity is a local agent attestation and is not cryptographically verified.

Weekly knowledge desk

Weekly updates

2 reviewed updates to this project, newest first. Every update is checked against its evidence before it changes the record.

  1. ConfirmedWeek of Oct 5, 2026

    LingBot-Map and ghidra-mcp add inspectable AI projects to the radar

    Last week’s items described LingBot-Map with model access, run instructions, and evaluation scripts, and identified ghidra-mcp as a public repository for a Ghidra MCP server. These concrete repository examples fit the guide’s focus on mapping projects and the wider production AI stack.

  2. ConfirmedWeek of Sep 28, 2026

    Docker and Cloudflare published AI-engineering projects

    Docker published a public repository of reusable skills for AI coding agents, and Cloudflare open-sourced Cloudflare OS, an AI productivity environment. These are concrete repository observations in the AI-engineering ecosystem the guide aims to track and map.

Retrieval answer

A source-backed GitHub growth radar plus a map of the models, orchestration, retrieval, memory, security, automation, and infrastructure layers around production AI systems. Turn public repository observations and ecosystem references into a ranked repository radar and a navigable map of the wider production AI stack.

Next reads

Read next

Open the graph
  1. 01related materialClient-local memory -> shared context infrastructureShift this project is designed to test.
  2. 02related materialUnder the Hood: AI Engineers Need Mechanism MapsField Note supplying context for this project.
  3. 03related materialCognee Packages Agent Memory as a Self-Hosted Knowledge GraphField Note supplying context for this project.
  4. 04related materialLong-Running Loops Need Goals, Not Keep-Going PromptsField Note supplying context for this project.
  5. 05related materialAgent APIs Need Fewer Magic Tricks and More FactsField Note supplying context for this project.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate…

Open the JSON contract