I think you are missing the most important part - forgetting. The missing "memory" layers is consolidation, prioritization AND forgetting (what is not important).

Also not too sure about provenance and inspectability - it is part of memory. If the source is deemed 'important' it will survive forgetting. If not, then maybe not. And its ok. I am sure you dont know the exact source who told you that the capital of France is Paris. You forgot, and its no big deal.

Agree. We came to the same conclusion sometime last year. Now we solely focus on a single threaded agent - and make them run longer in a focussed way.

You dont need a team of humans to write great code - one engineer with solitude and focus is all it takes.

Keep at it - there are a ton of things you can try which will help. Try to use reddit to see what other people are looking at.

If there is one thing I can recommend you - get the Wellue O2 Monitor. This wil montior your O2 saturation through the night - if the saturation is dropping, you know that there is an issue, irrespective of what the resmed cpap claims. The resmed cpap figures cant be trusted imo.

But once you know what the saturation levels are, you can try a LOT of things which might help. Different cpap masks, head of bed elevation, mouth tape, neck straps - what you end up using will depend on your condition. But imo - dont rely on doctors to diagnose and fix you - you will have to do it yourself. Fortunatately there is a ton of people who are trying things out in reddit and extremely unlikely that you have a conditoin which is not fixable.

Just keep at it and track it using the O2 ring and try out what works for you.

You should consider getting an Wellue O2 ring. This is something you can use to monitor your oxygen saturation throughout the night. Use it with the CPAP and also otherwise. If your oxygen saturation is better with CPAP - you know that it is working. You will eventually feel better.

The main thing about CPAP is that, and imo almost everyone gets wrong, is that you need to titrate it. CPAP is sold as an Automatic Pressure device, but in practice it doesnt work like that. You almost always need to set it just 1 number below and 1 above your required pressure - more like a fixed pressure device. And getting it working correctly - with all the mask combinations, leaking issues, pressure calliberation, supporting gear like mouth tapes and neck bands - can take months. It is incredibly hard - BUT - it is worth it. The best resource for me has been the reddit to get this right.

The key is to track your saturation everyday with all the small tweaks you make and the only way to do it is using something like the O2 ring.

The bigger problem with solutions like these is that most AI already know how to use grep and search really well because of their training. Any such new tool that you handle to the AI, takes away from the cognitive capability of the AI. Humans would normally 'learn' how to operate tools like this - but the learning in LLM's is frozen and they already with a very strong depth in existing tools like grep.

For example, an AI would already use linux commands like tree to traverse the code base. And again it already has good training in this.

The other problem is that it is easy to cook up examples which demonstrate the efficacy of tools like these - but actually proving that the cognitive deficit that such tools result it, is surmounted by their efficacy in long horizon runs. My first contact instinct is that this will result in a net negative 'deployable intelligence' over long horizon runs - make the agent perform worse than using existing tools.

Proving the opposite is a non-trivial problem - but maybe it might be something you want to take up.

I was of the same view - but then there is this other trend which is putting sync back in favor. And that is that agents are becoming faster. If they are faster - it makes sense to stick around and maintain your 'context' about the task and supervise in real time. The other thing which might keep sync in fashion is that LLM providers are cutting back on cheap tokens. So you have a bigger incentive to stick around and make sure that your agent is not going astray.

The only place I use async now is when I am stepping away and there are a bunch of longer tasks on my plate. So i kick them off and then get to review them when ever I login next. However I dont use this pattern all that much and even then I am not sure if the context switching whenever I get back is really worth it.

Unless the agents get more reliable on long horizon tasks, it seems that async will have limited utility. But can easily see this going into videos feeding the twitter ai launch hype train.

Not sure why you think Agentic coding is solved - it isnt imo, and exactly because of the same memory issues.

I looked into Saunas in detail sometime back as a replacement/complement to exercise. There is a lot of research out there which says Saunas are as beneficial - but at the end of it I reached a similar conclusion - exercise is just better understood, so no point experimenting when something can go wrong.

To clarify - we don't read user conversations - what I'm referring to is deploy volume (how many times OpenClaw gets spun up on our infra) and direct conversations I've had with people in my network who deployed OpenClaw independently

Congratulations on the launch !

We run upwards of a thousand sandboxes for coding agents - but these are all standard VM's that we buy off the shelf from Azure, GCP, Akamai and AWS. I am not sure why we should use this instead of the standard VM's? Pricing could be one part, but not sure if the other features resonate.

Forking is interesting, but I would need to know how it works and if it is in the blast radius of the agent execution. If we need to modify the agent to be cognizant of forking, then that is a complexity which could be very expensive to handle in terms of context. If not, then I am not sure what is the use for it.

Sandbox start time at 500ms is definitely interesting. But its something we already are on track to reproduce with a pooled batch of VM's. So not sure if that in itself is worth paying for the premium.

My two cents on the space is that agents are rapidly becoming more capable to just use the tooling developed for humans. All clouds provide a CLI which agents can already use to orchestrate - they should just use the VM's designed for humans through the CLI. Our agent can already 'login' to any VM on the cloud and use the shell exactly like a human would. No software harness is required for this capability. The agent working on a VM is indistinguishable from humans.