bstrama

Works on my PC.

Could you gimme the url that's failing?

Can't wait to see the next generation of LLMs after feeding it all of that hahaha

Created just a discord server for this, easier than manually people asking me for invite: https://discord.gg/maHCN2b5Nc

Nah, only thing is a group some dude created on reddit and called "YC P26 Waitlist". Although some people have their speculations, you won't find any concrete information. If you want me to invite you there, let me know.

my reddit: u/baderbc

idk, I only received that message via email. Guess they wouldn't want to brag about it.

Think they could be testing us, for how much progress we can do. Especially since its scale seems to be quite big, most likely at least a few hundreds of applications got that.

As for me I feel the AI fear. Just a few months ago, narrative that AI won't replace programmers, made a lot of sense, and still somewhat does.

But after spending a few weeks totally vibe coding my new project, which is technically advanced, which for sure would be very hard to do on my own, I felt the pressure of what happens in the future with my career.

The only thing keeping me sane is hope, that even if AI takes SE jobs, it makes us a potentially strong founder candidates, we know how to code, how the good architecture should look like and have amazing tool, to iterate very quickly. Although the fact that rapid development is not enough to succeed is another thing.

Not sure I’d call it spam. A cloud pivot would be a major shift in both architecture and audience, not necessarily means going closed source.

We're already seeing some "spin up OpenClaw VM with one click" solutions (I mean user friendly VPS wrappers).

Although I don't think OpenClaw will become cloud-native solution. Especially taken into account OpenClaw author's vision and how large the codebase become.

Not to mention such pivot would be impossible without deprecating skills (which are built specifically for current architecture)

Hi HN,

While building the execution runtime for our AI tool ecosystem (Gace), we originally planned to rely on local execution—similar to how OpenClaw handles things.

But the further we got, the more we realized that treating a user's laptop as a 24/7 background server for LLMs is an architectural anti-pattern. Two things killed it for us:

Latency: ReAct loops bouncing back and forth over home Wi-Fi ruin the UX.

Security: Running untrusted community scripts locally without absolute sandboxing is terrifying.

So we pivoted. We built a cloud sandbox using quickjs-emscripten that executes JS tools in strict isolates with 25ms cold starts. By putting the executor in the same data center as the LLM, the multi-step latency tax practically disappears. (For eventual local file access, we're building a dumb, permission-gated daemon rather than a heavy local execution engine).

I wrote down our technical reasoning on why we think the current "local-first" agent trend is structurally flawed. I'd love to hear your thoughts.

The core idea behind Gace AI was to treat AI plugins and tools like standard JS functions or packages, rather than the more heavyweight approach seen in MCP which requires a persistent server.

The biggest challenge was achieving this without the typical latency associated with spinning up new sandboxes. We eventually landed on using quickjs-emscripten, which utilizes a WASM-compiled QuickJS engine to execute JS scripts in a secure, isolated environment.

By going this route, we managed to achieve 0.025s cold starts for new sandboxes. This allows us to offer a free hosting and a hot reload experience where you can host and call tools instantly without worrying about the infrastructure overhead.