Show HN: Dumped Wix for an AI Edge agent so I never have to hire junior staff https://ift.tt/6VEaDfd

Show HN: Dumped Wix for an AI Edge agent so I never have to hire junior staff I run a building design consultancy. I got tired of paying Wix $40/month for a brochure that couldn’t answer simple service questions, and me wasting hours on the same FAQs. So I killed it all and spent 4 months building a 'talker': https://axoworks.com The stack is completely duct-taped: Netlify’s 10s serverless timeout forced me to split the agent into three pieces: Brain (Edge), Hands (Browser), and Voice (Edge). I haven’t coded in 30 years. This was 3 steps forward, 2 steps back, heavily guided by AI. The fight that proved it worked: 2 weeks ago, a licensed architect attacked the bot, trying to prove my business model harms the profession. The AI (DeepSeek-R3) completely dismantled his arguments. It was hilariously caustic. Log: https://ift.tt/Db0GIML... A few battle scars: * Web Speech API works fine, right up until someone speaks Chinese without toggling the language mode. Then it forcefully spits out English phonetic gibberish. Still a headache. * Liability is the killer. Hallucinate a building code clause? We’re dead. Insurance won’t touch us. * We publish the audit logs to keep ourselves honest and make sure the system stays hardened. Audit: https://ift.tt/UreVD5c The hardest part was getting the intent right: making one LLM pivot seamlessly from a warm principal’s tone with a homeowner, to a defensive bulldog when attacked by a peer. That took 2.5 months of tuning. We burn through tokens with an 'Eager RAG' hack (pre-fetching guesses) just to improve responsiveness. I also ripped out the “essential” persistent DBs—less than 5% of visitors ever return, so why bother? If a client drops mid-query, their session vanishes. No server-side queues. The point: To let me operate with a network of seasoned pros, and trim the fat. Try to break it. I’ll be in the comments. Kee March 19, 2026 at 09:29PM

Show HN: Knowza.ai – Free 10-question trial now live (AI-powered AWS exam prep) https://ift.tt/6iuZD9v

Show HN: Knowza.ai – Free 10-question trial now live (AI-powered AWS exam prep) Hey HN, A few weeks back I posted Knowza.ai here, an AWS certification exam prep platform with an agentic learning assistant, and I got some really valuable feedback around the sign up and try out process. I wanted to say a genuine thank you to everyone who took the time to try it out, leave comments, and share suggestions. It made a real difference. Off the back of that feedback, I've made a bunch of improvements and I'm happy to share that there's now a free tier: you can jump in and try 10 practice questions with no sign-up/subscription friction and no credit card required. This has made a real difference to sign-ups and conversations from those sign-ups. I've went from ~1% conversation rate on the site to 18%. Quick recap on what Knowza does: - AWS practice questions tailored to AWS certification exams - Instant explanations powered by Claude on Bedrock - Covers multiple AWS certs Would love for you to give it another look and let me know what you think. Always open to feedback. https://knowza.ai https://www.knowza.ai/ March 19, 2026 at 12:20AM

Show HN: Tmux-IDE, OSS agent-first terminal IDE https://ift.tt/y6tY9FL

Show HN: Tmux-IDE, OSS agent-first terminal IDE Hey HN, Small OSS project that i created for myself and want to share with the community. It's a declarative, scriptable, terminal-based IDE focussed on agentic engineering. That's a lot of jargon, but essentially its a multi-agent IDE that you start in your terminal. Why is that relevant? Thanks to tmux and SSH, it means that you have a really simple and efficient way to create your own always-on coding setup. Boot into your IDE through ssh, give a prompt to claude and close off your machine. In tmux-ide claude will keep working. The tool is intentionally really lightweight, because I think the power should come from the harnesses that you are working with. I'm hoping to share this with the community and get feedback and suggestions to shape this project! I think that "remote work" is directionally correct, because we can now have extremely long-running coding tasks. But I also think we should be able to control and orchstrate that experience according to what we need. The project is 100% open-source, and i hope to shape it together with others who like to work in this way too! Github: https://ift.tt/SPsxpKt Docs: https://ift.tt/BswNkvb https://ift.tt/8xJNXCs March 18, 2026 at 11:16PM

Show HN: TerraShift: What does +2°C (or -20°C) look like on Earth? https://ift.tt/I95GVXt

Show HN: TerraShift: What does +2°C (or -20°C) look like on Earth? I built an interactive 3D globe to visualize climate change. Drag a temperature slider from -40°C to +40°C, set a timeframe (10 to 10,000 years), and watch sea levels rise, ice sheets melt, vegetation shift, and coastlines flood... per-pixel from real elevation and satellite data. Click anywhere on the globe to see projected snowfall changes for that location. --- I'm an amateur weather nerd who spends a lot of time on caltopo.com and windy.com tracking snow/ice conditions. I wanted to build something fun to imagine where I could go ski during an ice age. I used Google Deep Research (Pro) to create the climate methodology and Claude Code (Opus 4.6 - High) to create the site. The code: https://ift.tt/9qBFMG7 The models aren't proper climate simulations, they're simplified approximations tuned for "does this look right?" but more nuanced than I expected them to be. The full methodology is documented here if anyone wants to poke holes in it. https://ift.tt/vg9QTAl... https://terrashift.io March 18, 2026 at 01:08AM

Show HN: Sulcus Reactive AI Memory https://ift.tt/Vz86Jcu

Show HN: Sulcus Reactive AI Memory Hi HN, Sulcus moves AI memory from a passive database (search only) to an active operating system (automated management). The Core Shift Current memory (Vector DBs) is static. Sulcus treats memory like a Virtual Memory Management Unit (VMMU) for LLMs, using "thermodynamic" properties to automate what the agent remembers or forgets. Key Features Reactive Triggers: Instead of the agent manually searching, the memory system "talks back" based on rules (e.g., auto-pinning preferences, notifying the agent when a memory is about to "decay"). Thermodynamic Decay: Memories have "heat" (relevance) and "half-lives." Frequent recall reinforces them; neglect leads to deletion or archival. Token Efficiency: Claims a 90% reduction in token burn by using intelligent paging—only feeding the LLM what is currently "hot." The Tech: Built in Rust with PostgreSQL; runs as an MCP (Model Context Protocol) sidecar. https://ift.tt/UezSkat https://ift.tt/SANwxCf March 18, 2026 at 01:09AM

Show HN: Flowershow Publish Markdown in seconds. Hosted, free, zero config https://ift.tt/WL1xycw

Show HN: Flowershow Publish Markdown in seconds. Hosted, free, zero config I'm Rufus, one of the founders of Flowershow. We love markdown and use it everywhere from making websites, to docs, to knowledgebases. Plus AI splits it everywhere now. Got tired of the framework/config/deploy overhead every time we wanted to share a file or put a site online. So we built the thing we wanted. Files in. Website out. "Vercel for Content" is our aspiration - make deploying (markdown) content as fast, seamless and easy as Vercel did for JS. Command line plus you can connect to github repos, use Obsidian via plugin, or drag and drop files. npm i -g @flowershow/publish publish ./my-notes # → https://ift.tt/EF8yWui live in seconds Flowershow is fully hosted — no server, no build pipeline, no CI/CD. Point it at a Markdown folder and get a URL. Full Obsidian syntax: wiki links, callouts, graph view, frontmatter GFM, Mermaid, LaTeX: diagrams and math render natively Themes via Tailwind & CSS variables: Tailwind out of the box. Customize without a build step Supports HTML: use HTML, images etc. ~7k Obsidian plugin installs, 1,400 users, 1,100 sites. Free forever for personal use. Premium ($5/mo) adds custom domains, search, and password protection. And it's open source: https://ift.tt/mic9wJU Check it out and let us know what you think and what we can improve https://flowershow.app/ March 17, 2026 at 10:51PM

Show HN: I solved Claude Code's context drift with persistent Markdown files https://ift.tt/rgpzq7P

Show HN: I solved Claude Code's context drift with persistent Markdown files I've been using Claude Code to build SaaS products, and kept hitting the same wall: it writes brilliant code for 20 minutes, then forgets your database schema and starts rewriting working code. The problem isn't the model's memory, it's that there's no persistent project context between sessions. Come back tomorrow and Claude has zero knowledge of what it built yesterday. My solution: Force Claude to read project truth files before every action. I built a multi-agent system that creates persistent context files upfront: PROJECT.md - What you're building, business model, core features REQUIREMENTS.md - Database schema, auth flows, API structure, edge cases ROADMAP.md - Build phases with success criteria STATE.md - Current position, completed work, pending tasks How it works: AI Product Manager asks questions most developers skip: "How does money flow through this?" "What happens when users cancel mid-month?" + Any Edge cases specific to your SaaS Creates the markdown files from your answers. Claude Code reads these files before writing ANY code. No guessing. Can't forget the schema, it's literally documented. Executor agents spawn per task, each reading the same context files. They build in parallel but never break what's already working. Verifier agent tests against success criteria after each phase. If broken, spawns debugger agent with persistent investigation files. Results: Built 3 products in 30 days using this system: Analytics dashboard: 13 hours Feedback widget: 18 hours Content calendar: 9 hours No context drift. No "Claude forgot my auth system" moments. Just consistent builds. The biggest difference: Saturday: Build auth with Claude Sunday: Come back, describe next feature Claude reads REQUIREMENTS.md, sees existing auth schema Builds new feature without touching auth vs. the normal experience of Claude rewriting everything. I packaged this as PropelKit (Next.js boilerplate + AI PM system that creates these files automatically). But the core concept, persistent markdown context, works with any Claude Code setup. Try it: https://propelkit.dev The agent architecture uses Claude Sonnet/Opus (configurable) parallel thinking to spawn multiple agents that all read from the same truth files. Happy to answer questions about the implementation. March 16, 2026 at 11:06PM