System Card [pdf]: <a href="https:&#x2F;&#x2F;www-cdn.anthropic.com&#x2F;d00db56fa754a1b115b6dd7cb2e3c342ee809620.pdf" rel="nofollow">https:&#x2F;&#x2F;www-cdn.anthropic.com&#x2F;d00db56fa754a1b115b6dd7cb2e3c3...</a>

Claude Fable 5

Making Graphics Like it's 1993

OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

Microsoft's open source tools were hacked to steal passwords of AI developers

Cleaning up after AI rockstar developers

FCC wants to kill burner phones by forcing telecoms to get all customers' IDs

Apple decided not to roll out Siri in EU after denied request for exemption

Let's Encrypt bans certificate usage in any US sanctioned territory [pdf]

Thi.ng – open-source building blocks for computational design and art

The iPhone's Last Stand?

Forever Young: how one molecule can lock plants in a youthful state (2025)

Just for fun and self education, I&#x27;ve built this over a weekend to teach myself why orbits exist, not just show planets going around. Something that was never clearly explain to me in school. 
It opens with a guided tour that builds the idea up step by step: two bodies and the equal&#x2F;opposite force, inertia (the Sun is removed and Earth just drifts straight), then &quot;an orbit is falling and continuously missing,&quot; cosmic velocities with a little rocket, Voyager 1 &amp; 2&#x27;s real gravity assists (the clock runs the actual 1977–1989 dates so the planets orbit into their grand-tour alignment and the slingshots line up), and it ends on Einstein — gravity as curved spacetime, the classic rubber-sheet well.
What&#x27;s real: every body uses its real radius&#x2F;mass and J2000 orbital elements; positions come from solving Kepler&#x27;s equation each frame. You can toggle to an N-body mode (symplectic leapfrog) that shows live energy drift (~1e-6%) so you can see the integrator is honest. The only thing faked is scale — at true scale you can&#x27;t see anything — so there&#x27;s a toggle between true scale and a log-remapped &quot;visual&quot; scale, with physics always running in real AU.
Tech: TypeScript + Three.js + Vite, fully client-side, no backend, works offline (surface textures are generated procedurally from value-noise; only Earth uses a real image). Source: <a href="https:&#x2F;&#x2F;github.com&#x2F;qunabu&#x2F;Gravity" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;qunabu&#x2F;Gravity</a>Happy to answer questions — and feedback on the physics or the explanations is very welcome. This project might be totally inaccurate in terms of real physics, this is how i do understand this on my own - i&#x27;m happy to confront this with reality

Show HN: Gravity – interactive solar-system simulator, from Newton to Einstein

A giant star may have destroyed itself in one of the rarest explosions

Is Grep All You Need? How Agent Harnesses Reshape Agentic Search

Can LLMs Beat Classical Hyperparameter Optimization Algorithms?

What it feels like to work with Mythos

Hello HN,I&#x27;ve been working on a simple OS for tinkering and running bare metal apps on vintage PCs.Since I couldn&#x27;t quite decide whether to target pure 16-bit, or slightly more capable 32-bit machines, I ended up with two separate versions:- GentleOS&#x2F;32 (<a href="https:&#x2F;&#x2F;github.com&#x2F;luke8086&#x2F;gentleos32" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;luke8086&#x2F;gentleos32</a>) works on i386+, requires 4MB of RAM and VGA display supporting 640x480x16 mode or any 256-color VESA mode.- GentleOS&#x2F;16 (<a href="https:&#x2F;&#x2F;github.com&#x2F;luke8086&#x2F;gentleos" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;luke8086&#x2F;gentleos</a>) works on 80186+, requires less than 192KB of RAM and a CGA display supporting 320x200x4 mode.You can find more details in the repos.

Show HN: GentleOS – A pair of hobby OSes for vintage 32-bit and 16-bit PCs

Biff.core: system composition for Clojure web apps

Unified Controllable and Faithful Text-to-CAD Generation with LLMs

We launched Infracost on HN five years ago (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26064588">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26064588</a>) where our CLI generated cost estimates for infra-as-code, e.g. &quot;this Terraform PR adds $400&#x2F;mo&quot;. 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&#x27;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&#x27;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&#x27;t compose jq | python | wc pipelines, output format that strips JSON&#x27;s redundant field names. The blog is here: <a href="https:&#x2F;&#x2F;www.infracost.io&#x2F;resources&#x2F;blog&#x2F;we-cut-claude-s-token-usage-79-by-redesigning-our-cli-for-agents">https:&#x2F;&#x2F;www.infracost.io&#x2F;resources&#x2F;blog&#x2F;we-cut-claude-s-toke...</a>2. With cloud costs, precision matters. Telling a coding agent &quot;make this Terraform cost-optimized&quot; 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&#x27;t know because it&#x27;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&#x27;s what we&#x27;re launching today - Cost.dev: <a href="https:&#x2F;&#x2F;cost.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;cost.dev&#x2F;</a>.- It runs locally. Your code never leaves your machine, you get a fast feedback loop, and you&#x27;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&#x27;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 &quot;agents writing IaC in prod&quot; actually a thing yet, or am I betting on a future that&#x27;s still a year out? I know software developers are using coding agents heavily, but are platform&#x2F;infra folks doing that for prod too? Also, if you have any feedback on Cost.dev, I&#x27;d love to hear it!

Show HN: Cost.dev (YC W21) – making agents cost-aware and cheaper to call