In a previous life I used to model insurance payouts for residential mortgages. The average we used was within 7 years.

I tend to agree with the rest of the commenters that the most likely outcome is that harnesses will include features like this. I had a slightly different issue and that was 'project-level memory' that i can use across models or harnesses (chat, claude code, etc).

for a while i used Obsidian but it was not very good with hosted tools like claude.ai then i moved to a combination of Linear and Notion. Still using Linear but Notion ended up being a royal pain: it is built for humans not agents. It is block based and when multiple agents use it there is a lot of corruption in the process.

I wanted a markdown only, notion built for agents that can work with multiple agents so built one: markbase.cloud

feel free to try and use it. i think it's useful

This.^ I realized this first when moving a design spec from Claude chat to Claude Code and panicked. I literally had to build something like Notion but for agents to act as a portable memory between all cloud and local models and agents. But honestly it paid off!

If you are interested you can try it out at markbase.cloud (disclaimer and all that). I am not charging for it.

We run a "context" repository that enables us to transition pretty seamlessly from model to model (usually codex to claude and back). It has skills / plugins / connectors / tooling in relatively malleable MD files. That's what I see as the future. Rather than exporting IDE settings we'll just carry our markdown to the next best tool.

It's hedging a bet at this point, but that's why people say there's no moat. If the tools are properly used + maintained, there should be no reason we can't use a new provider even next week (maybe with a little tweaking).

that's an interesting approach and something i also considered (using git to avoid conflicts). one thing i needed was a "database" (basically a folder of markdowns) with a fixed schema so i can let the agents record their decisions in (for example when the code conflicts with product design spec). this combined with search has been a real lifesaver.

this is how it works: https://help.markbase.cloud/humans/collections/overview

Believe it or not, after writing this comment I was doing some more reading on the task. I'm planning to reorganize our context repo after finding this paper (it argues that AI generated context files can stunt the performance of models):

https://arxiv.org/abs/2602.11988

For what it's worth, if you were considering building context out.

Very interesting. Anecdotally I’ve found the opposite to be the case. But I’m very interested in understanding more. Thanks for sharing

I just want to say thank you for all your good work. We are very proud to have been a small part of your efforts at Cloud 66. Keep up the good work.

sometimes I feel we need to hire someone just to catch up with google breaking changes.

When you signup for Railway, they have uncommon way of making sure you have read and understood their T&C regarding abuse of their systems, including crypto mining, etc.

My guess is that many are abusing their free tier, causing them trouble with their service providers.

I take no joy in seeing Railway take a hit like this, even as a competitor, but free compute attracts all sorts of strange users. We've been there and decided early on to avoid free compute even it costs us our top of the funnel.

That is a good hypothesis but then you’d imagine they could combine it with registered clients to keep crawlers accountable.

‘Keeping crawlers accountable’ sounds like whack-a-mole.

At least to me because benign crawling is likely to be a tiny subset of all crawling activity that is not done by google, etc.

Overall, it's an interesting idea. Although it's Google and it's packed, it's going to be packed with Gemini and Google AI and whatnot. My problem is not the AI, nor is it that it's an undefined territory for what a laptop use case is. My problem is Google's attention span. Google is notoriously bad at paying attention to any product for more than 18 months. I'm not going to spend money on buying a piece of hardware where it's going to be totally irrelevant from a manufacturing point of view in 18 months and be left high and dry holding the bag.

It's turned into a bizarre place. Today I asked the same question on /r/meta and my question was immediately removed without explanation. I tried to message the mods and got bounced with a "you cannot send a message to that user"

It was much better years ago.

We certainly see a lot more automated security vulnerability reports coming our way that are clearly generated by AI and in bulk.

As a SOC 2 compliant company we have to record each one and respond to them as per our policies.

Our solution was to use AI to combat that as the first line of defence and filtering. Eventually we turned this system into a separate business (fortworx.com) because it seems a lot of other companies have the same problem.