loading
Loading.loading
Loading.Not with a bigger context window. That's short-term working space, refilled every session and flat. Agents stay reliable over a long project when you give them a durable source of truth they navigate on demand: the current, canonical answer about the codebase, served cheaply, instead of re-reading the repo each time. For long-running work you layer memory by job, facts and decisions, with a path to promote a repeated decision into a standing rule.
The window is capped, re-filled each session, and has no notion of a fact versus a one-off versus a standing rule. Over a long project an agent has to recall a decision from months ago without re-reading everything — a storage-and-retrieval problem the window doesn't solve.
Most agent failures come from losing the thread of your codebase and re-deriving it wrong. Serving the canonical answer on demand (this is trovex's job) keeps them fast and correct instead of expensive and confidently wrong.
For an agent that holds a relationship over months, memory is an architecture: a rules store for what's always true, a decision journal for why, a history log — and a deliberate path to promote a repeated decision into a rule.
or have us build it — same capability, the other door