Building agents @TechAtBloomberg; Previously Postdoc @jhuclsp JHU; PhD @GeorgiaTech

Joined September 2015
Accepted to #NeurIPS2026 #NeurIPS πŸ₯³ We've added more experiments and new findings; stay tuned for the camera-ready version.
Multimodal LLMs can read text in images, but why do they often perform worse than when the same text is given as tokens? Our work studies the modality gap of models perceiving text as pixels and shows how to close it. πŸ“„ arxiv.org/abs/2603.09095 πŸ§΅πŸ‘‡ #NLProc #LLM #ComputerVision
7
39
2,007
πŸ”₯FIRE-Bench got into #ICML2026πŸŽ‰ Our take on #AutoResearch: target real human-verified scientific insights, not engineered ML models Stay tuned for two follow-ups: 1️⃣ FIRE-Bench scaled into the "SWE-Bench" of research agents 2️⃣ Paper2Bench: any paper β†’ a verifiable benchmark
πŸ€–πŸ”¬ Can AI actually do science end-to-end? πŸ§ πŸ“ˆ And how would we know when it matches, or surpasses, humans? ⚑πŸ§ͺ AI is rapidly automating scientific discovery, but benchmarking full-cycle discovery, from πŸ’‘ ideation β†’ πŸ§‘β€πŸ’» execution β†’ πŸ“Š conclusions, remains unsolved: 🧐🧐🧐 βŒπŸ› οΈ Open-ended discovery β†’ manual validation (costly, unscalable) βŒπŸ“ Metric-driven benchmarks (e.g., MLE-Bench) β†’ convenient but narrow (is higher accuracy really enough?) βŒπŸ€–βš–οΈ LLM-as-judge β†’ useful, but fundamentally risky if used alone πŸ”₯πŸš€ Introducing FIRE-BenchπŸ”₯: Fullcycle Insight Rediscovery Evaluation πŸ‘‰πŸŒ firebench.github.io πŸ“šβœ¨ A benchmark that turns fresh, human-verified insights from recent πŸ† NeurIPS / ICLR / ICML papers into masked, end-to-end discovery challenges 🧩 πŸŒπŸ” Constrained open-ended discovery–backed by ground truth. πŸ“Œ Key takeaways: 1⃣ πŸ“–πŸ§± Reference-based evaluation still matters: constrained LLM judging helps, but human-grounded references remain essential until agents can consistently match human conclusions 2⃣ πŸ†πŸ§  Expert-validated ground truth: all tasks come from recent NeurIPS / ICLR / ICML papers, with contamination carefully controlled 3⃣ πŸ”πŸŽ­ Rediscovery, not reproduction: original πŸ§ͺ methods, πŸ“Š experiments, πŸ’» implementations, and πŸ“ˆ analyses are fully masked to create real discovery challenges πŸ”‘ Key empirical findings: πŸ’‘ The "Science Gap" is Real: Even the best setup (Claude Code + Sonnet-4) caps out at an F1 score of 46.7. On hard tasks, agents struggle to break 30 πŸ’‘ Success is a "Lottery": Performance has incredibly high variance. Reliability is a major unsolved issue. πŸ’‘ Coding is no longer the bottleneck; high-level reasoning and analysis are: ~74% of errors stem from flawed planning, not coding βš™οΈ How it works: πŸ”Ή Research-Problem Trees: We parse papers into trees (from broad roots to concrete leaves). This allows us to select intermediate nodes that perfectly balance open-ended exploration with verifiable ground truth. πŸ”Ή Claim-Level Evaluation: We match AI conclusions against human conclusions using granular claim decomposition (F1 score). πŸ”Ή Creativity Check: We score false positives to see if agents are finding novel truths (Spoiler🚨: they aren’t creative yet). πŸ”Ή New Diagnostic Taxonomy: failures traced across four stages: 🧠 Planning β†’ πŸ› οΈ Implementation β†’ ▢️ Execution β†’ 🧾 Conclusion πŸ”Ή Additional Analyses: cost efficiency, contamination checks, and more. πŸ‘€ The Future: πŸš€ Live-FIRE-Bench: a live, continuously updated FIRE-Bench to track real-time progress on the latest research (Newest LLMs should be benchmarked with the newest research) πŸš€ Stronger scaffolding (search + planning + coding) 🧠🧰 and converting FIRE-Bench into interactive environments for training research agents πŸš€ Toward real creativity: We want better systems that can produce genuinely novel conclusions toward creativity 🎨⏳ πŸš€ Better systems 🧠✨ and better benchmarks πŸ“ must co-evolve πŸ”„ over time πŸ“œπŸŽ₯ Paper, video, demo, and research trees: πŸ‘‰πŸŒ firebench.github.io #AI πŸ€– #MachineLearning πŸ“š #AI4Science πŸ”¬ #LLMs 🧠 #Research πŸ§ͺ #AgenticAI πŸš€ #FireBench πŸ”₯
4
20
2,507
Excited to share our latest work on the modality gap in multimodal LLMs. Imagine an agent interacting with the real world as humans do. The text it encounters on signs, documents, or screens appears as pixels, not tokens. Yet MLLMs often perform worse when reading the same text from images. We study this gap and show how to close it.
Multimodal LLMs can read text in images, but why do they often perform worse than when the same text is given as tokens? Our work studies the modality gap of models perceiving text as pixels and shows how to close it. πŸ“„ arxiv.org/abs/2603.09095 πŸ§΅πŸ‘‡ #NLProc #LLM #ComputerVision
3
11
1,910
Love this direction from @karpathy. Autonomous agents iterating on training runs feel like a modern renaissance of AutoML, except now the search space includes research decisions themselves: architectures, training setups, analysis pipelines, etc. But if β€œautoresearch” becomes a thing, the obvious question is: how do we measure progress in β€œautoresearch”? - Paper generation, single metrics, LLM-as-judge, or traditional reproducibility research? That’s exactly the motivation behind FIRE-Bench (Full-cycle Insight Rediscovery Evaluation): xitter.cf/zhenwang9102/status/20… Instead of optimizing a single metric or judging papers, FIRE-Bench evaluates whether agents can rediscover real scientific insights from recent NeurIPS / ICLR / ICML papers: - Turn papers into research-problem trees and select a proper research problem to ask (neither too broad nor too narrow) - We mask the original methods, experiments, and conclusions - Ask agents to go from idea β†’ implementation β†’ experiments β†’ conclusions - Then score them via claim-level matching against expert-validated ground truth What we found so far: - Even the strongest agents struggle (best F1 β‰ˆ 46.7) - Performance is extremely high variance (β€œresearch lottery”) - Planning and reasoning, not coding, is the main bottleneck If autoresearch systems like this keep improving, benchmarks must evolve alongside them. Better research agents πŸ€– need better ways to measure real discovery πŸ”¬ FIRE-Bench: firebench.github.io
I packaged up the "autoresearch" project into a new self-contained minimal repo if people would like to play over the weekend. It's basically nanochat LLM training core stripped down to a single-GPU, one file version of ~630 lines of code, then: - the human iterates on the prompt (.md) - the AI agent iterates on the training code (.py) The goal is to engineer your agents to make the fastest research progress indefinitely and without any of your own involvement. In the image, every dot is a complete LLM training run that lasts exactly 5 minutes. The agent works in an autonomous loop on a git feature branch and accumulates git commits to the training script as it finds better settings (of lower validation loss by the end) of the neural network architecture, the optimizer, all the hyperparameters, etc. You can imagine comparing the research progress of different prompts, different agents, etc. github.com/karpathy/autorese… Part code, part sci-fi, and a pinch of psychosis :)
2
14
1,038
Really excited to co-lead this work. πŸš€ Agentic AI for scientific discovery is moving fast β€” but it’s not there yet. Across FIRE-BenchπŸ”₯, even SOTA agents (e.g., Claude Code and Codex) stay <50 F1, struggling with research planning and drawing valid conclusions from experiments. More strikingly, performance variance across runs is huge, highlighting how brittle current agents are on long-horizon, full-cycle research tasks. Lots of room to push forward. πŸ”¬πŸ€–
πŸ€–πŸ”¬ Can AI actually do science end-to-end? πŸ§ πŸ“ˆ And how would we know when it matches, or surpasses, humans? ⚑πŸ§ͺ AI is rapidly automating scientific discovery, but benchmarking full-cycle discovery, from πŸ’‘ ideation β†’ πŸ§‘β€πŸ’» execution β†’ πŸ“Š conclusions, remains unsolved: 🧐🧐🧐 βŒπŸ› οΈ Open-ended discovery β†’ manual validation (costly, unscalable) βŒπŸ“ Metric-driven benchmarks (e.g., MLE-Bench) β†’ convenient but narrow (is higher accuracy really enough?) βŒπŸ€–βš–οΈ LLM-as-judge β†’ useful, but fundamentally risky if used alone πŸ”₯πŸš€ Introducing FIRE-BenchπŸ”₯: Fullcycle Insight Rediscovery Evaluation πŸ‘‰πŸŒ firebench.github.io πŸ“šβœ¨ A benchmark that turns fresh, human-verified insights from recent πŸ† NeurIPS / ICLR / ICML papers into masked, end-to-end discovery challenges 🧩 πŸŒπŸ” Constrained open-ended discovery–backed by ground truth. πŸ“Œ Key takeaways: 1⃣ πŸ“–πŸ§± Reference-based evaluation still matters: constrained LLM judging helps, but human-grounded references remain essential until agents can consistently match human conclusions 2⃣ πŸ†πŸ§  Expert-validated ground truth: all tasks come from recent NeurIPS / ICLR / ICML papers, with contamination carefully controlled 3⃣ πŸ”πŸŽ­ Rediscovery, not reproduction: original πŸ§ͺ methods, πŸ“Š experiments, πŸ’» implementations, and πŸ“ˆ analyses are fully masked to create real discovery challenges πŸ”‘ Key empirical findings: πŸ’‘ The "Science Gap" is Real: Even the best setup (Claude Code + Sonnet-4) caps out at an F1 score of 46.7. On hard tasks, agents struggle to break 30 πŸ’‘ Success is a "Lottery": Performance has incredibly high variance. Reliability is a major unsolved issue. πŸ’‘ Coding is no longer the bottleneck; high-level reasoning and analysis are: ~74% of errors stem from flawed planning, not coding βš™οΈ How it works: πŸ”Ή Research-Problem Trees: We parse papers into trees (from broad roots to concrete leaves). This allows us to select intermediate nodes that perfectly balance open-ended exploration with verifiable ground truth. πŸ”Ή Claim-Level Evaluation: We match AI conclusions against human conclusions using granular claim decomposition (F1 score). πŸ”Ή Creativity Check: We score false positives to see if agents are finding novel truths (Spoiler🚨: they aren’t creative yet). πŸ”Ή New Diagnostic Taxonomy: failures traced across four stages: 🧠 Planning β†’ πŸ› οΈ Implementation β†’ ▢️ Execution β†’ 🧾 Conclusion πŸ”Ή Additional Analyses: cost efficiency, contamination checks, and more. πŸ‘€ The Future: πŸš€ Live-FIRE-Bench: a live, continuously updated FIRE-Bench to track real-time progress on the latest research (Newest LLMs should be benchmarked with the newest research) πŸš€ Stronger scaffolding (search + planning + coding) 🧠🧰 and converting FIRE-Bench into interactive environments for training research agents πŸš€ Toward real creativity: We want better systems that can produce genuinely novel conclusions toward creativity 🎨⏳ πŸš€ Better systems 🧠✨ and better benchmarks πŸ“ must co-evolve πŸ”„ over time πŸ“œπŸŽ₯ Paper, video, demo, and research trees: πŸ‘‰πŸŒ firebench.github.io #AI πŸ€– #MachineLearning πŸ“š #AI4Science πŸ”¬ #LLMs 🧠 #Research πŸ§ͺ #AgenticAI πŸš€ #FireBench πŸ”₯
3
10
1,235
πŸ€” LLMs can ace Olympiad math, yet struggle with something as β€œsimple” as NER β€” even with in-context learning (ICL)? πŸ’‘ Our #EMNLP2025 paper answers why: β€œLLMs are Better Than You Think: Label-Guided In-Context Learning for Named Entity Recognition.” @mdredze @jhuclsp πŸ‘‰ TL;DR: The issue isn’t the LLM β€” it’s how we pick demonstrations. πŸ“„ arxiv.org/pdf/2505.23722v2 1/8
2
2
8
1,249
Even vs strong fine-tuned models like GoLLIE-34B, DEER (with GPT-4o) is competitive β€” all without training πŸ’ͺ Training-free, label-aware, and robust. LLMs can do NER β€” they just need better demonstrations. 8/8
1
74
Please check out 🦌 Paper + Code for more details! πŸ“„ arxiv.org/pdf/2505.23722v2πŸ“· πŸ’» github.com/bflashcp3f/deerπŸ“·
54
Fan Bai retweeted
Can LLM-simulated users replace expensive human evaluation for multi-turn conversations? Short answer: yes, if you model the user right. With our SimulatorArena, we find that detailed user profiles (knowledge + message style) improve alignment with real human evaluation by 26% at <3% the cost. #EMNLP2025 [1/6] 🧡
4
25
1
133
10,125
What happens when an LLM is asked to use information that contradicts its knowledge? We explore knowledge conflict in a new preprintπŸ“‘ TLDR: Performance drops, and this could affect the overall performance of LLMs in model-based evaluation.πŸ“‘πŸ§΅β¬‡οΈ 1/8 #NLProc #LLM #AIResearch
4
24
2
86
11,589
Glad to see my first project at JHU has been accepted to #ml4h2024. Here are a few key takeaways: 1. Naive prompting often produces "easy-to-learn" examples, and methods that promote syntactic diversity in LLM output don't address this fundamental issue.
Today at #ML42024: Clinical QA can help doctors find critical information in patient records. But where do we get training data for these systems? Generating this data from an LLM is hard. 🧡 @loadingfan
1
3
20
3,428
3. Scaling synthetic data narrows the gap with human-generated data, though the label quality of "hard-to-learn" examples remains the central bottleneck, which may be addressed through selective annotation.
1
109
Please checkout our paper and code for more details! Paper: arxiv.org/pdf/2412.04573 Code: github.com/bflashcp3f/synthe…
1
66