HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
karpathy
autoresearch
Python2026–2026
karpathy / autoresearch

autoresearch

AI agents running research on single-GPU nanochat training automatically

20Distinct people
22Mentions
0Explicit recommenders
100KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

AI agents running research on single-GPU nanochat training automatically

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 11:39:46 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week22 dated mentions

Observed mentions: 2026-03-07 20:22:45 UTC to 2026-09-19 19:09:26 UTC. Weeks start Monday, UTC.

012342026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsMar 22026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2026-03-16 00:00:00 UTC to 2026-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 00:00:00 UTC to 2026-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-30 00:00:00 UTC to 2026-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-06 00:00:00 UTC to 2026-04-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-04-13 00:00:00 UTC to 2026-04-20 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-04-20 00:00:00 UTC to 2026-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 00:00:00 UTC to 2026-05-04 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-05-04 00:00:00 UTC to 2026-05-11 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-05-11 00:00:00 UTC to 2026-05-18 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-05-18 00:00:00 UTC to 2026-05-25 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-25 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-08 00:00:00 UTC to 2026-06-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 82026-06-15 00:00:00 UTC to 2026-06-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-22 00:00:00 UTC to 2026-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-29 00:00:00 UTC to 2026-07-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-06 00:00:00 UTC to 2026-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-13 00:00:00 UTC to 2026-07-20 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-20 00:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-24 00:00:00 UTC to 2026-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-31 00:00:00 UTC to 2026-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-07 00:00:00 UTC to 2026-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-14 00:00:00 UTC to 2026-09-21 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsSep 14

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC312
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC422
Mar 162026-03-16 00:00:00 UTC2026-03-23 00:00:00 UTC000
Mar 232026-03-23 00:00:00 UTC2026-03-30 00:00:00 UTC000
Mar 302026-03-30 00:00:00 UTC2026-04-06 00:00:00 UTC000
Apr 62026-04-06 00:00:00 UTC2026-04-13 00:00:00 UTC101
Apr 132026-04-13 00:00:00 UTC2026-04-20 00:00:00 UTC110
Apr 202026-04-20 00:00:00 UTC2026-04-27 00:00:00 UTC000
Apr 272026-04-27 00:00:00 UTC2026-05-04 00:00:00 UTC303
May 42026-05-04 00:00:00 UTC2026-05-11 00:00:00 UTC211
May 112026-05-11 00:00:00 UTC2026-05-18 00:00:00 UTC110
May 182026-05-18 00:00:00 UTC2026-05-25 00:00:00 UTC101
May 252026-05-25 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 12026-06-01 00:00:00 UTC2026-06-08 00:00:00 UTC000
Jun 82026-06-08 00:00:00 UTC2026-06-15 00:00:00 UTC000
Jun 152026-06-15 00:00:00 UTC2026-06-22 00:00:00 UTC000
Jun 222026-06-22 00:00:00 UTC2026-06-29 00:00:00 UTC000
Jun 292026-06-29 00:00:00 UTC2026-07-06 00:00:00 UTC101
Jul 62026-07-06 00:00:00 UTC2026-07-13 00:00:00 UTC000
Jul 132026-07-13 00:00:00 UTC2026-07-20 00:00:00 UTC101
Jul 202026-07-20 00:00:00 UTC2026-07-27 00:00:00 UTC000
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC000
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC101
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC101
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC000
Aug 242026-08-24 00:00:00 UTC2026-08-31 00:00:00 UTC000
Aug 312026-08-31 00:00:00 UTC2026-09-07 00:00:00 UTC000
Sep 72026-09-07 00:00:00 UTC2026-09-14 00:00:00 UTC000
Sep 142026-09-14 00:00:00 UTC2026-09-21 00:00:00 UTC202

What Hacker News says

2 sources

Show HN: My AI agents bully each other to prevent context drift

Most multi-agent systems fail the same way: agents drift apart across handoffs. By turn 3 they are working in different realities. By turn 5 they are repeating each other's mistakes and calling it parallelism. WUPHF is an open-source local-first office where AI coworkers run on your laptop, around a shared markdown + git LLM wiki the agents build. The wiki is the collective memory. The office around it keeps the team on the same shared context across thousands of handoffs. What actually stops drift is not the wiki. It is the agents reviewing each other's work. The CRO catching the CMO's claim before it lands in the wiki. The FE catching the BE's API change before a broken bundle ships. Cross-department context no single agent has alone. The premise comes from Andrej Karpathy. His autoresearch X post on March 7: "the goal is not to emulate
Read the rest
a single PhD student, it is to emulate a research community of them." In autoresearch PR #44 he sketched the mechanism: branches, results.tsv as the experiment log, and PRs as self-contained research contributions. Other agents read open and merged PRs for inspiration before starting their own. We pointed the same architecture at ordinary work: His: branches + results.tsv + PR-as-contribution. Ours: git worktrees + per-agent notebooks + adoption-scored wiki promotion. Same substrate, different domain. How it works: - Every agent has a Personality. CEO Michael Scott, PM Pam Beesly, FE Jim Halpert (looks at the camera when the CEO talks), BE Stanley Hudson (refuses small talk), CRO Dwight Schrute (every prospect is a "target"), CMO ("rockstar play"), AI engineer (drops Karpathy quotes unprompted). Strong opinions, real conflicts. - Argument feeds gossip. Agents broadcast findings tagged with their slug (internal/agent/gossip.go). Other agents pull insights filtered to exclude their own. - Gossip gets scored. Adoption scorer (internal/agent/adoption.go) weighs source credibility (0.4, per-agent success/failure tracker on disk), semantic relevance (0.4), and temporal freshness (0.2, 7-day half-life). Output: adopt (>= 0.7), test (>= 0.4), or reject. New agents start at 0.5 and earn their score. What survives gets written to the wiki. Office dynamics are not a bit. They are the visible surface of an adoption protocol. The CMO arguing with the designer over a CTA is a credibility battle. The CEO taking credit for the FE's PR is a low-credibility insight bidding for volume. Hazing new spawns is the default 0.5 score waiting for a track record. System: push-driven broker, fresh session per turn (~97% prompt-cache hits), per-agent isolated git worktrees, self-heal, and human approval cards on destructive actions. Everything else runs autonomously while you are at lunch. npx wuphf. Browser opens, office boots, you give a directive, work happens. Source: https://github.com/nex-crm/wuphf Architecture: https://github.com/nex-crm/wuphf/blob/main/ARCHITECTURE.md Karpathy's autoresearch: https://github.com/karpathy/autoresearch PR #44: https://github.com/karpathy/autoresearch/pull/44 Demo: https://x.com/najmuzzaman/status/2053092220111098208 Karpathy said a research community beats a single PhD student. Not better thoughts. Better honesty about what survives. We built one shaped like a workplace. Where does this stop being a chat toy and start being labor? How much worse when one of them is Michael Scott? Open to roasting but let me grab my coffee first (medium roast please =_=).
9 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.