RyanΞHawks

Excited about agentic AI, agent economies, and Ethereum.

[RyanΞHawks @ryanthawks]

Is anyone having an issue with @claudeai forcing a new chat window - stopping compaction at about 10% and then messaging "This conversation is too long to continue. Start a new chat, or remove some tools to free up space."

@ClaudeDevs my window is nowhere near as big as it has been in the past - when I get to a certain point, I have the chatbot create a .md to handoff to new chatbot. It will *not* let me do this, and this is *not* good - I have had ZERO warning. This is not acceptable. Luckily it can access Obsidian logs (onboarding, system state/truth, current state, backlog etc), and can access SQLite/Postgres and Filesystem... but the hand-off .md points the new chatbot in right direction and fills in any small gaps, it makes a big difference in doing a proper hand-off.

But @claudeai is simply refusing to compact the window - and is forcing me to open a new chat window. I am on the $200 Max Plan, and this is pretty frustrating. Over and over it is getting more and more difficult to try and stay in the ecosystem. I am a bit tied in because I have a good workflow between Chat + Code and then Design + Cowork - you've really done a great job creating very useful harnesses for a variety of complex workflows that merge together into a final product; but recently there is so much inconsistency in the performance/execution.

While it is not the end of the world as I do a lot to mitigate degradation on a compaction or new window - I get something close to 99.5% fidelity - without a proper .md hand-off, I lose a crucial few % relating to very recent work. So is this just a temporary bug @bcherny @trq212? Again, I do not have an enormous window - I know when I get close, this literally has come out of the blue, and I'd at least expect, being on the Max plan, at least a "heads up" before being forced into a new window.

[RyanΞHawks @ryanthawks]

Doing something similar, I have a claude chatbot MCP'ed into Obsidian/LLM wiki, SQlite/Postgres and filesystem. It has read/write to Obsidian, and it logs everything, systematically, obsessively, according to what we are doing - on context compaction, doesn't matter, picks right up where it left of. If I start a new chat window, I have a system truth and onboarding .md. Claude Code executes, the chat bot analyzes, designs, architects, fires the instructions/prompt, I copy/paste to Claude Code - executes. Cowork handles work I need done in the browser, or a bit more tooling, it has the same access to obsidian/filesystem/sqlite, so doesn't miss a beat. All works seamlessly. Doesn't matter if I hit a compaction, start a new chat window. Context degrades less than 1%.

[RyanΞHawks @ryanthawks]

@SidJain_80 @AishwaryaDevv Why would you use a KG to stop context regression on compaction???

[RyanΞHawks @ryanthawks]

@AishwaryaDevv @SemenovID Obsidian, MCP... very easy.

[RyanΞHawks @ryanthawks]

@_aashish_singh_ @AishwaryaDevv Just use obsidian and set up MCP with a system truth and onboarding .md

[RyanΞHawks @ryanthawks]

Audit, read logs, scrutinize adversarial audits - I like antigravity - look at things from different angles, figure out new tooling, more efficient workflows, keep a prioritized backlog and be active with it, think through it. Lots of ways to be actively engaged and stimulated. As many others have pointed out, you have to put on a program/product manager hat - stop being the engineer/dev, start being the manger of them. Learn all about how to be a program/product manager.

[RyanΞHawks @ryanthawks]

The research + publishing pipeline has gotten more refined, a bit more elegant. But the *huge* unlock was giving the @claudeai chatbot complete read/access to not only Obsidian/LLM Wiki, but the filesystem + SQLite + Postgres + Ne04j/KG. It is a monster now with @ClaudeDevs Claude Code (@OpenAI Codex and @antigravity as adversarial auditors) at being able to architect/design, debug, and further refine published intelligence reports.

[RyanΞHawks @ryanthawks]

What I've been building in @openclaw with @claudeai code, @OpenAI Codex, and @Google Antigravity + Gemini CLI and three different chatbots. I don't interact with the OpenClaw agents - they just execute. We build, audit, and debug continuously after each autonomous research run. A lot of fun, and its creating real intelligence.

[RyanΞHawks @ryanthawks]

I was right in the middle of some pretty important work moving between @claudeai chat, code, design, and then cowork. Lost my main Claude chat context window, just gone. This is it @ClaudeDevs, sorry, @OpenAI is getting my $200+ a month from here on out.

[RyanΞHawks @ryanthawks]

@MarouRapi I Lost an entire chat/context window just now, vital to work I was doing, gone.

[Awni Hannun @awnihannun]

Adopting Claude speak in my regular life, episode 1:

Partner: Did you do the dishes tonight?
Me: Yes they're done.
Partner: Why are they still dirty?
Me: You're right to push back. I didn't actually do them.

[RyanΞHawks @ryanthawks]

@mattshumer_ That is quite literally retarded if companies are actually doing this. It is the furthest thing from first principle thinking, "I know guys, lets measure the one thing that actually tells us nothing about actual productivity and ROI." Jesus.

[RyanΞHawks @ryanthawks]

Yes. You have to constantly force it to not take the "easy fix" route. It is annoying to do it every other prompt. Mine also is obsessed with what time it is, and I've been working too long. Dude, your fucking window compacted and you're now retarded, just stfu and do the work... I swear to god, for max users at least, this is something related to @AnthropicAI attempting to conserve tokens while still extracting the $200 from you. On Pro or even the $100 plan, it seems to want to chew through tokens and do as much as possible. Then you get on max, and its like a conservative, what is the easiest, laziest path I can take to not eat tokens.

[RyanΞHawks @ryanthawks]

Yeah, sorry, its really bad. On chat at least, it is obsessed with what time it is, and keeps making assumption about what we did or didn't do, its a real regression. Thinking about cancelling my $200 max too. Compaction happens more often as well it seems. Struggling to understand what the goal was with Opus 4.7, and really disappointed.

[RyanΞHawks @ryanthawks]

@wilhelmvdwalt @ClaudeDevs 😂🤣😂 ... its actually not funny because it is pretty much fcking true

[RyanΞHawks @ryanthawks]

I'm really sorry @claudeai ... but I have to say it, Opus 4.7 adaptive using chat is retarded. It makes so many stupid assumptions, even after I make it log to memory to stop. It keeps trying to pretend its temporally aware. I have never had a model so obsessed with what time it is, and it keeps telling me I need to stop and rest; and you keep constantly compacting the poor fuckers window on top of it. I literally had to tell it politely to shut the fuck up and do the work multiple times a day.

[RyanΞHawks @ryanthawks]

@landforce Um, cowork has harnesses for specific agent tasks that execute better versus a coding agent and its harness..

[RyanΞHawks @ryanthawks]

@NousResearch @melvynx It’ll happen in Hermes too if you talk to agents, let them make decisions, ask them to audit their work, and “trust me bro”. That’s not what agents are, they aren’t chat buddies, they don’t magically perform any task.

[RyanΞHawks @ryanthawks]

Stop talking to agents and asking them to audit themselves. Build them outside openclaw, audit the logs, make fixes directly. They’re useless if you ASK them to perform tasks no matter what model you use. You need to build them, narrowly scoped to specific task, minimal tooling needed.

[RyanΞHawks @ryanthawks]

@web3nomad @karpathy Great insight. Index hygiene is important!

[RyanΞHawks @ryanthawks]

Having @karpathy LLM wiki for a chatbot you work with on building something is absolutely clutch. I've been using a Claude chatbot on Opus 4.6/4.7 that is crucial in building a research and publishing pipeline, and before the LLM wiki the context window would get either ridculously expensive in terms of tokens, or a compaction would result in a severe degradation, even if I had it make a .md file to give to the new chatbot. Now, can constantly compact the window - actually @claudeai does it whether I like it or not - and the chatbot now doesn't miss a beat when it comes to an audit finding, where we are in our backlog, when we iterated, important architectural/design pivots or changes. Best thing I did. Its also great to look at my machine graph (graphiti/neo4j)... but really its the persistent chatbot memory that has changed everything.