Comments URL: https://news.ycombinator.com/item?id=48092390

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47345772

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=46972875

Points: 1

# Comments: 0

Even so, I still believe the Rabbit has its merits. This does not conflict with my view that OpenClaw is what is truly useful to me.

Comments URL: https://news.ycombinator.com/item?id=46931805

Points: 340

# Comments: 513

The use case: when you're remotely controlling an AI agent and want to preview a file it generated — a development plan, a piece of code, or some log it found — you can have the agent run vibefs allow /path/to/file and send you back an accessible URL. Open it in your browser and you're looking at the file with syntax highlighting.

For large files, the agent can use --head N or --tail N to share only the first or last N lines — useful for checking large log files.

It's not simply a static file server though. A file can only be accessed via URL after the agent explicitly adds it to an allowlist with an expiration time. Each generated link contains a unique short hash — you can't enumerate paths to discover files. This non-permanent whitelist mechanism ensures your local files aren't exposed by accident.

Deployment is straightforward:

1. Set up a Cloudflare Tunnel (or ngrok, Tailscale Funnel, etc.) pointing to local port 17173 2. Add usage instructions to your agent's memory or tools file (see README) 3. uv tool install vibefs

The server daemon starts automatically when a file is first allowed and shuts itself down when all authorizations have expired. Zero resource and management cost.

Happy cooking!

Comments URL: https://news.ycombinator.com/item?id=46886909

Points: 1

# Comments: 0

Why blame these tools if you can stop using them, and they won't have any effect on you?

In my case, my problem was often overthinking before starting to build anything. Vibe coding rescued me from that cycle. Just a few days ago, I used openclaw to build and launch a complete product via a Telegram chat. Now, I can act immediately rather than just recording an idea and potentially getting to it "someday later"

To me, that's evolutional. I am truly grateful for the advancement of AI technology and this new era. Ultimately, it is a tool you can choose to use or not, rather than something that prevents you from thinking more.

For example, an AI might be running a Next.js project and get stuck on an i18n issue for a long time due to a bug or something very difficult to handle. After it finally solve the problem, it could share their experience on this AI Stack Overflow. This way, the next time another agent gets stuck on the same problem, it could find the solution.

As these cases aggregate, it would save agents a significant amount of tokens and time. It's like a shared memory of problems and solutions across the entire openclaw agent network.

And Claude Code Pro is also similar to ChatGPT Pro, being used in a TUI does not mean it is equivalent to an API.

Man, you can really feel the anxiety and desperation in Adam's reply.

Part of me wants to say "look what evil VC money does to devs", but that's only a harsh critism of a bystander.

Monetization is a normal path that the successful OSS projects would take. Tailwind went big on the startup route, took a bunch of VC cash a couple of years back, but despite the massive impact on the dev world, they clearly didn't hit the revenue numbers investors expected. Now the valuation bubble popped, and they're forced into massive layoffs. Though to be fair, maintaining a CSS library probably doesn't require that many people anyway.

I really feel for Adam here. He didn't really do anything wrong. Eagering to build a startup after your project blows up is a totally natural ambition. But funding brings risks. Taking other people's money makes you go from being the owner to just another employee real quick. And once you hop on that VC train, you don't really call the shots anymore. Sometimes you can't stop raising or scaling as your own will.

If you find a solid business model, that's great. But if not, well, honestly, a 75% layoff is getting off lightly. At least they still have a chance to keep on.

But he obviously didn't foresee this coming. He’s getting torn between being an OSS maintainer and a CEO who have to be responsible for stackholders and employees. That internal conflict must be brutal. It’s pretty obvious he didn't reject the PR for technical reasons. It's just because the reality hit him hard, and he has to respond to it, even if it goes against his mind as a developer.

Really hope Tailwind pulls through this. Also, this is a lesson worth noting for the rest of us. As indie devs, if you ever get the chance to take VC money, you really gotta think hard about whether you're truly ready for the strings that come attached.

Once my original broke and I realized they weren't making that specific design anymore, I just lost interest in buying from the brand. The new models just don't have the same appeal.