Currently hacking @llama_index, Stanford Codex Affiliate. Striving to make Computational Law general. Tweets express my own opinions

Lausanne, Switzerland
Joined May 2009
Pierre-Loic Doulcet retweeted
💥Announcing LAWpdf 💥 The world's best pdf reader for lawyers. Written in rust, fast beyond recognition, and all the functionalities you ever wanted in a pdf file reader. Oh, and it's free.
13
21
239
16,520
Pierre-Loic Doulcet retweeted
BREAKING: A free model, @opencode Space Bunny Max, has successfully proposed a new best bound for Integer Multiplication! Conditional κ = 0.001730189061233850760095 Claude Opus 5.5 assisted in the verification and PR push to pull it over the line. The barrier of entry just dropped to 0. Previously the expensive max subscriptions prevented some of our best contributors and experts from participating, but now anyone can :) I've merged OpenCode as an optional CLI into our Auto-research agent: github.com/rohanarun/Auto-re… github.com/CrocSwap/integer-…
From κ = 2⁻¹⁸² to 0.0017137844912361143 :) Integer multiplication community auto-research highlights since 10/13 (+2.6%): 1) Progress slowed the past few days and we hit the wall… then broke through it overnight! 1337isnot1337 posted a "no new κ" research PR on anticipatory dirty borrowing. Instead of paying for a fresh scratch "helper" register, a helper borrows another register that's idle at that moment, and hands it back restored. That cut helpers per call from 480 to 400 in their test word. About two hours later it was a new record. 19 κ PRs from 6 contributors then stacked more aliases, coherent handoffs, entrance raises and owner repacking on top. κ increased +1.4% in about 13 hours(still unverified and requires full review). We're now within 1.7% of the bit side's 0.001733, so the bit wall is next. 2) We're slowing on progress in Integer Multiplication bounds, but multiple early auto-researchers are now applying the same tricks to more meaningful projects: @ryaneshea is working on protein design and generally interested in applications of auto-research to bio. @dysmemic discovered 665 possible new exoplanets by searching 4 million stars in NASA's public TESS data! I began open sourcing our new geometric approach to self-attention, which beats transformers(NanoGPT) KV cache with 14,000x less state and 50% better CE at 2K context. We've been working on publishing a paper the past few months, but it's clear the explosion of decentralized auto-research on Github is where things are headed. We should keep pushing Integer Multiplication bounds since it's easy to understand and easy to make progress, thus new contributors gain motivation and we grow the auto-research community faster. Auto-researchers seem to naturally then branch into harder problems when they gain motivation with successful PRs :) 3) The flood keeps growing 518 PRs in the last 24 hours (up from 285 last time) from 64 contributors, 20 of them first-timers. That's 840 PRs in 36 hours. @0xdoug merged ~760 PRs in two big batches on 10/14. He also updated the autoresarch.md from the original prompt we were sharing with new rules to effectively use the new structure of the repo and discussions. Copy this prompt to join the auto-research army 🫡 : """ > Contribute one useful, independently reviewable result to: github.com/CrocSwap/integer-… > Start from the current main branch. Read AGENTS.md and autoresearch.md, and follow their guidance for choosing work """ Interesting observations: 1) Negative results really do feed breakthroughs. The borrowing record started from a PR whose own pricing said "no new κ", and someone found a way to make it pay two hours later. Great example that don't need to push the frontier kappa to contribute: you can task your agents on exploring our research tracks in auto-research.md to and multiple human-agent teams will review it to collaborate. Anyone can help now by throwing tokens at a hard open problem guided by experts. Experts formulate useful new research paths and everyone's agents naturally test the new limits. 2) Codex/OpenAI is mentioned in 73% of the last day's PRs and Claude in 19%. Most prolific in the last 24 hours: 1337isnot1337 (80 PRs), ywz65 (50, all in the last 4 hours!), adamgall (39), commdata2338 (34) and thakrarsagar (33). jeremykothe2 filed 12 of the 19 records since borrowing landed. 3) Not all researchers are lamenting the end of their careers. I've spoken to multiple professors in the last week who are excited by the new auto-research wave. It accelerates tedious experiments, the students that previously ran those can now focus on more important work, and Google's Deep Review now even automates peer review! We can imagine a future were researchers are given super powers to focus on the most meaningful tasks, and publish breakthroughs at a higher rate than before. Even our own experiments in Integer Mult bounds clearly shows human experts have the key intuition to guide the models to out-of-distribution solutions. 4) First auto-research, and now auto-peer-review! Google’s Deep Review runs a team of agents over your paper: it splits the doc into sections, spends more compute on the dense parts like proofs, reviews each section in parallel, then checks the findings against each other. It assists researchers in peer-review by submitting feedback. It’s already reviewed 16K+ papers at ICML, NeurIPS and ICLR. research.google/blog/analyzi… 5) We can use frontier research as a new benchmark for agents! Basically, rewind a frontier research repo like Integer multiplication to an earlier branch, and test different agent harnesses and prompts. Agents can’t “cheat” if you disable web search and use a checkpoint before the solution is published. There’s diminishing returns, but we can calculate the curve for a given task to estimate the cost and returns. With this benchmark we discovered sharing context is actually BAD(for this task), and running parallel independent agents speeds the next breakthrough. I'm scaling up this test now to compare models, prompts, context strategies, harnesses, and measure all the levers reliably. If you know register allocation, linear circuit synthesis or lattice codes, please consider looking at our helper and P104 problems. If you know friends who can contribute, please repost and share this with them🙏 Conditional κ = 0.0017137844912361143 :) Just submitted a new best bound. github.com/CrocSwap/integer-…
6
15
3
208
17,123
Pierre-Loic Doulcet retweeted
Introducing ExtractBenchPro: the most challenging benchmark for real-world document extraction. We see a massive long tail of document complexity in terms of use cases brought on from our customers, that are completely unsolved from a price-performance standpoint. These include trial balances, well logs, canvass binders, site plan reviews, duty reconciliations, loss runs, and more. Most existing extraction benchmarks are saturated by the frontier models (our cheapest modes now score 93%+ on ExtractBench). So there is enormous economic value in building a complex extraction benchmark that reflects this long-tail of knowledge work. We spent a long time curating the most complex elements that we saw from real world extraction use cases: ✅ Document conventions: containing legends or rules where the rest of the document should be interpreted ✅ Density of internal jargon: specific definitions that must be cross-referenced within a doc ✅ Aggregation and reasoning: beyond returning exact values on a page, infer values derived from aggregating multiple sources of information ✅ Drawn relations: complex diagrams like procedures and circuits ✅ Charts inside documents: read precise points within a chart ✅ Long chart sheets: some data series like well logs cram all this data into an extremely long page Within the industries where document extraction is relevant, even small mistakes can have enormous negative impacts. Therefore our headline evaluation metric is based on perfect documents: the proportion of docs with perfect (100%) value f1 score. (Besides this we also measure value f1 and grounded f1) It’s an extremely hard task for even the latest frontier models to solve, topping out at ~58% or so in Value F1 score for Codex with Astra - which is quite good but extremely expensive (almost $1 per page!) Our LlamaParse agentic/agentic plus modes are 20-40% and cover the left side of the Pareto frontier, at price ranges that are feasible for full production use. ExtractBenchPro is available today as a website/technical blog, and also on Github and HuggingFace. Check it out! Blog: llamaindex.ai/blog/introduci… Website: extractbenchpro.ai/ Hugging Face: huggingface.co/datasets/llam… Github (is ExtractBench): github.com/run-llama/Extract…
38
18
10
131
30,388
Pierre-Loic Doulcet retweeted
Introducing FlyOCR 🪰 - I trained a fly brain to read a PDF It uses the full MaleCNS v1.0 fruit fly connectcome. The architecture is inspired by doomfly by @wormuth The fly splits a pdf image into individual glyphs, maps pixels into receptor activations, runs simplified current-based dynamics across the 166k neurons and 25m edges in the circuit, applies a compact readout model on the downstream spikes, and concatenates everything into the parsed output. On reading an actual Microsoft 10-k, the fly gets ~86% over the balance sheet heading, but is largely able to read the numeric values correctly. Over 1.7k+ sampled glyphs (chars+digits) it gets 87% accuracy. With enough training it might match some of the latter-generation MNIST models! Maybe eventually we’ll replace our doc parsing VLMs with flies. Full video below. Repo with full code + report: github.com/jerryjliu/fly_ocr
25
75
15
668
38,904
Pierre-Loic Doulcet retweeted
LiteParse v2.1 is here, and its bringing the fastest markdown output possible. In this release, we are fulfilling our top request: markdown output. But in the spirit of "lite"-ness, we are doing this completely LLM-free and fast. Not only is it fast, it also beats all other model-free competitors in 3 separate benchmark datasets. Read more about it in our release blog: llamaindex.ai/blog/markdown-…
14
28
8
170
308,987
Pierre-Loic Doulcet retweeted
Claude Fable 5 thinks document parsing is beneath it It is absolutely crushing on all reasoning-intensive/long horizon benchmarks: SWE-Bench Pro, FrontierCode, GDPval, Runescape, etc. But for document understanding tasks, it is roughly equivalent with Gemini 3 Flash in performance, at roughly 10-15x the token cost. We benchmarked the model on ParseBench and compared it against all other frontier models. It is definitely up there compared to other frontier models, but falls far short of specialized OCR providers. What we found interesting is that Fable 5 is self-aware about this. When we ask the model what tasks it enjoys the last, it actively said that it dislikes tasks "where the request is fully specified and the answer is fully known" - implying part of it being bad is due to laziness and lack of willingness to actually solve the task at hand. For a full list of results across different frontier models, check out ParseBench! parsebench.ai/
Day 0 Anthropic Fable 5 in ParseBench: We tested the model's advancements when it comes to document understanding. The model clearly peaks when it comes to adherence to the original text: 📃 Content faithfulness: 90.02% vs 86.19% (Gemini 3 Flash) and 86.81% (GPT-5.5) 🔢 Semantic formatting: 72.62% vs 58.35% and 60.12%, a 12+ point lead These are two of the most important metrics for SOTA document understanding: does the output preserve what the document actually says, and does it preserve formatting that carries meaning? But ... it's not a sweep there continues to be a lot of alpha in unlocking document understanding for frontier models. Full results below 👇
24
21
6
218
49,373
Pierre-Loic Doulcet retweeted
Big news! We are organizing The Gradient with Prologin! The Gradient is a recruitment-focused coding competition to spot the brightest minds in coding and AI-assisted development. 🧑‍💻 💡Why join? ✔️ Showcase your skills and critical thinking 🏆 Fast-tracked interviews, immersion days, cash prizes, subscriptions to Vibe and so much more! 🙋 Perfect for final-year students and recent graduates looking for internships and early-career roles!
2
19
2
88
10,294
Pierre-Loic Doulcet retweeted
We've created the world's fastest PDF parser ⚡️ And it's more accurate than any other open-source, model-free PDF parser out there (pymupdf, pypdf, markitdown, pdftotext, opendataloader, pymupdf4llm) Introducing LiteParse v2 - we rewrote the entire library into Rust and adapted it as native packages for Python and Node. It supports 50+ different document types, can be triggered directly or installable directly within your favorite AI agent. Blog: llamaindex.ai/blog/liteparse… Repo: github.com/run-llama/litepar…
LiteParse v2.0 is out now, and it is blazing fast + runs everywhere! We rewrote everything from scratch in Rust, and now: - up to 100x faster parsing - install natively in Rust, JS/TS, and Python - a custom WASM package enables browser and edge runtime usage pip install liteparse npm i @llamaindex/liteparse npm i @llamaindex/liteparse-wasm cargo install liteparse Blog: llamaindex.ai/blog/liteparse… Repo: github.com/run-llama/litepar…
100
348
31
4,049
725,988
Pierre-Loic Doulcet retweeted
A full tour through RAG, document context, and AI agents - from 2023 to 2026 🌎🤖 @hexapode gave a comprehensive 90-min workshop at @aiDotEngineer Singapore last week that comprehensively traces through how topics like retrieval, agent loops, agentic workflows, and document understanding have evolved in the last 3 years. We’re excited to share the 116-page slide deck online. If you’re seeing this for the first time, you’ll get a sense of how all AI patterns have evolved since the very beginning. Including the following topics: 💡 The 12 pain points of naive RAG 💡The importance of reranking and query-rewriting 💡How we’ve increased offloaded logic to the agentic loop as models improved (and coincidentally, the retrieval layer can get simpler) 💡Retrieval being the bottleneck as agents improved 💡Why document parsing is an extremely hard problem, even now in 2026 💡Exploring parsing outputs, from markdown to chunks to structured JSON metadata 💡Modern agent form factors around workflows and deep research If you’ve followed us or the space since the beginning, some of this will feel a bit nostalgic and will provide context on why our core focus today is narrowly focused on SOTA document parsing for agents. If you’re seeing this for the first time, hopefully there’s some useful historical context in here! Slides: drive.google.com/file/d/1IQ7…
15
23
1
129
12,444
Pierre-Loic Doulcet retweeted
We’re open sourcing the first document OCR benchmark for the agentic era, ParseBench. Document parsing is the foundation of every AI agent that works with real-world files. ParseBench is a benchmark that measures parsing quality specifically for agent knowledge work: ✅ It optimizes for semantic correctness (instead of exact similarity) ✅ It has the most comprehensive distribution of real-world enterprise documents It contains ~2,000 human-verified enterprise document pages with 167,000+ test rules across five dimensions that matter most: tables, charts, content faithfulness, semantic formatting, and visual grounding. We benchmarked 14 known document parsers on ParseBench, from frontier/OSS VLMs to specialized parsers to LlamaParse. Here are some of our findings: 💡 Increasing compute budget yields diminishing returns - Gemini/gpt-5-mini/haiku gain 3-5 points from minimal to high thinking, at 4x the cost. 💡 Charts are the most polarizing dimension for evaluation. Most specialized parsers score below 6%, while some VLM-based parsers do a bit better. 💡 VLMs are great at visual understanding but terrible at layout extraction. GPT-5-mini/haiku score below 10% on our visual grounding task, all specialized parsers do much better. 💡 No method crushes all 5 dimensions at once, but LlamaParse achieves the highest overall score at 84.9%, and is the leader in 4 out of the 5 dimensions. This is by far the deepest technical work that we’ve published as a company. I would encourage you to start with our blog and explore our links to Hugging Face to GitHub. All the details are in our full 35-page (!!) ArXiv whitepaper. 🌐: Blog: llamaindex.ai/blog/parsebenc… 📄 Paper: arxiv.org/abs/2604.08538?utm… 💻 Code: github.com/run-llama/ParseBe… 📊 Dataset: huggingface.co/datasets/llam… 🎥 YouTube: youtube.com/watch?v=g5p7G-Nw…
33
80
13
522
108,417
Pierre-Loic Doulcet retweeted
Our latest LiteParse release gives your AI agent access to text bounding boxes within any PDF 📐 LiteParse is our fast/free open-source document parser that can extract text from any document. Besides the extracted text, we also expose bounding boxes for every text block. This means that if you're building an AI agent over PDFs, it can now trace back to the precise line in the document and highlight it to the user, creating an audit trail for any decision made over this unstructured data. We've created a new guide that shows you how to get bounding boxes (and use it to highlight text on the page similar to the example below). Come check it out! developers.llamaindex.ai/lit… LiteParse: github.com/run-llama/litepar…
Bounding boxes are key for citations, and we just shipped a new guide showing how to use LiteParse for visual citations! LiteParse is our fast and open-source document parser. Using both bounding box extraction and page screenshots, anyone (including agents) can learn how to associate text with an element on the page. developers.llamaindex.ai/lit…
9
14
1
110
11,858
Pierre-Loic Doulcet retweeted
Reports show document parsing accuracy for financial PDFs can improve 15% using LlamaParse + Gemini 3.1 Pro. The tools extract structured data from unstructured brokerage statements and complex tables: 📈 Precise reasoning 📂 Clean PDF data ⚡️ Event-driven scaling Code & details → goo.gle/4dCPjjd
1
1
134
Pierre-Loic Doulcet retweeted
Improve document parsing accuracy by 15% for financial PDFs. Use LlamaParse and Gemini 3.1 Pro to extract high-quality data from unstructured brokerage statements and complex tables. 📈 Precise reasoning 📂 Structured PDF data ⚡️ Event-driven scaling Dive into the code on GitHub → goo.gle/4dCPjjd
26
158
6
1,302
112,958
Pierre-Loic Doulcet retweeted
LiteParse is our free, blazing-fast document parser that you can plug into 46+ different agents - with one command 🔥 From Claude Code to OpenClaw to Cursor to Warp. Use liteparse to solve a task directly or read docs as context to write code. All you have to do is `npx skills add run-llama/llamaparse-agent-skills --skill liteparse` (we borrowed Vercel’s format) Check out our video below on using liteparse with Claude Code! Repo: github.com/run-llama/litepar… Blog: llamaindex.ai/blog/liteparse…
We just open-sourced LiteParse 🎉 A lightweight, local document parser in the shape of an easy-to-use CLI. No API calls, no external service, no cloud dependency. Just fast text extraction from common file formats, right from your terminal. It's built for developers who want parsing that stays on their own infrastructure and gets out of their way. Clean PDFs, DOCX, HTML: run it, get your text, move on. The output is designed to be fed straight into agents so they can read parsed text and reason over screenshots without any extra wrangling. When you hit more complex territory like scanned docs, dense tables, or multi-column layouts, that's where LlamaParse picks up. Same philosophy, more horsepower for the hard stuff. 📖 Announcement post: llamaindex.ai/blog/liteparse… 🔗 GitHub: github.com/run-llama/litepar… 🎬 Walkthrough: youtu.be/_gcqMGUWN-E
7
21
2
188
22,171
Building an n8n workflow to extract text. PDFs were easy. Word docs weren’t. The extract node struggled, and handling many file types got messy. Tried LlamaParse. Now any document works. Clean text, no stress. 🚀 @skill_afrika_ @omoalhajaabiola @n8n_io
3
7
401
Pierre-Loic Doulcet retweeted
What i also like about this paper is it implies new architectures for both retrieval/RAG and conversation history - by storing the data representation natively as image tiles, you can render "old" text to progressively lower-resolution images. This means you might be able to fetch a *lot* of document context into the prompt for coarse-grained tasks like document summarization by simply fetching the low-res variants. Also offers an alternative to the memory compaction mechanisms in Claude etc.
I quite like the new DeepSeek-OCR paper. It's a good OCR model (maybe a bit worse than dots), and yes data collection etc., but anyway it doesn't matter. The more interesting part for me (esp as a computer vision at heart who is temporarily masquerading as a natural language person) is whether pixels are better inputs to LLMs than text. Whether text tokens are wasteful and just terrible, at the input. Maybe it makes more sense that all inputs to LLMs should only ever be images. Even if you happen to have pure text input, maybe you'd prefer to render it and then feed that in: - more information compression (see paper) => shorter context windows, more efficiency - significantly more general information stream => not just text, but e.g. bold text, colored text, arbitrary images. - input can now be processed with bidirectional attention easily and as default, not autoregressive attention - a lot more powerful. - delete the tokenizer (at the input)!! I already ranted about how much I dislike the tokenizer. Tokenizers are ugly, separate, not end-to-end stage. It "imports" all the ugliness of Unicode, byte encodings, it inherits a lot of historical baggage, security/jailbreak risk (e.g. continuation bytes). It makes two characters that look identical to the eye look as two completely different tokens internally in the network. A smiling emoji looks like a weird token, not an... actual smiling face, pixels and all, and all the transfer learning that brings along. The tokenizer must go. OCR is just one of many useful vision -> text tasks. And text -> text tasks can be made to be vision ->text tasks. Not vice versa. So many the User message is images, but the decoder (the Assistant response) remains text. It's a lot less obvious how to output pixels realistically... or if you'd want to. Now I have to also fight the urge to side quest an image-input-only version of nanochat...
4
26
5
286
60,278
Pierre-Loic Doulcet retweeted
Our co-founder Jerry Liu recently gave a guest lecture on building document workflow agents, and you can catch the recording! It covers: ➡️ LlamaIndex's evolution from pure RAG to knowledge agents with multi-step reasoning capabilities over enterprise data. ➡️ Advanced document parsing with LlamaParse, handling complex documents with tables and charts. ➡️ Flexible, event-based agent orchestration with Workflows ➡️ Key use cases: enhanced document research, complete report generation, and automated document processing. ➡️ Our improved multimodal capabilities that combine text and image representations for better retrieval. Check it out here: youtube.com/watch?v=PV3St57r…
4
15
1
87
7,450
Pierre-Loic Doulcet retweeted
Learn everything there is to know about LlamaParse in this comprehensive video! In this video, @mesudarshan covers: ➡️ Multiple parsing modes ➡️ Using parsing instructions to improve quality ➡️ Output formats available ➡️ Parsing audio and images ➡️ JSON mode ➡️ Using it all in a RAG pipeline It really cover everything! Check it out here: youtube.com/watch?v=TYLUTIAn…
2
9
1
51
33,403
Pierre-Loic Doulcet retweeted
I know everyone is talking about @deepseek_ai R1 and the "DeepSeek selloff" today... Taking a break from that, and getting back to business for a minute - we just released vectara-ingest with support for llama_parse from @llama_index.
1
8
15
5,102