So where its fair to say enterprise users buy safety, if he's referring to his own product I would offer the following.

He's in the AI tool space i.e. a better rag. So you're selling to AI developers and developers nearly always go open source first.

If they can't find an open source solution or if they don't even look, they prefer to build it themselves.

For this kind of product most enterprise buyers won't understand its benefits, you have to get the developers interested first.

And finally, in this market, you are 1 prompt away from someone cloning your whole business and calling it openaxon or something like that.

It's a tough time to be a software startup.

A dizzying array of adverts and popups.

Developers won't pay for it. I'll pay for hosting begrudgingly and I pay for AI tokens and domain names and that's it.

And every Saas idea can now be copied with this prompt.

Build me an open source clone of -> https://your-saas.com

You need a moat these days more than ever.

The authors stack left me thinking about how will he re-start the app if it crashes, versioning, containers, infra as code.

I've seen these articles before... the Ruby on Rails guys had the same idea and built https://kamal-deploy.org/

Which starts to look more and more like K3s as time goes on.

I was thinking more of

Running multiple websites. i.e. 1 application per namespace. Tooling i.e. k9s for looking at logs etc. Upgrading applications etc.

But, actually you can run Kubernetes and Postgres etc on a VPS.

See https://stack-cli.com/ where you can specify a Supabase style infra on a low cost VPS on top of K3s.

My bet would be OpenAPI specs. The model will think its calling a cli but we intercept the tool call and proxy it with the oauth credentials.

There are some implementations already out there in open web ui and bionic gpt.

Its usually pretty easy to get one to call you and they can give you an idea about the market.

Taking something that is basically a lonely depressing activity and putting a social aspect around it.

Well done.

I actually use it from the web app not the cli. So far I've run over 100 codex sessions a great percentage of which I turned in to pull requests.

I kick off codex for 1 or more tasks and then review the code later. So they run in the background while I do other things. Occasionally I need to re-prompt if I don't like the results.

If I like the code I create a PR and test it locally. I would say 90% of my PR's are AI generated (with human in the loop).

Since using codex, I very rarely create hand written PR's.

What are the advantages vs having a mono repo per team?

1. Some LLMs support function calling. That means they are given a list of tools with descriptions of those tools.

2. Rather than answering your question in one go, the LLM can say it wants to call a function.

3. Your client (developer tool etc) will call that function and pass the results to the LLM.

4. The LLM will continue and either complete the conversation or call more tools (functions)

5. MCP is gaining traction as a standard way of adding tools/functions to LLMs.

GitMCP

I haven't looked too deeply but I can guess.

1. Will have a bunch of API endpoints that the LLM can call to look at your code. probably stuff like, get_file, get_folder etc.

2. When you ask the LLM for example "Tell me how to add observability to the code", the LLM can make calls to get the code and start to look at it.

3. The LLM can keep on making calls to GitMCP until it has enough context to answer the question.

Hope this helps.

The US will need a lot of factories to employ 10s of millions of workers.I also imagine new factories will employ less workers due to increased automation.

I'm interested to see how this plays out.

So effectively you would be paying people to work in manufacturing even though it's no longer necessary.

You may as well pay a basic income instead.

There are various ways to validate libraries but it's best to assume an exploit gets through.

So then, you should be looking at your deployment, i.e. locking down containers, network policies, least privileges etc etc.

Try to reduce the blast radius to zero.