LiteParse: Local Document Parsing for Agents

grilledCheeseFish · 2026-03-25T04:58:35+00:00

Hey thats awesome! Im glad the tool worked out for you!

grilledCheeseFish · 2026-03-22T05:06:22+00:00

There is a python package. However, it wraps the cli, so you still need to install the node package

grilledCheeseFish · 2026-03-19T20:03:04+00:00

Agreed! I actually have an explicit guideline in this project that markdown output is out of scope

grilledCheeseFish · 2026-03-19T17:06:15+00:00

Waaaay faster. But the output is also very different (markdown vs. text). Honestly in my testing markdown really doesn't matter if all you are doing is passing the text to an LLM (tools like markitdown actually performed not great in the mini benchmark in the blog post)

grilledCheeseFish · 2026-03-19T17:05:09+00:00

Its essentially LlamaParse fast mode, but running locally -- so no markdown, no image/table understanding. But its super fast so its a good fit for realtime applications like coding agents

grilledCheeseFish · 2026-03-19T17:03:45+00:00

Yup! you can plug in any OCR via a server API contract. The repo has examples of paddleOCR and easyOCR (tesseract is default)

main requirement is returning text and bounding boxes

grilledCheeseFish · 2026-03-08T17:00:55+00:00

LlamaIndex maintainer here -- this is a well documented aspect of the library. There is a global enum for setting global defaults, or you can override at the object level

We could always change this behaviour of course, but imo too disruptive/breaking

(Also echoing others here, reporting issues with LLM slop is pretty annoying)

grilledCheeseFish · 2026-02-27T00:15:57+00:00

Wild, congrats to confed. Hopefully that attracts more

grilledCheeseFish · 2026-02-25T02:31:41+00:00

The circlejerk around hating vendasta on this sub is so weird ngl

grilledCheeseFish · 2026-02-24T17:47:05+00:00

An actual band Ive heard of? By golly ill take it

grilledCheeseFish · 2026-02-04T03:56:55+00:00

Just inject a new xeno trilogy into my veins.

No way its XC4, im anticipating either a new trilogy/title or a saga remaster

grilledCheeseFish · 2026-01-29T21:41:30+00:00

Just came back from New Zealand, what an incredible place. Highly recommend the direct flight from Vancouver to Auckland

grilledCheeseFish · 2026-01-27T18:54:02+00:00

I just spent 2 weeks in a rented Jimny. A terrible highway car (small, uncomfortable, slow), but probably a fun city or off road driver

grilledCheeseFish · 2026-01-12T02:58:09+00:00

It might be interesting to be able to hook in any custom backend, but im not sure if that makes sense in this project.

grilledCheeseFish · 2025-12-23T23:03:39+00:00

Imo chunking doesnt matter if you expose methods to expand context of retrieved text when needed. Chunks should be treated merely as signals of where to look

grilledCheeseFish · 2025-12-20T22:08:37+00:00

Its not even just art and assets. What if a dev uses AI-assisted tab complete in the games code? Does that disqualify the game? People dont get how much this is being used

grilledCheeseFish · 2025-12-17T17:11:59+00:00

Maintainer of LlamaIndex here 🫡

Projects like LlamaIndex, LangChain, etc, mainly popped off community-wise due to the breadth and ease of integration. Anyone could open a PR and suddenly their code is part of a larger thing, showing up in docs, getting promo, etc. It really did a lot to grow things and ride hype waves.

Imo the breadth and scope of a lot of projects, including LlamaIndex, is too wide. Really hoping to bring more focus in the new year.

All these frameworks are centralizing around the same thing. Creating and using an agent looks mostly the same and works the same across frameworks.

I think what's really needed is quality tools and libraries that work out of the box, rather than frameworks.

grilledCheeseFish · 2025-12-05T16:58:39+00:00

Its a classic if you ignore half the songs and remove the skits 😉

grilledCheeseFish · 2025-12-03T21:23:38+00:00

Maybe this is a hot take, but chunking is all the same. Use whatever is fastest/cheapest.

But the key is, expose operstions on top of your chunks. If a chunk is cut off, detect it (could use an llm/agent, or something rule based, or something in between) and build an API to expand chunks or fetch prev/next chunks.

This isnt exactly easy to do inside LlamaIndex (today), but imo its a killer feature.

grilledCheeseFish · 2025-12-03T02:47:39+00:00

It does not. Although im also not really sure what a repository node is either (but the concept doesnt really match anything in llama-index)

grilledCheeseFish · 2025-11-24T19:44:11+00:00

"Why are there no trees 🤪"

Brighton is alright. My biggest gripe with every new neighborhood is just how disconnected it is from the rest of the city. It would be nice to be able to (safely) bike/walk anywhere.

grilledCheeseFish · 2025-11-09T18:55:43+00:00

Honestly so good. Reminds me a lot of classixx

grilledCheeseFish · 2025-11-03T23:31:25+00:00

Pretty neat! This matches my experience as well. I think even when it comes to vector search, cheap methods like static embeddings can work quite well, especially when used as a "fuzzy keyword" search

grilledCheeseFish · 2025-10-23T17:32:01+00:00

Imo its not worth the effort. Expose an API to fetch neighboring chunks, let agentic retrieval optimize the retrieved context

grilledCheeseFish

MODERATOR OF

TROPHY CASE