Postingan

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

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/RoCTqW3 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 fo...
Posting Komentar
Baca selengkapnya

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

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...
Posting Komentar
Baca selengkapnya

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

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 s...
Posting Komentar
Baca selengkapnya

Show HN: OpenUser: Self-hosted user-persona tester for AI coding agents https://ift.tt/vQAaLJn

Show HN: OpenUser: Self-hosted user-persona tester for AI coding agents Recent hype about loop engineering made me realize that im missing one thing, and that is an agent that should be doing my job at the end of my loop: real user test i developing a huge b2b ecommerce project codebase. and for every new feature or fixes my job is always to test it on the browser. yuck. so i have made some research and there is TestSprite, but its not what i really want, i cant even self host it. so i built OpenUser. now i just engineer the loop with simple prompt: complete {feature} and use /openuser to test it. it store user persona, struggle, checkpoints, console logs, network logs. the agent has access to all and just fix everything. this is the real replacement of me at the end of the loop. everything runs locally, with any coding agents and model. try it: https://ift.tt/rdTFNAG npx openuser-cli June 24, 2026 at 12:03AM
Posting Komentar
Baca selengkapnya

Show HN: Your self, in every light - a local-first MCP self model for AI agents https://ift.tt/MdZjTne

Show HN: Your self, in every light - a local-first MCP self model for AI agents https://ift.tt/OXwJfe8 June 23, 2026 at 11:49PM
Posting Komentar
Baca selengkapnya

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

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

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

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....
Posting Komentar
Baca selengkapnya