Show HN: Metaspec: The DpANS3R Common Lisp Spec in S-Expr and HTML Format https://ift.tt/rjJQBqg

Show HN: Metaspec: The DpANS3R Common Lisp Spec in S-Expr and HTML Format I started this project back in 2015, to translate the TeX original specification into an easily parsed format (s-doc), and to create an HTML rendering of that format as a proof of concept. The project is homed here: https://ift.tt/TWe517g Differences from the Hyperspec (from the README): - Most importantly, it is free to modify and distribute. - The original TeX is very hard to parse and use for things other than generating a printed copy. The Hyperspec is an HTML rendering which can be parsed as HTML, but loses a lot of information. The Metaspec has an easily parsed intermediate form that can be used for all kinds of purposes, like converting into lookups. - Math equations are rendered using MathML. - Includes the acknowledgements and appendix sections. - Uses progressively enhanced Javascript to provide search and light/dark theme switching. - Incorporates over 145 patches for content, using corrections accumulated over the years, and documented in the errata page. - Includes TeX comments, which can contain interesting historical data. - Includes links and identifiers to bibliographical references. https://metaspec.dev/# June 24, 2026 at 11:28PM

Show HN: Forte – Cloud infra to get startups to production faster https://ift.tt/rcvXWRn

Show HN: Forte – Cloud infra to get startups to production faster Forte is an opinionated cloud platform that gets developers to production faster. Developers bring their code and Forte containerizes it with autoscaling and no cold starts, securely configures auth, and provides logging insights and monitoring out of the box. I used to help lead service development at AWS, and even before AI coding was widespread, our biggest bottleneck was rarely feature development. We would spend months on security prep, observability tooling, on-call optimization, and other overhead before launching new features. When I worked in startups, every team hit a surprisingly similar set of problems and spent weeks rebuilding auth, logging, monitoring, and payments. Platforms like Heroku, Render, and Railway are helpful for getting a container running but don't provide the rest of the tooling the teams need to go to production -- auth, secure defaults, and request-level logging. We built Forte to solve that entire stack of problems. You can check out Forte at https://ift.tt/jAQrPn7 (it's free to sign up and doesn't require a payment method). We'd love to hear your questions and feedback! https://ift.tt/jAQrPn7 June 24, 2026 at 11:06PM

Show HN: peerd – AI agent harness that runs entirely in your browser https://ift.tt/uIlsnDL

Show HN: peerd – AI agent harness that runs entirely in your browser Hey HN. http://peerd.ai is an AI agent harness that lives entirely in your browser as a web extension. You don’t have to install a separate “AI browser”. You don’t have to bolt on or run some external process or manage a clunky mcp integration. It’s just a fully contained web extension, written in no build vanilla JS with minimal non-browser dependencies, using your own provider keys, and Apache 2. This isn’t just a fun hack. While it has largely been a solo side project, I genuinely believe the browser and the web could be the most natural platform for AI agents to operate safely, autonomously, and most importantly without A2A middlemen (more on that in a sec). To demonstrate that point peerd doesn’t just drive browser automation. It spins up isolated sandboxes using tabs and worker instances to support various real workload types. Those include headless JS computational work, visual JS notebooks, personal client side apps, and real Linux VMs on top of wasm with full http networking. The industry discourse over the last several months has been dominated by “which substrate is the best for ai agent sandboxes” with many competing answers focused on different models and use cases. Cloudflare is one of the most prominent examples, positioning its v8 isolate based workers as the best in class solution thanks to faster than container startup times and strong isolation guarantees. The v8 isolate is of course the product of chromium, which runs on billions of browsers around the world for free. The browser as a whole is perhaps the most battle tested sandbox system in the entire software industry. It’s been built on 3 decades of learning from hostile content, hostile code, and hostile users. Native and cloud agents are necessarily rebuilding all or most of this posture from scratch. peerd doesn’t. It leverages everything the browser has to offer and pushes it to its functional limits, while inheriting its security baseline and isolation from the host system. Robust sandboxing isn’t the only thing the browser offers and peerd uses. It comes with extremely powerful and underrated primitives, from webCrypto, webRTC, webAuthn, webGPU, and ~soon WebNN. Direct web access, with your real live sessions, and api calls with fetch present an alternative model to MCP integrations. The agent can write and spawn web apps right there in a tab, no hosted service necessary. Then there’s the A2A piece: peerd already has a rudimentary p2p (peerd-to-peerd?) network in place using webRTC. Today you can connect with peers on the network, add them as contacts, and share signed apps you’ve created. I’m working on extending these apps to be able to leverage the same p2p network to support decentralized web apps (dwapps), as well as facilitate true p2p A2A with no platform or middlemen. Given this is an early part time project, this is an extremely experimental build and in a v0.x preview state. I’ve taken care to attempt to address the lethal trifecta: the main agent loops/sessions never ingest untrusted DOM code or possess low level navigation tools. It delegates those tasks to dedicated web runners with no wider tooling or secrets access that return summarized results. Both the DOM and the summarized results are bracketed as untrusted, meaning two stacked prompt injection escapes are needed. All egress goes through a central module that has a customizable deny list, and only models calls to designated allowed endpoints are possible. See more in the docs, site, and the code itself. Ultimately, use at your own risk. Today anthropic, open router, local ollama, and even an experimental WebGPU instance of Gemma are supported. Honest limitations: Chrome store and AMO are still pending until it can get more eyeballs and live usage. Just loading unpacked from GitHub is the easiest way to go, and as a bonus makes it easy to audit thanks to no build. Linux on wasm depends on the Cheerpx engine, which is not open source and has restrictions for commercial use. That may be a good reason to reassess it compared to alternatives, but it’s also the most performant and looks closest to implementing 64bit support. Poke around, use it, critique it, and have fun. https://ift.tt/yzLICVP June 23, 2026 at 10:05PM

Show HN: Caplets - Give your agent capabilities, not giant tool walls https://ift.tt/CoTcFYS

Show HN: Caplets - Give your agent capabilities, not giant tool walls https://caplets.dev June 23, 2026 at 11:31PM

Show HN: CUDA Profiler for Production Inference https://ift.tt/jFwhMz1

Show HN: CUDA Profiler for Production Inference https://ift.tt/9u7scD0 June 23, 2026 at 11:24PM

Show HN: I gave Claude Code the keys to the Visual Studio debugger https://ift.tt/JRsSwtu

Show HN: I gave Claude Code the keys to the Visual Studio debugger I use Visual Studio daily, and Claude Code only ships native integration for VS Code (annoying). So, I built the Visual Studio half myself. It's an unofficial extension that speaks Claude Code's undocumented IDE protocol. It started simple. Review Claude's edits in the real VS diff and accept or reject there, with no duplicate y/n prompt in the terminal, plus sharing the C# and C++ compiler errors with it directly. The infra I built for the extension allowed me to add the interesting part, the VS debugger. When you're paused at a breakpoint, Claude can read the call stack and locals, and with a toggle it can drive the debugger itself: set breakpoints, step, start and stop a session, and find a bug by running the code instead of reading it. There's a short walkthrough in the README where it catches a bug that never shows up in the output, by watching a counter fail to reset as it steps through a loop. Would really appreciate if you take the time to check it out. Thanks! https://ift.tt/qb5pOuN June 23, 2026 at 11:14PM

Show HN: Oak – Git replacement designed for agents https://ift.tt/RTpxg02

Show HN: Oak – Git replacement designed for agents Oak is a version control system I've been working on designed for agents ( https://oak.space ). It improves the speed and context your agents need when working on serious projects. With virtual mounts, agents locally and in the cloud no longer need a full copy of a repo to get working. You can work on many tasks in parallel without needing to download everything or fight worktrees. Version control shouldn't waste you or your agents time. It should be fast, creative and fun to make things with agents. Oak is still early in development. There's no Windows build and missing plenty of features (no CI, no issues, no comments). We still use GitHub Actions for building Oak now, but we've been fully bootstrapped on Oak with no Git backup for several months: https://oak.space/oak/oak . Blog post: https://oak.space/blog#git-is-forever Docs: https://oak.space/docs https://oak.space/oak/oak June 22, 2026 at 10:37PM

Show HN: Selector Forge – browser extension for AI-generated resilient selectors https://ift.tt/LT39K5g

Show HN: Selector Forge – browser extension for AI-generated resilient selectors Hi HN, I'm Ahmad from the Intuned ( https://intunedhq.com ) team. Today, we're releasing and open-sourcing Selector Forge ( https://ift.tt/2DBhQJc ), a browser extension that generates reliable CSS/XPath selectors using AI. You can use it to create a selector for a single element or for an array of elements. The selectors it creates are meant to be "semantic" and more resilient to page changes than what Chrome DevTool’s “Copy Selector” (and other similar extensions) give you. Those tend to hand you something brittle like `#top > div.w-100.ph0-l.ph3.ph4-m > h1 > span`, which can break with a minimal page change. Selector Forge aims for selectors that don't break as easily. Here are some selectors that Selector Forge created: `//div[@aria-label="Showing weekly downloads"]//p[@aria-live="polite"]` (item selector) and `//*[local-name()='svg' and @aria-label="Download statistics"]/following-sibling::div` (list selector). Here is a video demo of using the extension: https://www.youtube.com/watch?v=8IjjeDQkKmo Selector Forge on Chrome: https://ift.tt/wtPCTDm... Selector Forge on Firefox: https://ift.tt/BJUDVnq... Selector Forge code: https://ift.tt/1HtP4ub Backstory: For the past couple of years we've been building Intuned Agent, a coding agent for building and maintaining browser automations. We quickly figured out that the most fragile part of any browser code is usually the selectors and that creating good selectors can go a long way towards improving the quality and reliability of the automation itself. So we abstracted selector creation into its own agent, wrapped it as a tool, and let our codegen agent call it. LLMs by default don't do a great job generating good selectors, so this turned out to be really useful and improved the code our agent generates. We recently thought that this piece (the selector agent/creation) is useful on its own (outside our platform) so we packaged it as a browser extension. That’s this post! Selector Forge is open source, and the version in the browser stores (Chrome and Firefox) is free for up to 200 selectors/month. Unlimited usage is part of our paid plans. We realize most developers aren't writing this kind of code by hand anymore, so the next step is exposing this functionality in a way coding agents can call directly, over a CLI or MCP. Here's our roadmap: https://ift.tt/aUYsDTE Excited to hear your thoughts, questions, and feedback! https://ift.tt/1HtP4ub June 22, 2026 at 09:21PM

Show HN: React Native Boost – swaps RN's Text/View wrappers for native ones https://ift.tt/nihrMTw

Show HN: React Native Boost – swaps RN's Text/View wrappers for native ones https://ift.tt/2ePMjWq June 23, 2026 at 12:01AM

Show HN: Smolsonic – A Subsonic-compatible music server written in Rust https://ift.tt/HNyaFqP

Show HN: Smolsonic – A Subsonic-compatible music server written in Rust https://ift.tt/qOudRDA June 22, 2026 at 11:40PM

Show HN: DebugBrief – turn debugging sessions into reports, no AI https://ift.tt/Fhl5Ljz

Show HN: DebugBrief – turn debugging sessions into reports, no AI https://ift.tt/qou07P4 June 22, 2026 at 02:57AM

Show HN: CleverCrow: give tokens to your favorite projects https://ift.tt/X2xcPve

Show HN: CleverCrow: give tokens to your favorite projects Howdy all. I'm Zack :wave:. I've been thinking about the problem of misguided AI pull requests and figured I'd throw a possible solution out there for feedback. Basically, CleverCrow lets supporters give tokens to a GitHub repo (or set of issues in that repo) for the maintainers to use to build/fix stuff. The fun implementation challenges have been around implementing the pooling dynamics and keeping the maintainers in charge while the backers are motivated to support their work. https://clevercrow.io June 22, 2026 at 02:06AM

Show HN: Pulse – Dashboard for Claude Code, approve tool calls from your phone https://ift.tt/4HxnYp5

Show HN: Pulse – Dashboard for Claude Code, approve tool calls from your phone Hi everyone, I'm a student from Flanders and I like to use Claude Code for my purposes, ideas and also just for fun and also make solutions for problems in our world!) So that's why I built "Pulse", it's an local application that you can easily install to your device and easily follow what your claude agent is doing right now in your terminal session with an ambiance design and easily give permissions for your agent. For those who wants to see directly how much tokens you spent, and how much the session costs, and approve tool calls from everywhere from your phone and everything runs locally without an account can install Pulse from GitHub: https://ift.tt/1NtPnEF https://ift.tt/1NtPnEF June 21, 2026 at 03:46AM