HN user

angelmm

297 karma

Gamer and Curious. Endor (https://endor.dev) cofounder. Parallelize your coding agents with Rover: https://github.com/endorhq/rover [ my public key: https://keybase.io/angelmm; my proof: https://keybase.io/angelmm/sigs/yDw5G3Dmu0qFA8cJvU_fyohGEwvPxPCl3qOj8vKc-XM ]

Posts51
Comments85
View on HN
tuicr.dev 26d ago

Local and GitHub Code Review TUI

angelmm
3pts1
holaclaw.ai 1mo ago

Show HN: In-browser real LLM token counter and cost estimation

angelmm
3pts1
twitter.com 4mo ago

Maintain your E2E test suite with Claude

angelmm
2pts0
github.com 5mo ago

Open-source voice cloning app using Qwen3-TTS

angelmm
4pts0
capsule.endor.dev 5mo ago

Claude prefers JSON over Markdown

angelmm
2pts0
endor.dev 7mo ago

Rebuilding our documentation site using AI

angelmm
2pts0
pocket-id.org 8mo ago

A simple open-source OIDC provider that only support passkeys

angelmm
2pts0
endor.dev 9mo ago

Rover: Coding Agent Manager

angelmm
8pts4
svelte.dev 11mo ago

SvelteKit Experimental Remote Functions

angelmm
4pts0
nitpicks.ai 11mo ago

Nitpicks: Record a video and let an agent implement the code

angelmm
14pts1
endor.dev 1y ago

Install Postgres, MariaDB, and Redis as NPM dependencies

angelmm
5pts0
angel.kiwi 1y ago

Disappointed by Gemini CLI

angelmm
4pts0
endor.dev 1y ago

Endor: Dev Tools for AI Agents and Impatient Humans

angelmm
5pts0
vercel.com 1y ago

Spain continues blocking IP addresses, now affecting Vercel

angelmm
7pts0
news.ycombinator.com 1y ago

Show HN: Endor, run server software in your browser

angelmm
5pts2
news.ycombinator.com 2y ago

Ask HN: How are you using LLMs in your personal projects today?

angelmm
2pts1
github.com 2y ago

Lumos, an extension to run LLMs locally in the browser with Ollama

angelmm
1pts0
wasmlabs.dev 2y ago

A guide to run WebAssembly modules in Docker Desktop

angelmm
1pts0
wasmlabs.dev 2y ago

AI-powered applications with WASM Workers Server

angelmm
1pts0
wasmlabs.dev 3y ago

Compiling PHP to WebAssembly

angelmm
2pts0
wasmlabs.dev 3y ago

Develop Workers with Go for WASM Workers Server

angelmm
4pts0
github.com 3y ago

Cargo-deny: a cargo plugin for linting Rust project dependencies

angelmm
3pts0
wasmlabs.dev 3y ago

Lamp Stack, but make it WASM

angelmm
2pts0
wasmlabs.dev 3y ago

WebAssembly Language Runtimes March Update: Batteries-Included Version

angelmm
9pts0
wasmlabs.dev 3y ago

WASM Workers Server 1.0: adding support for Python and Ruby

angelmm
5pts1
angel.kiwi 3y ago

Side Effects Are Unavoidable

angelmm
1pts0
angel.kiwi 3y ago

Complexity Comes Alone

angelmm
1pts0
wasmlabs.dev 3y ago

Wasm Workers Server v0.6.0: static assets and environment variables

angelmm
1pts0
github.com 3y ago

Add Material Icons to Your Ruby on Rails App

angelmm
2pts1
github.com 3y ago

Run your first worker in WebAssembly in 1 minute

angelmm
2pts1

Hey, I'm Angel, one of the people behind HolaClaw. We recently had to optimize different prompts for local inference and understanding how much tokens the system and user prompts consume were quite important.

I found several token counters around, but most of them were using estimations. In this tool, all the calculations are real. The website loads the public tokenizer.json files from those models and encode them to count. Everything happens in your browser.

For models / families that don't publish their tokenizer, we had to do an estimation. If you are curious, it worked by compiling the tokenizers library from HuggingFace to Wasm (they already have a demo).

Hope you like it! We plan to add some extra visualizations and stats. Also, feel free to suggest any missing model.

Even though I'm not that familiar with the synth world, I always found it a really interesting field. Websites like this that helps me exploring and learning are amazing :)

This is why I uninstalled Cursor and moving to the terminal with Claude Code. I felt I had more control to reduce the noise from LLMs. Before, I noticed that some hours were just wasted looking at the model output and iterating.

Not sure if I improved using agents over time, or just having it in a separate window forces you to use them only when you need. Having it in the IDE seems the "natural" way to start something and now you are trapped in a conversation with the LLM.

Now, my setup is:

- VSCode (without copilot) / Helix

- Claude (active coding)

- Rover (background agent coding). Note I'm a Rover developer

And I feel more productive and less exhausted.

Also, Codex Cloud and similar services require you to give fully access to your repository, which might trigger some concerns. If you can run it locally, you still have the control, same development environment, and same permissions.

Vibe engineering 10 months ago

Hey! Angel from Endor / Rover :)

Thanks for your feedback! I faced this in the past. As you mentioned, monorepos are more common these days, but multi-repo is an established approach in many teams. The way I "solved" this situation was to move all the related projects into a single folder with a parent AGENTS.md file (CLAUDE.md, etc.). Then, I run Rover / Claude / Gemini on this folder.

However, this is not ideal. Due to the amount of code, it usually misses many things to do. We are currently exploring specific workflows for these use cases, trying to help agents to prepare a complete plan.

Another similar case we are working on is to support spawning the same task across different repositories. This would help teams to apply refactor or changes in different projects at the same time.

Totally. I think Zed has its own value proposition. That's why I never put them close to other editors like Cursor at the beginning.

Lately, I started putting it together due to all the AI excitement. People try it because of the AI capabilities to find an IDE that works for them.

I hope Zed continues providing new amazing features in all the areas.

Many companies are considering IDEs the way to reach developers. Atom started the trend of next generation IDEs and VSCode consolidated most of the market. With the AI raising, people are looking to get usage, gathering data, and positioning models. An IDE provides you all of that.

AI seems to be a way to engage happy users to try new things. Kiro joins a growing list of projects:

- Kiro (AWS)

- VSCode + Copilot (Microsoft)

- Windsurf (OpenAI tried to get it)

- Cursor

- Trae (Alibaba)

- Zed

- etc.

I put Zed in a separate category in the past. Now with assistants / agents, it's playing on the same space.

The market is a bit saturated and tools like Claude Code gave some flexibility and an alternative for users. I tried Cursor in the past, and now I'm back to Helix / VSCode + Claude Code.

This is the kind of introduction I was looking for! I'm currently learning a bit more about this instruction set, so that's perfect.

Also, there are so many great resources in the comments.

After ChatGPT was announced, I found many cool projects that simplifies how you integrate LLM capabilities into your services. However, I didn't find many of these in the vision ecosystem.

Getting started in AI + vision with just 3 commands is amazing! I will definitely try it for some personal projects with IP cameras.

Good stuff :)

I know other existing projects like this (GitHub profile generators), although I like the idea you can customize the template.

However, it requires quite effort to deploy this one as you need to setup different services for the DB, deployment, etc. Since the data is pushed based on a GitHub action, I'm wondering if it's possible to just build a static site based on it. In the end, we're storing "snapshots" of the data to query them later.

I'm curious how the status page is down too. Those pages are usually in a totally separated infrastructure.

Wasm Labs dev here :)

In mod_wasm, there are some differences with a pure CGI implementation. When Apache boots, it loads the configuration and initializes the WasmVM. When a new HTTP request arrives, the VM is ready so you don't need to initialize a different process to manage it.

You still need to process the request and pass the data to the Wasm module. This step is done via STDIN through the WebAssembly System Interface (WASI) implementation [0]. The same happens in the opposite direction, as the module returns the data via STDOUT.

So, the CGI pattern is still there, but it doesn't require new processes and all the code runs in a sandbox.

However this is not the only way you can run a Wasm module. In this specific case, we use CGI via WASI. In other cases, you may compile a module to fulfill a specific API, like ProxyWasm [1] to create HTTP filters for proxies like Envoy.

- [0] https://wasi.dev/

- [1] https://github.com/proxy-wasm/spec

(Wasm Labs dev :)) For me, this is the key point. The end goal is to limit the attack surface for future vulnerabilities. This is not something specific to Drupal or PHP, but an example about technologies / apps that can take advantage of Wasm.

Those are great questions! I believe Emscripten will be required for some cases as it provides more features for targeting a Web Browser. If WASI is the only requirement for a Wasm module, then there are three possible solutions:

- Use a library that provides the WASI bindings in a browser environments: there are some OSS projects that provides WASI bindings on top of browser technologies. For example, workers-wasi from Cloudflare [1]. It could be even another Wasm module that provides the implementation for the main one. I know the people from Loophole Labs are experimenting with virtual filesystems (VFS) [2].

- Browsers provides a WASI implementation: server-oriented runtimes like NodeJS are already providing these bindings (under a experimental flag). I shouldn't have stated that as a fact, as browsers may provide it or not. However, I saw in the past the Google Chrome team experimenting with WASI and the browser FileSystem API [3]. So, I think it may happen :)

- [1] https://github.com/cloudflare/workers-wasi

- [2] https://www.youtube.com/watch?v=46jZSXVxYPw

- [3] https://github.com/GoogleChromeLabs/wasi-fs-access

The main work behind this patch is to ensure that SQLite can compile to Wasm32-wasi. WASI doesn't offer all syscalls that SQLite may require, so it may require some conditional definitions and code to ensure it works properly. It doesn't mean that SQLite is part of WASI, but you can embed SQLite in a Wasm32-wasi module.

In the future, the WASI standard will include more and more features. This will allow SQLite to enable more internal features that are currently skipped due to the limitations on WASI.

(Wasm Labs team member here) SQLite is a pretty popular database and it's a critical dependency for many different applications. By compiling it to Wasm32-wasi, you can add it to any WebAssembly module.

This enables a new set of possibilities for Wasm and SQLite. For example, now you can run a full WordPress application in the browser [1][2] / server [3] using the same Wasm module. Note that for the browser these projects use Emscripten [4], but in the future the same Wasm32-wasi module will work. A teammate gave a lightning talk about SQLite and WASI at KubeCon EU [5].

In general, any environment that includes a wasm runtime can potentially run applications that uses SQLite under the hood. Before, it wasn't possible.

- [1] https://wordpress.wasmlabs.dev/

- [2] https://developer.wordpress.org/playground/demo/

- [3] https://wasmlabs.dev/articles/running-wordpress-with-mod-was...

- [4] https://emscripten.org/

- [5] https://www.youtube.com/watch?v=E7tWtgf9V2s