<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Arch-Router: Aligning LLM Routing with Human Preferences · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2506.16655/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2506.16655/feed.xml" rel="self" type="application/rss+xml" /><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — mentioned by honorable_coder</title><link>https://news.ycombinator.com/item?id=45337202</link><guid isPermaLink="false">urn:hackerpapers:mention:2506.16655:45337202</guid><pubDate>Mon, 22 Sep 2025 18:03:21 GMT</pubDate><description>&lt;p&gt;Today we’re shipping a major update to ArchGW (an edge and service proxy for agents [1]): a unified router that supports three strategies for directing traffic to LLMs — from explicit model names, to semantic aliases, to dynamic preference-aligned routing. Here’s how each works on its own, and how they come together. Preference-aligned routing decouples task detection (e.g., code generation, image editing, Q&amp;amp;A) from LLM assignment. This approach captures the preferences developers establish when testing and evaluating LLMs on their domain-specific workflows and tasks. So, rather than relying…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — HN submission</title><link>https://news.ycombinator.com/item?id=45324991</link><guid isPermaLink="false">urn:hackerpapers:submission:2506.16655:45324991</guid><pubDate>Sun, 21 Sep 2025 17:45:54 GMT</pubDate><description>&lt;p&gt;Show HN: Model-literals, model-aliases, and preference-aligned routing for LLMs&lt;/p&gt;&lt;p&gt;Today we’re shipping a major update to ArchGW (an edge and service proxy for agents [1]): a unified router that supports three strategies for directing traffic to LLMs — from explicit model names, to semantic aliases, to dynamic preference-aligned routing. Here’s how each works on its own, and how they come together. Preference-aligned routing decouples task detection (e.g., code generation, image editing, Q&amp;amp;A) from LLM assignment. This approach captures the preferences developers establish when testing and evaluating LLMs on their domain-specific workflows and tasks. So, rather than relying…&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — HN submission</title><link>https://news.ycombinator.com/item?id=44845147</link><guid isPermaLink="false">urn:hackerpapers:submission:2506.16655:44845147</guid><pubDate>Sat, 09 Aug 2025 09:21:40 GMT</pubDate><description>&lt;p&gt;Arch-Router: Aligning LLM Routing with Human Preferences&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — HN submission</title><link>https://news.ycombinator.com/item?id=44774539</link><guid isPermaLink="false">urn:hackerpapers:submission:2506.16655:44774539</guid><pubDate>Sun, 03 Aug 2025 06:32:04 GMT</pubDate><description>&lt;p&gt;Show HN: Arch-Router – Aligning LLM Routing with Human Preferences&lt;/p&gt;&lt;p&gt;Hi HN — we&amp;#x27;re the team behind ArchGW [1], an edge and service proxy for agents written in Rust, and we just recently published our research on LLM Routing: https://arxiv.org/abs/2506.16655 As teams integrate multiple LLMs - each with different strengths, styles, or cost/latency profiles — routing the right prompt to the right model becomes a critical part of the application design. But it&amp;#x27;s still an open problem. Most routing systems fall into two camps: - Embedding-based routers use intent classifiers — label a prompt as “support,” “SQL,” or “math,” then route to a matching model. This works…&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — HN submission</title><link>https://news.ycombinator.com/item?id=44771836</link><guid isPermaLink="false">urn:hackerpapers:submission:2506.16655:44771836</guid><pubDate>Sat, 02 Aug 2025 21:42:16 GMT</pubDate><description>&lt;p&gt;Arch-Router: Aligning LLM Routing with Human Preferences&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;9 points; 2 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — HN submission</title><link>https://news.ycombinator.com/item?id=44650696</link><guid isPermaLink="false">urn:hackerpapers:submission:2506.16655:44650696</guid><pubDate>Tue, 22 Jul 2025 17:52:01 GMT</pubDate><description>&lt;p&gt;Show HN: RouteGPT – model routing on ChatGPT aligned to user preferences&lt;/p&gt;&lt;p&gt;Hey HN I had a personal itch to scratch, and thought that it might be useful to others: If you are a ChatGPT pro user like me, you are probably tired of pedaling to the model selector drop down to pick a model, prompt that model and then repeat that cycle all over again. So I built RouteGPT to end that pedaling. RouteGPT is a Chrome extension for chatgpt.com that automatically selects the right OpenAI model for your prompt based on preferences you define. For example: “creative novel writing, story ideas, imaginative prose” → GPT-4o, or “critical analysis, deep insights, and market research ”…&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — mentioned by honorable_coder</title><link>https://news.ycombinator.com/item?id=44601319</link><guid isPermaLink="false">urn:hackerpapers:mention:2506.16655:44601319</guid><pubDate>Fri, 18 Jul 2025 04:50:41 GMT</pubDate><description>&lt;p&gt;Hi HN — we&amp;#x27;re the team behind Arch (an open-source edge and service proxy for agents)[1], and today we&amp;#x27;re releasing Arch-Router (https://huggingface.co/katanemo/Arch-Router-1.5B), a 1.5B LLM router model designed to align to user-defined preferences, not public benchmarks and leader boards. As teams integrate multiple LLMs - each with different strengths, styles, or cost/latency profiles — routing the right prompt to the right model becomes a critical part of the application design. But it&amp;#x27;s still an open problem. Most routing systems fall into two camps: - Embedding-based routers use intent…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — HN submission</title><link>https://news.ycombinator.com/item?id=44597819</link><guid isPermaLink="false">urn:hackerpapers:submission:2506.16655:44597819</guid><pubDate>Thu, 17 Jul 2025 20:29:12 GMT</pubDate><description>&lt;p&gt;Show HN: 1.5B LLM routing model that aligns to preferences, not leaderboards&lt;/p&gt;&lt;p&gt;Hi HN — we&amp;#x27;re the team behind Arch (an open-source edge and service proxy for agents)[1], and today we&amp;#x27;re releasing Arch-Router (https://huggingface.co/katanemo/Arch-Router-1.5B), a 1.5B LLM router model designed to align to user-defined preferences, not public benchmarks and leader boards. As teams integrate multiple LLMs - each with different strengths, styles, or cost/latency profiles — routing the right prompt to the right model becomes a critical part of the application design. But it&amp;#x27;s still an open problem. Most routing systems fall into two camps: - Embedding-based routers use intent…&lt;/p&gt;&lt;p&gt;4 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — mentioned by honorable_coder</title><link>https://news.ycombinator.com/item?id=44573623</link><guid isPermaLink="false">urn:hackerpapers:mention:2506.16655:44573623</guid><pubDate>Tue, 15 Jul 2025 17:24:05 GMT</pubDate><description>&lt;p&gt;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&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — mentioned by honorable_coder</title><link>https://news.ycombinator.com/item?id=44566142</link><guid isPermaLink="false">urn:hackerpapers:mention:2506.16655:44566142</guid><pubDate>Mon, 14 Jul 2025 22:40:21 GMT</pubDate><description>&lt;p&gt;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 understanding of a single file id want to use a fast model that doesn&amp;#x27;t cost me an arm and a leg. Recent research on preference-aligned LLM routing here: https://arxiv.org/abs/2506.16655&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Arch-Router: Aligning LLM Routing with Human Preferences — HN submission</title><link>https://news.ycombinator.com/item?id=44436031</link><guid isPermaLink="false">urn:hackerpapers:submission:2506.16655:44436031</guid><pubDate>Tue, 01 Jul 2025 17:13:11 GMT</pubDate><description>&lt;p&gt;Show HN: Arch-Router – 1.5B model for LLM routing by preferences, not benchmarks&lt;/p&gt;&lt;p&gt;Hi HN — we&amp;#x27;re the team behind Arch (https://github.com/katanemo/archgw), an open-source proxy for LLMs written in Rust. Today we&amp;#x27;re releasing Arch-Router (https://huggingface.co/katanemo/Arch-Router-1.5B), a 1.5B router model for preference-based routing, now integrated into the proxy. As teams integrate multiple LLMs - each with different strengths, styles, or cost/latency profiles — routing the right prompt to the right model becomes a critical part of the application design. But it&amp;#x27;s still an open problem. Most routing systems fall into two camps: - Embedding-based routers use intent…&lt;/p&gt;&lt;p&gt;66 points; 15 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2506.16655/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
