MurphyA/hacker-news huggingface dataset:
Show HN: MCPlexor – MCP multiplexer that cuts agent context usage by 95%
by arustagi | 2026-02-09 07:17:15+00:00
I built MCPlexor to solve a token waste problem I kept running into with MCP-based agents.

The Problem:
MCP (Model Context Protocol) is great for giving LLMs access to external tools. But if you connect multiple servers (GitHub, Linear, Postgres, Slack), you end up with 40-50k tokens of tool definitions injected into every request – before the agent even does anything.

On a 200k context model, that's 25% gone. On smaller models, it's worse. And most runs only use 1-2 tools.

The Solution:
MCPlexor sits between your agent and your MCP servers. Instead of loading all tool definitions upfront:

Agent asks for a capability ("create an issue")
MCPlexor routes to the right server using semantic matching
Only relevant tools get exposed
Result: ~500 tokens overhead instead of ~20k.

Technical Details:
- Written in Go, single binary, no runtime deps
- Supports both stdio and HTTP transports
- Stores credentials in OS keychain (macOS Keychain, Windows Credential Manager, Linux keyring via zalando/go-keyring)
- Works with Claude Desktop, Cursor, Augment Code, or any MCP-compatible client

The routing logic can run entirely locally using Ollama. No API calls, no cost, works offline.

Business Model (for transparency):
- Local/Ollama users: completely free
- Cloud tier (on waitlist): we run inference on efficient small models instead of Opus/Pro, pass on savings, take a margin
The bet is that routing is a narrow enough task that a fine-tuned 7B model does it as well as a frontier model. Early testing suggests this works.

CLI uploads: https://github.com/arustagi101/mcplexor
Install: `curl -fsSL https://mcplexor.com/install.sh | bash`
Happy to answer questions about the architecture, the routing approach, or anything else.
by awesome_dude | 2026-02-09 07:18:06+00:00
I'm not sure if you are being serious, but

Number of commits don’t tell anything about the value and quality of those commits. Please don’t measure yourself with this poor metric.

— Jaana Dogan ヤナ ドガン (@rakyll) February 26, 2019

Number of IOS apps isn't much of a metric either to be honest, but sure we can pretend that that's a result of the AI revolution...
by davedx | 2026-02-09 07:18:08+00:00
I'm still building https://techposts.eu - the Hacker News for Europe!

Some stats so far:

- 200 users

- 378 startup jobs

- 500+ posts

- 2800+ funding rounds

- 1700+ startup companies

- 5000+ investors

The next part of the project is Tech Posts Intel: a lead gen tool using statistical methods to predict which companies should have a funding round coming soon. I'm hoping to soft launch it this week.

I'd love to hear anyone's feedback on the website. Advice on how to get inbound links in 2026 would also be greatly appreciated!
by franga2000 | 2026-02-09 07:18:38+00:00
People definitely care about things that a more open platform brings you, but today's open platforms have really bad downsides. The thing is, those downsides are artificial. They were manufactured by the corporations that prefer to be in control of our devices. It's not the natural state of things.

I often get asked by friends and family "can I get rid of annoyance X" or "can I have feature Y" on their Android phones, usually because they see that I've done it on my phone [0]. The answer is always "yes, I can set that up for you, but this will take an hour, I need to wipe all your data and a bunch of your apps will stop working".

There is no reason it should be like that. That was a choice by the manufacturers. They developed these DRM features and actively market them to developers - to the point where I can't submit an update to my little bus app without getting a prompt to add SafetyNet to it. They even somehow concinced pentesters to put "no cert pinning, root check and remote attestation" into their reports, so bank and government apps are the worst offenders.

It's not like people decided they prefer closed to open. They prefer working to non-working. And open platforms were broken intentionally by the developers of the closed ones.

It's like saying Americans all love their cars and simply decided not to use public transport. No, their public transport was crippled to the point of uselessness and their neighbourhoods were built in a way that makes public transport unfeasible. Cars work for them and trains don't. This was not their choice and it's painfully obvious when you see them go literally anywhere else on the planet and be amazed at how great trains are.

[0] Things like: global adblock, removing bloatware, floating windows or splitsceen, miracast, slide for brightness/volume, modded apps, lockscreen gestures, app instances, working shared clipboard, NFC UID emulation, automatic tethering, audio EQ...
Show HN: MemeOS – The Ultimate Meme Operating System (iOS)
by moimaere | 2026-02-09 07:18:41+00:00
Hi HN, the creator of MemeOS here.

I built MemeOS because I was tired of the current state of meme generators. Most existing mobile apps / websites are either riddled with ads, have outdated templates, or are just simple image captioners without real editing power.

MemeOS is a native iOS app designed to treat memes as a serious medium. I wanted to build something that feels like a "pro" tool but for something as fun as memes.

Key Features:

AI Meme Maker: I built an agentic workflow using Supabase Vector Search. You can describe a situation or feeling, and my "Meme Maker Agent" (yes, I really built a meme agent!) will find relevant templates and suggest captions.

Professional Editor: Layer-based editing, and precise text controls. It feels more like a mini-Photoshop for memes than a simple captioner.

Meme Lore: Every meme has an origin story. I use AI to research and write the history ("lore") of each template, so you know exactly where it came from and how to use it correctly.

The Tech Stack:

Backend: Supabase (PostgreSQL).

Frontend: SwiftUI (100% native iOS).

AI/Search: Supabase Vector for semantic search of templates and RAG for the "Lore" generation.

Edge Functions: Deno runtime for the heavy lifting of AI coordination.

The app is free to try. I monetize through a separate subscription for power users (AI tools, premium assets, watermark removal), but the detailed Meme Lore and the core editor are accessible to everyone.

You can check it out here:

Website: https://memeos.app

Download (iOS): https://memeos.app/download

I’d love to hear your feedback on the editing feel. I am actively tweaking the vector search weights, so any examples where the AI "missed" the vibe would be super helpful!
by yoyohello13 | 2026-02-09 07:19:11+00:00
I think LLMs the technology is very cool and l’m frankly amazed at what it can do. What I’m ‘anti’ about is pushing the entire economy all in on LLM tech. The accelerationist take of ‘just keep going as fast as possible and it will work out, trust me bro’ is the most unhinged dangerous shit I’ve ever heard and unfortunately seems to be the default worldview of those in charge of the money. I’m not sure where all the AI tools will end up, but I am willing to bet big that the average person is not going to be better off 10 years from now. The direction the world is going scares the shit out of me and the usages of AI by bad actors is not helping assuage that fear.

Honestly? I think if we as a society could trust our leaders (government and industry) to not be total dirtbags the resistance to AI would be much lower.

Like imagine if the message was “hey, this will lead to unemployment, but we are going to make sure people can still feed their families during the transition, maybe look in to ways to support ubi.” Seems like a much more palatable narrative than, “fuck you pleb! go retrain as a plumber or die in a ditch. I’ll be on my private island counting the money I made from destroying your livelihood.”
by emporas | 2026-02-09 07:19:11+00:00
Vibe coding is entertainment. Nothing wrong about entertainment, but when totally clueless people connect to their bank account, or control their devices with vibe coded programs, someone will be entertained for sure.

Large language models and small language models are very strong for solving problems, when the problem is narrow enough.

They are above human average for solving almost any narrow problem, independent of time, but when time is a factor, let's say less than a minute, they are better than experts.

An OS kernel is exactly a problem, that everyone prefers to be solved as correct as possible, even if arriving at the solution takes longer.

The author mentions stability and correctness of CCC, these are properties of Rust and not of vibe coding. Still impressive feat of claude code though.

Ironically, if they populated the repo first with objects, functions and methods with just todo! bodies, be sure the architecture compiles and it is sane, and only then let the agent fill the bodies with implementations most features would work correctly.

I am writing a program to do exactly that for Rust, but even then, how the user/programmer would know beforehand how many architectural details to specify using todo!, to be sure that the problem the agent tries to solve is narrow enough? That's impossible to know! If the problem is not narrow enough, then the implementation is gonna be a mess.
by jorvi | 2026-02-09 07:19:28+00:00
High-end chips should be more of a EU concerted effort rather than every country for itself.

The problem is that unlike Airbus, which (highly inefficiently) can be made in multiple countries, you can't really spread out parts of a fab that way. The most you can do is fab machines + chips + chip packaging. Netherlands already has fab machines and in packaging there isn't a high margin.

That leaves chips, and you can be sure that whoever gets the fabs, the other EU countries will throw a shit fit and demand counter investments to compensate. And on top of that there is also regional animosity. So even if it makes logical sense to pop the fab down in the middle of the blue banana, it won't make political sense because France and all of South and East EU will be angry about "the rich getting richer".
by fc417fc802 | 2026-02-09 07:20:36+00:00
A PKI is any scheme that involves third parties (ie infrastructure) to validate the mapping of key to identity. The US DoD runs a massive PKI. Web of trust (incl. PGP) is debatably a form of PKI. DID is a PKI specification. You can set up an internal PKI for use with ssh. The list goes on.
by kleiba | 2026-02-09 07:20:44+00:00
I just read that whole thread and I think the author made the mistake of submitting a 13k loc PR, but other than that - while he gets downvoted to hell on every comment - he's actually acting professionally and politely.

I wouldn't call this a fiasco, it reads to me more that being able to create huge amounts of code - whether the end result works well or not - breaks the traditional model of open source. Small contributions can be verified and the merrit-vs-maintenance-effort can at least be assessed somewhat more realistically.

I have no bones in the "vibe coding sucks" vs "vibe coding rocks" discussion and I reading that thread as an outsider. I cannot help but find the PR author's attitude absolutely okay while the compiler folks are very defensive. I do agree with them that submitting a huge PR request without prior discussion cannot be the way forward. But that's almost orthogonal to the question of whether AI-generated code is or is not of value.

If I were the author, I would probably take my 13k loc proof-of-concept implementation and chop it down into bite-size steps that are easy to digest, and try to get them to get integrated into the compiler successively, with being totally upfront about what the final goal is. You'd need to be ready to accept criticism and requests for change, but it should not be too hard to have your AI of choice incorporate these into your code base.

I think the main mistake of the author was not to use vibe coding, it was to dream up his own personal ideal of a huge feature, and then go ahead and single-handedly implement the whole thing without involving anyone from the actual compiler project. You cannot blame the maintainers for not being crazy about accepting such a huge blob.
by aurareturn | 2026-02-09 07:21:02+00:00
I don't think this is how pro and anti conversation goes.

I think the pro would tell you that if GCC developers could leverage Opus 4.6, they'd be more productive.

The anti would tell you that it doesn't help with productivity, it makes us less versed in the code base.

I think the CCC project was just a demonstration on what Opus can do now autonomously. 99.9% of software projects out there aren't building something as complex as a Linux compiler.
by onion2k | 2026-02-09 07:21:08+00:00
however it's something entirely different for that output to be good and maintainable

People aren't prompting LLMs to write good, maintainable code though. They're assuming that because we've made a collective assumption that good, maintainable code is the goal then it must also be the goal of an LLM too. That isn't true. LLMs don't care about our goals. They are solving problems in a probabilistic way based on the content of their training data, context, and prompting. Presumably if you take all the code in the world and throw it in mixer what comes out is not our Platonic ideal of the best possible code, but actually something more like a Lovecraftian horror that happens to get the right output. This is quite positive because it shows that with better prompting+context+training we might actually be able to guide an LLM to know what good and bad looks like (based on the fact that we know). The future is looking great.

However, we also need to be aware that 'good, maintainable code' is often not what we think is the ideal output of a developer. In businesses everywhere the goal is 'whatever works right now, and to hell with maintainability'. When a business is 3 months from failing spending time to write good code that you can continue to work on in 10 years feels like wasted effort. So really, for most code that's written, it doesn't actually need to be good or maintainable. It just needs to work. And if you look at the code that a lot of businesses are running, it doesn't. LLMs are a step forward in just getting stuff to work in the first place.

If we can move to 'bug free' using AI, at the unit level, then AI is useful. Above individual units of code, like logic, architecture, security, etc things still have to come from the developer because AI can't have the context of a complete application yet. When that's ready then we can tackle 'tech debt free' because almost all tech debt lives at that higher level. I don't think we'll get there for a long time.
by p2hari | 2026-02-09 07:21:20+00:00
I am working on a e-commerce and pos solution. More like shopify/saleor/woocommerce etc. with ready to start for small businesses selling physical and online and in-store products and services.

The platform itself is built on elysiajs/bun and tanstack and is completely hosted in EU and the payment processor is a EU based entity and we have an ISV partnership.
by shiroiuma | 2026-02-09 07:21:47+00:00
Exactly right.

On top of this, they're going to have mandatory bed position assignments. Just like you currently can't choose which desk you're going to sit at, and have to put up with the most annoying person on the team as your deskmate, in the near future you're going to have to cuddle with him/her at night too, whether you like it or not, and regardless of his/her bad hygiene, just because your manager decided to stick you two together.
by AlexDenisov | 2026-02-09 07:21:49+00:00
Building a tool for finding scientific papers behind real-world OSS projects: https://papergrep.dev/

This is a follow up to an idea I had years ago https://news.ycombinator.com/item?id=13022649, which is now semi-automated (with lots of manual curation as the last step).

The biggest challenges:

- how to organize all this info in a nice way

- where to find more time to read all the gems I've found so far :)

UPD: formatting
Show HN: Invox – Open-source self-hosted invoicing for freelancers
by maksim-pokhiliy | 2026-02-09 07:22:16+00:00
I built Invox because every invoicing tool I tried was either bloated, expensive, or wanted to own my data.

It does what freelancers actually need: create invoices, send them via email, track when clients open them, set up recurring billing, and get automated payment reminders. No accounting features, no payment processor lock-in.

Tech stack: Next.js 16 (App Router), MUI 7, Prisma, PostgreSQL, Zod 4, React Query. Feature-Sliced Design architecture. TypeScript strict mode throughout.

Self-host with Docker in 3 commands:

git clone https://github.com/maksim-pokhiliy/invox.git
cd invox
docker compose up

Live demo: https://invox-green.vercel.app

MIT licensed. Looking for feedback on the UX and what features freelancers actually want next.
by jeffreygoesto | 2026-02-09 07:23:03+00:00
All these people that built GCC and evolved the language did not have the end result in their training set. They invented it. They extrapolated from earlier experiences and knowledge, LLMs only ever accidentally stumble into "between unknown manifolds" when the temperature is high enough, they interpolate with noise (in so many senses). The people building GCC together did not only solve a to technical problem. They solved a social one, agreeing on what they wanted to build, for what and why. LLMs are merely copying these decisions.
by andyjohnson0 | 2026-02-09 07:23:15+00:00
I recall a few posts when he moved out there. Based on a quick look at my archived IP emails:

https://seclists.org/interesting-people/2018/Jun/35

https://seclists.org/interesting-people/2018/Jul/2

https://seclists.org/interesting-people/2018/Jul/84
by jeeeb | 2026-02-09 07:24:10+00:00
Japan giving a security guarantee to Taiwan would be major news!

In reality no such thing happened and one YouTube video of a handful of protestors doesn’t make it so.

What she did say is that a Chinese attack on Taiwan _could_ clearly become an existential threat to Japan. Note that key word _could_

Which… of course it could!

Japan hosts multiple US military bases. If it developed into an armed conflict between the US and China then it’s exceedingly likely that Japan would be attacked. Think Chinese missiles aimed
At Yokosuka, just south of Tokyo.

Not only that but Japan and China have multiple territorial disputes. It’s not hard to imagine China deciding to go all in and settle those as well.
by smt88 | 2026-02-09 07:24:12+00:00
> After all, the appeal of biggest cities was always, at least to me, the availability of white collar, highly paid jobs

You are definitely unusual.

Since remote work became more common because of Covid, remote workers have moved within the same city or moved to smaller cities. Only 4% relocated to rural areas[1].

Cities are appealing to most people because they have entertainment, variety, walkability, and many other benefits that rural places don't provide. The urbanization of America isn't only because work has changed, but because people generally prefer urban or suburban living over rural living.

1. https://pmc.ncbi.nlm.nih.gov/articles/PMC11551397/
by locknitpicker | 2026-02-09 07:26:00+00:00
> We need no AI for this one: If I could only maintain code I wrote, I'd have to work alone.

I think you missed the whole point. This is not about you understanding a particular change. This is about the person behind the code change not understanding the software they are tasked to maintain. It's a kin to the discussion about the fundamental differences between script kiddies vs hackers.

With LLMs and coding agents, there is a clear pressure to turn developers into prompt kiddies: someone who is able to deliver results when the problem is bounded, but is fundamentally unable to understand what he did or the whole system being used.

This is not about sudden onsets of incompetence. This is about a radical change in workflows that no longer favor or allow research to familiarize with projects. You no longer need to pick through a directory tree to know where things are, or nagivate through code to check where a function is called or what component is related to which component. Having to manually open a file to read or write to it represents a learning moment that allows you to recall and understand how and why things are done. With LLMs you don't even understand what is there.

Thus developers who lean heavily on LLMs don't get to learn what's happening. Everyone can treat the project as a black box, and focus on observable changes to the project's behavior.
by xeyownt | 2026-02-09 07:26:42+00:00
Funny how people only looks at the easy part, but not the cost part.

"I did it with AI" = "I did it with an army of CPU burning considerable resources and owned by a foreign company."

Give me an AI agent that I own and operate 100%, and the comparison will be fair. Otherwise it's not progress, but rather a theft at planetary scale.
by red75prime | 2026-02-09 07:27:19+00:00
Me: Top 0.02%[1] human-level intelligence? Sure. But we aren't there yet.

[1] There are around 8k programming languages that are used (or were used) in practice (that is, they were deemed better than existing ones in some aspects) and there are around 50 million programmers. I use it to estimate how many people can do something, which is objectively better than existing products.
by Animats | 2026-02-09 07:28:34+00:00
Including the AI, which generated it once and forgot.

This is going to be a big problem. How do people using Claude-like code generation systems do this? What artifacts other than the generated code are left behind for reuse when modifications are needed? Comments in the code? The entire history of the inputs and outputs to the LLM? Is there any record of the design?
by AngryData | 2026-02-09 07:28:42+00:00
I don't think people would care as much about AI reusing code or images or text so directly if people were allowed to do so too. The big problem I think comes in when AI is allowed to do things that humans can't. Right now if I publish a book that is 70% somebody else's book but slightly rehashed with certain key phrases and sentences or more as perfect copies, I would get sued and I would lose. Right now though if an AI does it not only is it unlikely to get litigated at all, but even if it does most of the time it will come down to "whoops AI did it, but neither the publisher nor the AI developer is individually responsible enough to recover any significant loses from."
by pcoch6 | 2026-02-09 07:29:18+00:00
I hardly write code anymore myself and am a heavy user of Claude Code.

One of the things I’m struggling to come to terms with is the “don’t commit code that you don’t understand” thing.

This makes sense, however it’s a thorn in my side that if I’m honest I’ve not been able to come up with a compelling answer to yet.

I agree with the sentiment. But in practice it only works for folks who have become domain experts.

My pain point is this - it’s fine to only review if you have put in the work by writing lots of code over their careers.

But, what’s the game plan in 10 years if we’re all reviewing code?

I know you learn from reviewing, but there’s no doubt that humans learn from writing code, failing, and rewriting.

So…this leaves me in a weird place. Do we move passively into a future where we don’t truely deeply understand the code anymore because we don’t write it? Where we leave it up to the AI to handle the lower level details and we implicitly trust it so we can focus on delivering value further up the chain? What happens to developers in 10-20 years?

I don’t know but I’m not so convinced that we’re going to be able to review AI code so well when we’ve lost the skill to write it ourselves.