Show HN: Modern demo of Douglas Hofstadter et al.'s 2001 Letter Spirit project https://ift.tt/G5BTgKe

Show HN: Modern demo of Douglas Hofstadter et al.'s 2001 Letter Spirit project https://ift.tt/odBEFPr August 23, 2026 at 10:02PM

Show HN: CtrlTool – 132 free online tools for developers and everyday tasks https://ift.tt/579NcCm

Show HN: CtrlTool – 132 free online tools for developers and everyday tasks Hey HN, I built CtrlTool because I kept needing small tools for random things and didn't want to install something or sign up for another website. It currently has 132 tools for things like JSON, JWT, Base64, URLs, text, hashes, PDFs, SEO, converters, generators, and other everyday stuff. The main thing I tried to focus on is making the tools fast and simple. For tools where it makes sense, everything runs locally in the browser so the data doesn't need to be uploaded to a server. It's still very new, so I'm mostly looking for feedback on the UX, which tools are actually useful, and what you think is missing. https://ctrltool.wtf Would appreciate any feedback. https://ctrltool.wtf August 23, 2026 at 05:44AM

Show HN: Built a CLI to find and disable telemetry for package.json dependencies https://ift.tt/dUfJEwi

Show HN: Built a CLI to find and disable telemetry for package.json dependencies https://ift.tt/Ysqk19L August 23, 2026 at 12:28AM

Show HN: OzBrain, a shared brain for knowledge between agents and your team https://ift.tt/Jafgq9U

Show HN: OzBrain, a shared brain for knowledge between agents and your team I think agent-first chat interfaces will be a primary software modality and busy dashboard/UI will go away. I’m not sure who exactly wins it, but I want my knowledge to grow/go with me. A lot of the “knowledge” ie research, analysis, reasoning will be done by agents as the primary user. Our current notes tools & tasks management systems were built for humans… I don’t care what the 17th thing on my bug backlog is. I want to conduct agents that can execute for me and do great work. What I built OzBrain to do: + Create a central place for agent reasoned knowledge to live + Be agnostic about what apps/agents connect to it + Capture everything and track it so I can audit it + Enable teams, collaborators or partners to share brains + Handle conflicts so many agents in the same article doesn’t blow up + Refactor knowledge into more token friendly chunks and map the index well + Close the knowledge loop so new thinking supersedes old thinking across the corpus. Don’t erase, depreciate and link + Keep user data safe and secure ++ Be easy enough to use that you don’t have to have any technical knowledge Some among us will always build their own custom solutions, but there are millions of tech professionals and small business owners that will use agents heavily and need a solution. So I’m trying to build that. Isn’t this like gBrain? Yes, similar. I think it’s like AWS vs Vercel. AWS is very powerful, configurable, and useful if you’re technical and want to invest the time into really fine tuning your system… but if you just want your web deploy/hosting to just work and be easy to deal with you use Vercel. // WHY I MADE IT I’ve been enjoying getting back to my technical roots, as I lost my coding skills more than a decade ago, but with AI I can focus on the system and the product in partnership with agent coding workflows. I recently built a Voice AI for older people. To build it I created an agentic engineering workflow (feel free to rip that up as I’m always looking to improve systems: https://ift.tt/QPNaX1Z ) My approach with coding agents is trust but verify, and I’m trying to replace the parts where a human would review with an adversarial or specialized agent who would give a better answer/review. I have workflows that will go high level task to shipped PR running in Claude cloud sessions. I use Claude Code locally and Cursor when I want a tighter loop on doing visual work like UI or layout. And Codex to either load balance usage for TokenThriffting or when I want a different llm to think thru something. It was a pain in the ass passing .md files around and keep track of which version was the most recent, so I built a hosted .md storage right in Supabase and any of my agents already have Supabase access. This let me build a solid, scalable, secure voice AI from my phone at the gym. All my agents have access to our knowledge, can write to it, update and refer to it as we build and improve the product and the systems we use. Out of 75 founder friends I asked about how they manage shared knowledge, 26 built their own custom knowledge systems… Obsidian vaults with 7k files synced through a VPS, markdown repos behind their own MCP servers, cron jobs stitching Supabase to a skills file… each a different Frankenstein they have to maintain. 32 said they felt the pain of moving static files around but didn’t have any solution for it. So I rebuilt my brain better and used it to build it. // HOW YOU CAN HELP Would love to have you try it out. The maintenance loop is still in alpha so not running it on customer data yet. If you built your own brain I’d love to hear how you did it. What criteria was most important for you in its design & function. If you are tired of shuffling .md files around I’d love to have you try out OzBrain and to give feedback, just ask your agent to put it in the shared bugs & features brain! Cheers! Bubs.co https://ozbrain.com August 22, 2026 at 03:09AM

Show HN: Traccia - Observability, Runtime Control & Audit for agents https://ift.tt/izQqE7d

Show HN: Traccia - Observability, Runtime Control & Audit for agents AI applications are becoming agents, which has started to take autonomous decisions. There are plenty of tools and platform available to trace, and observe what an agent or llms calls does. They are good in what they do, but tracing and observability isnt enough for AI agents era. We need a solution that can help you observe, evaluate, create run time policies to govern and finally audit the actions of the agent. We built Traccia to solve this problem. The good part, all of these can be achieved by just writing few lines of code. Traccia has an open-sourced sdk that can work with your existing observability tool like grafana, tempo, jaeger, etc. In case you need more than just observability, Traccia provides the platform to evaluate, control and audit the agents. The platform is easy to use. The product's documentation is quite extensive. It is also cloud vendor and framework agnostic. Traccia is being built by an Indian start up ,based out of Bengaluru. We are running a 3 months free trials so that you can explore without any strings attached. We are open to improvise and get better so please drop your comments and feedbacks. https://traccia.ai/ August 21, 2026 at 10:20PM

Show HN: CSVtoTable – turn a CSV/XLSX into one self-contained HTML file https://ift.tt/GQ2U5ei

Show HN: CSVtoTable – turn a CSV/XLSX into one self-contained HTML file https://ift.tt/Qiwx5eV August 21, 2026 at 10:53PM

Show HN: Huzzah – a novel approach to coding with AI https://ift.tt/d9bILxf

Show HN: Huzzah – a novel approach to coding with AI Hello everyone. I've been working on this experimental editor called Huzzah. I've been working almost exclusively with coding agents since January of this year, and over the past few months I began to feel utterly exhausted by them. They're great, but I'm finding it more and more tedious to write full sentences for every change I want. Not only that, but it seems there's a complexity limit for codebases - beyond a certain point the agent begins confusing itself. I'd like to go back to writing code, but I don't want to go all the way back to fully manual coding. So I've come up with this interaction paradigm where you: 1. write pseudocode in whatever way makes the most sense to you 2. on save, the editor synchronizes your work to real source code 3. the pseudocode is persisted alongside the generated code, making your prompt effectively a stored record of intent. It may not work for every use case, but in my initial playthroughs I've found it very enjoyable. Right now it's just a proof of concept - installation instructions are here in the readme: https://ift.tt/teKZjb2 You can also watch a video of it in action here: https://ift.tt/Sw5RZIm Cheers! https://ift.tt/cPT1pj6 August 20, 2026 at 11:05PM