Answers
Your CLAUDE.md outgrew a page. What comes out of it?
The usual advice is to keep a CLAUDE.md under a page and trim it when it grows. Trimming treats size as the problem. The problem is that everything in the file governs every session, and nobody sees what goes in or approves it: an assistant's guess, a status line from March and a decision made in a meeting the reader never attended all carry the same weight as the build command. So what comes out is all of it. What still holds moves to Arroway, where a person approves it and the read picks it by task; what is stale or noise is deleted. The file can end up empty.
Last updated August 26, 2026
Why the short, true lines get no exception
The build command, the folder layout and the convention the code follows look like safe exceptions, because they are short and true today. They are also the lines an assistant can rewrite in passing with nobody reviewing the edit, and the lines nobody rereads once they stop being true. Whatever stays in the file stays out of anyone's sight. In Arroway the same fact is a memory with an author, a person who approved it and the condition that ends it — and it reaches every tool the team uses, not only the one that loads the file.
What is making it long
Everything with a person behind it. A decision about pricing or scope, a rule about what may be sent to a customer, the approach the team tried and abandoned, the convention agreed in a meeting by someone who does not commit code. New ones keep arriving, because decisions never stop being made, so the file grows in the one direction it cannot afford — and once it passes a page, the lines that matter most compete for attention with the lines that were merely never deleted.
Where it goes instead
Into Arroway: written by people and by the assistants they use, approved by a person before it governs anything, carrying the condition that ends it, and served by relevance to the task at hand rather than loaded whole. The size problem stops being a size problem, because a read selects. A file cannot select — it is all placed in front of the model, every time, and the only way to keep it small is to keep deleting things a person still needs.
What it looks like in practice
A team's context file reaches four pages. Someone trims it back to one, by length: the build commands stay because they are short, and the paragraph explaining why the team stopped using a library goes because it is long. Two weeks later an assistant proposes that library. The trim was done exactly as advised, and it removed the line that was doing the most work — and nothing in the file could have said which line that was: no author, no date, no approval.
Questions people ask about this
- So the CLAUDE.md is wrong?
- It is the wrong place for anything that has to hold. Whatever sits in it governs every session, and nobody sees what went in or approves it — the line an assistant added on its own, the status that went stale, the decision nobody remembers making. It also cannot say that a line was superseded, or reach a person who never opens the repository. Arroway's recommendation is to leave it empty and keep what holds in Arroway, where a person sees and approves each line.
- Can I not just split it into several files?
- You can, and it postpones the problem rather than solving it. More files means more text placed in front of the model, or a loading rule someone has to maintain — and neither touches the part that actually hurts: nothing in a file says which of two contradicting lines is in force today. Splitting organises the text. It does not give a decision an expiry, an author, or a person who approved it.
- What does the assistant read, then, and how do I know it arrived?
- It asks Arroway, at the start of the work. That read is ordered by the task and comes back saying what it delivered and what did not fit — so “did the assistant actually get our rules?” has an answer you can look at, which is something no file can offer about itself.
Where this is verifiable
Product documentation on this site (How it works, Install) and the sanctioned product spec in the repository. The guidance about keeping a context file short is publicly published practice; every property named here about a plain context file is one any versioned text file has — no expiry, no sanction step, no selection, no delivery receipt. This page makes no claim about the built-in memory of any AI product.
https://www.arroway.app/en/answers/context-file-outgrew-a-page