每日 Show HN

Upvote0

2026年6月4日 的 Show HN

34 篇
235

Uruky (EU-based Kagi alternative) now has Image Search and URL Rewrites #

uruky.com faviconuruky.com
240 評論8:56 AM在 HN 查看
You can get a 2h free trial by solving a proof-of-work captcha when topping up your account for the first time.

If you'd like to learn more, an independent interview was posted a couple of weeks ago [1], and the FAQ [2] has a lot of information as well.

For the source code sharing, we've talked with lawyers and are inclined to no longer require the NDA/NCC for privacy reasons shared with us before (signing requires identification), but instead use a source-available permissive license that doesn't allow competition, like PolyForm Shield [3] (we do still have about 6 months before finalising a decision, here).

This does come with a lot more risks for us (it's harder to track down if someone publishes the code or uses it against the license), but given we've already passed 100 monthly active accounts, we're feeling more confident it's an acceptable risk.

The plan is to give logged in accounts (who are 12 months old or more) a way to download a ZIP of the current code base that's in the server.

Obviously there's no easy way to prove that's the case, but we're open to ideas/suggestions if someone here has them.

[1]: https://theprivacydad.com/interview-with-the-engineer-of-uru...

[2]: https://uruky.com/faq

[3]: https://polyformproject.org/licenses/shield/1.0.0

104

Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud #

boxes.dev faviconboxes.dev
79 評論2:38 PM在 HN 查看
Hi HN, we’re Nick and Drew, and we’re building boxes.dev – the first cloud-only agentic dev environment (ADE) that gives every Codex and Claude Code agent its own cloud computer.

We’re two engineers who previously built Gem (co-founder/CTO and first hire), and we spent the last year coding almost exclusively using Codex and Claude Code. It’s been a huge change to how we code, and it’s been exhilarating seeing the models keep getting better – but we eventually realized that developing on localhost was holding us back:

- Git worktrees are clunky to set up and use for parallelizing work - It’s 2026, but somehow everyone is still walking around with laptops cracked open or SSHing into mac minis in their garage so their agents don’t stop working. - Mobile is treated like an afterthought even though coding is just texting now We started hitting resource constraints when multiple parallel agents test their own work by running the full app locally. - We tried different products, but couldn’t find any that solved all of our pain points – so we pivoted and decided to just build the ADE we wanted for ourselves.

Boxes.dev is a desktop and mobile app that lets you run Claude Code, Codex (using your subscription!), and the full dev environment for whatever you’re building, all on remote compute. It’s similar to Conductor or the Codex desktop app, except everything is in the cloud.

We use coding agents to scan your local dev setup and port it to the cloud. Then every Claude Code/Codex thread starts from a snapshot of the full setup, with its own filesystem and compute. No more git worktrees, no more cracked-open laptops, and your coding agents can actually test their work end-to-end because they can run your full app in isolation.

We’ve mirrored the Claude Code and Codex UX to feel natural to power users, and also have a fully-featured mobile app (no handoffs or remote control), plus scheduled automations and a Slack integration.

We’re obviously biased, but we’ve been building boxes.dev with boxes.dev for months and it’s honestly been a gamechanger. It’s hard to go back once you realize how much localhost has been limiting you; based on early feedback from beta testers, we’re increasingly sure that cloud is the future of agentic coding.

We’d love for you to experience it yourselves! Would appreciate any feedback – and happy to answer any questions on this thread.

93

Formally verified polygon intersection – Opus 4.8 oneshots, prev failed #

github.com favicongithub.com
21 評論10:06 PM在 HN 查看
To my knowledge, this is the first formally verified implementation of an intersection algorithm for polygons.

The experience of working with AI agents on this project changed a lot with recent model releases, as I describe in the readme. Opus 4.8 is able to provide algorithm implementation with formal proof in one shot, whereas previous models required me to provide proof strategies in multiple steps.

Trust in the correctness comes entirely from the Lean checker and human review of a small specification, not from the LLM.

Also check out the web demo built around the verified core linked in the readme: https://schildep.github.io/verified-polygon-intersection/. It supports multipolygons including holes, self intersections, and overlapping edges.

63

Free animated icon library for Vue #

respeak-io.github.io faviconrespeak-io.github.io
18 評論8:07 AM在 HN 查看
Hi everyone!

Tim here, maintainer of the lucide-motion-vue library. I build this as a way to use nice animated icons in my webapps. We were already on lucide, and found animate-ui animated icons as a great collection, unfortunately React only or made to be used with shadcn.

So I ported the library to Vue, and combined it with another library (lucide-animated.com). As both libraries dont share the same animations and/or icons, this creates the largest animated icons library for vue that can be used from one source.

Additionally, I've made several quality of live changes to make it easier to use the icons: - drop-in replacement for lucide icons, or use a seperate namespace if you want - several animation variants - easy to be used standalone or in buttons - several animation triggers - comprehensive overview, playground and docs page, comes with llms.txt to be used by agents

Finally, the repo also contains a "forge". With this, you can

a) take any icon from the lucide library, or have ai suggest some b) autogenerate animations for these icons c) add them to the library with one click

We'll use the forge over time to hopefully create animated variants for all of lucides icons, if these icons are useful to be animated.

Looking forward to hear your feedback Cheers!

48

Cost.dev (YC W21) – making agents cost-aware and 79% cheaper to call #

cost.dev faviconcost.dev
29 評論11:30 AM在 HN 查看
We launched Infracost on HN five years ago (https://news.ycombinator.com/item?id=26064588) where our CLI generated cost estimates for infra-as-code, e.g. "this Terraform PR adds $400/mo". The idea was to shift cloud costs (FinOps) left, so engineers get visibility of costs before deployment and make better decisions.

Earlier this year we started seeing agent traffic in our logs and it looked like coding agents were calling our CLI. But that CLI wasn't designed with coding agents in mind. We went down a philosophical rabbit hole to see if a CLI is even needed anymore given that Claude, Copilot et al. already follow best practices. Ultimately we decided to create a new CLI from the ground up with coding agents in mind for two reasons:1. We optimized the CLI for agent callers and cut Claude's output token usage by up to 79% and API cost by up to 67% versus a bare-Claude baseline. We wrote a blog documenting our lessons on optimizing user token usage when designing a CLI, e.g. using predicate flags so the agent doesn't compose jq | python | wc pipelines, output format that strips JSON's redundant field names. The blog is here: https://www.infracost.io/resources/blog/we-cut-claude-s-toke.... With cloud costs, precision matters. Telling a coding agent "make this Terraform cost-optimized" can be expensive and lossy. You burn tokens loading code and policy context into every conversation. Your agent could make up a price and you wouldn't know because it's difficult to verify that across the ~10M price points that AWS, Azure and Google have. The CLI runs static analysis on the code, uses the latest prices from cloud vendors, and passes that context to the coding agent.So that's what we're launching today - Cost.dev:- It runs locally. Your code never leaves your machine, you get a fast feedback loop, and you're not burning API calls per character when you want to fetch prices.- The CLI does the deterministic work. Fetching price points, scanning the code, validating fixes. The coding agent does the natural-language part. You don't have to trust the LLM to remember the rules, and can verify it called the right CLI command.- It provides a consistent rule layer across every tool you use. Get cost estimates in your IDE and your coding agent with a single install. We support Claude Code, GitHub Copilot, Cursor, Windsurf, OpenAI Codex, Gemini CLI, as well as IDEs like VS Code and JetBrainsBefore we keep building more in that direction, I want to sanity-check with HN: is "agents writing IaC in prod" actually a thing yet, or am I betting on a future that's still a year out? I know software developers are using coding agents heavily, but are platform/infra folks doing that for prod too? Also, if you have any feedback on Cost.dev, I'd love to hear it.

21

Hitoku Draft – Context aware local assistant #

hitoku.me faviconhitoku.me
8 評論5:48 PM在 HN 查看
Hi guys.

I have been working on Hitoku Draft, an open-source, voice-first AI assistant that runs entirely locally. I posted about it already, and now it has also transcription with voice editing. Looking for feedback, as I found that outside tech circles other people still do not use this tech much.

It's context-aware, in the sense that it reads your screen, documents, and active app to understand what you're working on. You can ask about PDFs, reply to emails, create calendar events, use web search, editing text, all by voice.

You can download a compiled version for free with the code HITOKUHN2026 https://hitoku.me/draft/ (base price is 5 dollars)

It supports Gemma 4 and Qwen 3.5 for text generation, plus multiple STT backends (Parakeet, Qwen3-ASR).

Examples: - Gemma4 in action, https://www.youtube.com/watch?v=OgfI-3YjEVU - query a pdf document, https://www.youtube.com/watch?v=ggaDhut7FnU - reply to email, https://www.youtube.com/watch?v=QFnHXMBp1gA - and the usual voice dictation (with optional polishing)

I currently use it a lot with Claude Code and Logseq. Now with some friends we are also building a new cross-platform version. The goal is on the long run to have AI interactive local models serving people and professionals.

9

Hydron – Hardware-aware coding agent #

hydron.sh faviconhydron.sh
7 評論1:06 PM在 HN 查看
Hi HN, this is Prashant from H2Loop. Embedded engineers that we work with were annoyed that generic AI tools hallucinated register addresses, generated code for peripherals that don't exist on the chip and mixed up timer quirks between similar platforms like STM32F4 and F7. The code looks clean but it just won't boot. This made them go back to the datasheet every time. So we built Hydron, an AI tool that writes datasheet-grounded code for your hardware.

Demo: Hydron setting up sleep-mode CPU logging for an onboard temp sensor on an STM32U385 - https://boot.hydron.sh/zzzDemo

First, we've pre-indexed 580+ platforms and peripherals. Most of what you'd use in a robotics, UAV, or IoT build: common dev platforms like STM32, ESP32, RP2040, AM6 families, plus the IMUs, GNSS modules, motor drivers, and baros that ship around them. Ask about a peripheral, the answer comes from our KG and the actual datasheet.

Second, you can bring your own context and share it with your team. Hydron indexes PDFs up to 5000 pages, plus a whole host of various file types and even ZIPs of full C/C++/Python codebases up to 250MB. One engineer indexes the HW, BSPs, and datasheet pack once. Anyone else can reference it from their own Hydron agent.

Third, HW-SW development happens in your editor or terminal. Agentic serial monitor is live today. GDB integration, and an AI log reader land in the next two weeks.

Up next, we're focused on closing the hardware-software loop. We're building more HIL debugging capabilities, deeper target awareness, and support for additional platforms. If you work on embedded SW we'd love your feedback on where today's tools fall short and what you'd like to see next.

Install: VS Code extension - https://marketplace.visualstudio.com/items?itemName=H2Loop.h... CLI mac/linux -> curl -fsSL https://get.hydron.sh/cli/install.sh | bash. CLI windows -> irm https://get.hydron.sh/cli/install.ps1 | iex

More at http://boot.hydron.sh/HN. 200 free credits, 50% off on paid plans, one-step signup. Me and u/ajithhyd will be in the thread all day.

9

Chatcode – Remote Control for Claude Code and Codex #

chatcode.dev faviconchatcode.dev
14 評論10:35 AM在 HN 查看
Hey HN,

what I wanted to build here is a proper universal layer for persisted agentic sessions, that could be seamlessly interacted both via web and a messenger (Telegram). I really like what's done so far and would be nice to hear some feedback from you.

The interesting thing is that I started to use Chatcode during its development as soon it was possible, so used this tool to build itself.

I know that there could be trust/privacy concerns, because it relies on a gateway that you need to install on your machine in order to work, but: 1. You can use it on any machine, just have some test VPS for that 2. I really believe you will love it as soon as it fits your needs! And it's free to start BTW.

Anyways, looking forward to your questions/suggestions.

7

I embedded 685M public texts in 32 minutes (on 8x A100, Rust, TensorRT) #

github.com favicongithub.com
0 評論3:23 PM在 HN 查看
Quick note on how it works and how I've done my batch embedding engine IgniteMS.

The whole thing runs as one process using Rust, reading input, tokenizing, packing batches, keeping the queue full. TensorRT handles inference. Python is only as a wrapper.

I built it this way because when you use more than couple of GPUs, the GPUs stop being the problem. CPU cannot feed them fast enough. One A100 can go through batches faster than Python can tokenize and feed, so the GPU just sits there idle waiting for work. Most of my time went into optimizing this. At 8 GPUs that was basically the entire challenge.

On cost. I ran the big 2B messages job on a spot p4d instance (8x A100 40GB). After filtering and dedupping I got 685M raw texts. With my new engine the whole production run finishes in about half an hour. Previously I used on-demand for these jobs, now switched to spots. If AWS reclaims the box, I just rerun it. It's roughly $7 for half-an-hour run. And at least right now spots are easier to get than on-demand.

Open warning: it's batch only and NVIDIA only. You can use it both as a docker image and native. I used some optimizations for my production run. With default settings you can expect to see ~250K msg/sec if you run the benchmark script on your p4d box. https://github.com/Artain-AI/ignite-ms/blob/main/BENCHMARKIN...

v1.1.0 added TensorRT 11 and 60 models, 23 tested on 1x and 4x A100.

Happy to share details.

7

an AI that settles small couple arguments #

thepiece.app faviconthepiece.app
3 評論1:16 AM在 HN 查看
Nisrine and I have been working in the same company for many years (she's Head of Product, I am CPTO) and we have done great things for our employer(s) all along. But we always wondered if we could launch our own app – after all, we know the process of it all, we just "never had the time".

The idea started from a random conversation, after Nisrine told me a personal story about she had a stupid little fight with her partner, and after 3 or 4 back-and-forths on each side, she decided she was right. Of course, he decided HE was. But he was not sure, so he asked chatGPT... And lost :)

We were making fun of him but then we thought, wait: everybody fights for stupid little things. It would be great if someone impartial, neutral, with no bias, could move the needle in one direction. Not render a verdict like in a Roman Forum but just shows you where (both of) you are right or wrong, and then makes the person who is more in the wrong apologise. Yeah, an AI :)

Why apologise? One, because it's the best way to bring back peace to any relationship. Two, because it's hard to let go, put your ego on the side and accept that, "yeah, it's not worth fighting or sulking, sorry". And three... because it's so cool to see the other one bow and lose the argument :) Come on, don't pretend this is not thrilling to win an argument!

So we built this app, called Piece (sounds like Peace, it's the peace of offering to bring back peace – the logo is an olive branch). The app comes with different tones: witty, theatrical, sarcastic and counsellor (if you want to go deeper in the analysis). The principle is very simple: you record yourself, your partner records their version, you get an analysis of each side's good and weak points, then a verdict.

The app stores everything locally, no personal data shared anywhere (except the ephemeral transcript). And the two partners need to use one phone only: that brings them closer already. And from there, you can imagine all the features you want: dashboard with analytics (who has the biggest ego? how many times do you fight?), sharing on social media for "funny" humiliation, karma points, music generation of your fights etc. This app does not replace the couple therapy apps, of course. We are more malicious, this is more about a gamified experience for the day to day arguments.

While building the app (Claude + Claude Design, app is in Flutter if you're interested), we were amazed by how many hilarious sentences the AI engine came up with. We were not expecting something that smart, to be honest, and that was what we liked about this side project: every test was a laugh! – ok, maybe not when Nisrine introduced regressions in the code: she argues that she did not but we asked Piece, and I won...

We had good feedback from regular users so we recently decided to launch for a bigger public. The app is on the iOS and Android stores (look for "Piece, relationships"), works in English and French for now. Free to start, we'll surely implement credits when we grow our audience. Get it from here: https://thepiece.app

Happy to expand on any of this here if you are interested

6

Recursi – self-improving LLM-connected coding environment #

recursi.dev faviconrecursi.dev
3 評論4:31 PM在 HN 查看
A coding environment designed to be "recursively self improving".... but a whole lot more. Uses web based chatbots to save tons of money while being within terms of service and still being efficient. Runs right off the web (with no signup) and saves to your browser and/or straight to disk. Open source. Lots of cool sample/template apps.
5

Digger Solo – Local AI File Explorer #

solo.digger.lol faviconsolo.digger.lol
0 評論7:25 PM在 HN 查看
After a lot of work I present Digger Solo 0.5.0 - the AI file explorer that respects your privacy (everything runs locally).

Demo video: https://vimeo.com/1198414414

New features: - LLM Chat with RAG (bring your own OpenAI compatible API key - ideally host a local model) - fresh redesign with light theme available in settings - multi-tabbed GUI: open multiple semantic maps at once - smart music player: auto-plays similar songs

Digger Solo offers semantic search and maps that allow you to browse your files intuively - uncovering hidden connections and near duplicates easily.

Happy to answer questions.

5

Bit-banged 10BASE-T Ethernet and Wi-Fi router in Rust on the Pico 2 W #

github.com favicongithub.com
0 評論3:27 PM在 HN 查看
Software 10BASE-T Ethernet (using PIO to bit-bang TX and RX) and wireless router on the Raspberry Pi Pico 2 W. Running cyw43 + an async executor in rust on the RP2350's RISC-V cores. Using cheap and minimal external hardware (just a magjack and ISL3177E RS-485 transceiver). I wanted to see how far I could get with the cheap, MCU-based, Wi-Fi router idea and learn some more about using rust on the RP2350 and RISC-V. Definitely not a good choice for a home router but it could be useful for low-rate IoT traffic.
3

Vlags, small vector flags. Less than 900 bytes each #

vlags.com faviconvlags.com
0 評論6:44 PM在 HN 查看
Hello HN. I created this set of SVG flag icons with small file sizes for an analytics dashboard project. I started this mostly for fun, many icon libraries I looked at had file sizes that were larger than necessary and some had details that looked off for complex flags. I’d seen lots of implementations of simplified flags across the web and wanted to create a set of my own and share it so that others can use them too.

The individual flags were drawn in illustrator, using a pixel grid to make the coordinates whole numbers and keep the size down. Claude code was used for much of the grunt work like fetching the reference images and arranging them into folders. There are a few that I may tweak slightly as well as some territories currently represented by their parent country’s flag that I may add.