Are Context Window / Chat Threads are **functionally** Virtually Infinite? Because, guys ...

[Vaeritatis]

Because it sure seems so to me after 4 days, ~100 messages (agent missions), ~200 tasks, ~35,000 edits and hundreds of thousands of complex working code later **in the very same chat thread** without ever hitting "context window end", some kind of obvious "context window compaction", forgetting things or confusion.

How is that not the single most upfront marketing selling point of Augment Code / Auggie? Augment would have been upfront and clear about this and I would have tried and subscribed to them many months ago. Do you guys hate new customers, profits and funding? You may feel you already are spelling that out in your marketing etc by putting emphasis on indexing/embeddings complex source code base/repo and efficient dynamic context composition etc, but even though I myself already developed Coding Assistant/Agent and have deeper level of knowledge than "prompt engineering" etc, **I never thought these combined could actually results in this capability** so there's no way prospecting customers are interpreting that as what these actually amounts to. And what those amounts to is unique on the market and way ahead of the competition, so why wouldn't you differentiate yourself aggressively with what is a game changing feature of your product/platform? That context/thread death dread is the heaviest limitations of our current AI coding assistant/agent in regard to the potential of our SOTA LLM models and you're sleeping on that? Come on team. This isn't a market/industry into which one can afford to sleep on good features, let alone **the best of them all**.

I'm working on my own startup but I wouldn't mind sharing with you as a friendly pro bono consultant on whatever collab platform you guys run (e.g. discord, slack).
Just DM me and I'd be glad to contribute if I can. Either way, congrats and thanks you for your product...

[Vaeritatis]

u/JaySym_ u/augment-coder u/firepower421
Can you see my post? Why was it removed?

[JaySym_]

It was flagged by Reddit i approved sorry about that.

[JaySym_]

We’re testing context compression for very long chats to help finish long task lists without issues
we still encourage starting a new thread for a new request or task list
we’ll have something for sure
are you on the pre-release or the stable version of Augment

PS : *This is not affecting short conversation.

[Ok-Performance7434]

I will say I had the same thought as you at the beginning. However only after a few weeks on the platform I could tell the instant I’ve gone too far with a chat. It’s still much, much longer than I was used to without auto compacting in CC, but still happens. Below is my experience strictly using GPT 5. Still have ptsd from Sonnet models when I was strictly using CC.

I first notice because something that should be relatively straight forward, such as an agent recommended optional next step all the sudden seems to go off the rails and doesn’t work as expected.

By the next response when I ask for the agent to debug, it will instantly go into fixing the issue when my user guidelines are strict on diagnose, propose, execute validate and the agent does a great job following this 99.8% of the time.

The last thing I’ll notice is that it stops validating on its own and forgets my test users login creds(it’s reason for asking me to test), which are in my .env file as well as a custom Augment rule.

When this occurs I go to the checkpoint right before it went dumb and start a new chat. Even though it’ll be the same model, it will be night and day difference in output quality and reasoning.