honorable_coder

6 ms·

31.
by honorable_coder 1y ago
Model: https://huggingface.co/katanemo/Arch-Router-1.5B Paper: https://arxiv.org/abs/2506.16655 Integrated experience via Arch: https://github.com/katanemo/archgw
32.
by honorable_coder 1y ago
Is model choice a core design consideration. Or will Kiro not let developers chose the underlying model? What if I want to set preferences for the underlying LLM for different usage scenarios? For example, for a quick and snappy understandi
33.
by honorable_coder 1y ago
MCP implementation is trivial - I agree. But A2A will require a mesh like structure. Meaning its not just about north/south traffic. It will be about east/west traffic as agents coordinate with each other. That communication and c
34.
by honorable_coder 1y ago
Its a core dependency for rate limiting, traffic shaping, fail over detection. Its cluster subsystem is super convenient for local LLM calls too. We'll write up a blog on the lessons because there were many. For example, for intelligen
35.
by honorable_coder 1y ago
This ^
36.
by honorable_coder 1y ago
There are a few critical differences. archgw is designed as a data plane for agents - handling and processing ingress and egress (prompt) traffic to/from agents. Unlike frameworks or libraries, it runs as a single process that includes
37.
by honorable_coder 1y ago
We’re using proxy-wasm and compiling to wasm32-wasip1, then mounting the .wasm binaries into Envoy as HTTP filters via envoy.filters.http.wasm. The line you're referring to: vm_config: runtime: "envoy.wasm.runtime.v8" cod
38.
by honorable_coder 1y ago
What’s missing right now are our guides showing how well ArchGW integrates with existing frameworks and tools. But the core idea is simple: it offloads low-level responsibilities—like routing, safety, and observability—that frameworks like
39.
Show HN: ArchGW – An intelligent edge and service proxy for agents(github.com)
118 points by honorable_coder 1y ago|15 comments