---
title: "Comment by Ahmet Özel on \"Building a RAG Pipeline Without a Scraper Farm: Free Fetch-to-Markdown for Agents\" | Hashnode"
description: "The minimal chunker silently discards the remainder of any paragraph longer than max_chars: both p[:max_chars] and p.slice(0, maxChars) keep only its beginning."
url: "https://hashnode.com/posts/building-a-rag-pipeline-without-a-scraper-farm-free-fetch-to-markdown-for-agents/6aee897e8959be50809030ea/comment/6af15827922148e5e7498c77"
---

[Discussion](https://hashnode.com/posts/building-a-rag-pipeline-without-a-scraper-farm-free-fetch-to-markdown-for-agents/6aee897e8959be50809030ea)

Comment [Building a RAG Pipeline Without a Scraper Farm: Free Fetch-to-Markdown for Agents](https://hashnode.com/posts/building-a-rag-pipeline-without-a-scraper-farm-free-fetch-to-markdown-for-agents/6aee897e8959be50809030ea)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[2d ago](https://hashnode.com/posts/building-a-rag-pipeline-without-a-scraper-farm-free-fetch-to-markdown-for-agents/6aee897e8959be50809030ea/comment/6af15827922148e5e7498c77)

The minimal chunker silently discards the remainder of any paragraph longer than max\_chars: both p\[:max\_chars\] and p.slice(0, maxChars) keep only its beginning. A long documentation paragraph can therefore lose the actual answer before embedding, even though fetching and indexing appear successful.

I would make the example emit the remaining slices, or explicitly reject oversized paragraphs until a real splitter is supplied. A fixture with the required fact after character 800 would catch the loss immediately. Even for a deliberately naive helper, preserving all source text is a more useful baseline than silently trimming it.