---
title: "Comment by Oglas AI on \"Day 03: Your repo does not fit in the context window. Now what?\" | Hashnode"
description: "Really useful breakdown, especially the point that measuring characters or using the wrong tokenizer can give a misleading picture of an AI agent’s actual cost."
url: "https://hashnode.com/posts/a-repo-does-not-fit-in-context/6acf2d667530ca888e78c002/comment/6acf652ab4fd765f1d1325b9"
---

[Discussion](https://hashnode.com/posts/a-repo-does-not-fit-in-context/6acf2d667530ca888e78c002)

Comment [Day 03: Your repo does not fit in the context window. Now what?](https://hashnode.com/posts/a-repo-does-not-fit-in-context/6acf2d667530ca888e78c002)

[Oglas AI](https://hashnode.com/@oglas-ai2026)

[Oct 14](https://hashnode.com/posts/a-repo-does-not-fit-in-context/6acf2d667530ca888e78c002/comment/6acf652ab4fd765f1d1325b9)

Really useful breakdown, especially the point that measuring characters or using the wrong tokenizer can give a misleading picture of an AI agent’s actual cost. I like how you turn an easily overlooked technical detail into a practical lesson about budgeting, context limits, and smarter system design. At Oglas AI, we believe building effective AI solutions means thinking beyond the model itself and paying attention to efficiency, reliability, and real world costs. Looking forward to the next part of this series!

[Harshavardhan Katkam](https://hashnode.com/@harshakatkam)

[Oct 14](https://hashnode.com/posts/a-repo-does-not-fit-in-context/6acf2d667530ca888e78c002/comment/6acf652ab4fd765f1d1325b9#reply-6acfc82321d79888bfc6fde6)

Thanks! The measured number surprised me too: on the free model I'm using, code came out at about 2.58 characters per token, well below the usual rule of thumb. That's why the ratio gets calibrated, not assumed. Next up, Day 04: making the model return structured output instead of prose I have to parse.