<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Context Window on No Semicolons</title><link>https://nosemicolons.com/tags/context-window/</link><description>Recent content in Context Window on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 11 Jun 2026 12:04:17 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/context-window/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Breaking Point: How to Handle Projects That Exceed Token Limits</title><link>https://nosemicolons.com/posts/ai-code-generation-breaking-point-token-limits/</link><pubDate>Thu, 11 Jun 2026 12:04:17 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-breaking-point-token-limits/</guid><description>&lt;p>You know that sinking feeling when you&amp;rsquo;re deep into a conversation with Claude or ChatGPT about your codebase, and suddenly it starts giving you advice that completely ignores the architecture decisions you discussed twenty messages ago? Welcome to the AI token limits breaking point – that invisible wall where your AI coding assistant essentially develops amnesia about your project.&lt;/p>
&lt;p>I hit this wall hard last month while working on a microservices platform with about 50,000 lines of code. One moment my AI pair was suggesting perfect database schema changes that aligned with our existing patterns, the next it was recommending solutions that would break half our service contracts. The context window had filled up, older conversations got pushed out, and suddenly my AI assistant was flying blind.&lt;/p></description></item></channel></rss>