Show HN: AgentSearch – Self-hosted search and MCP for AI agents, no API keys https://ift.tt/Dz6CWVR

Show HN: AgentSearch – Self-hosted search and MCP for AI agents, no API keys https://ift.tt/cEz6lvN April 24, 2026 at 01:25AM

Show HN: Turning a Gaussian Splat into a videogame https://ift.tt/t2LfW4B

Show HN: Turning a Gaussian Splat into a videogame https://ift.tt/z6F5hAH April 23, 2026 at 09:18PM

Show HN: Core – open-source AI butler that clears your backlog without you https://ift.tt/XhyIjrw

Show HN: Core – open-source AI butler that clears your backlog without you Hi HN, we're Manik, Manoj and Harshith, and we're building CORE ( https://ift.tt/9NWGre2 ), an open source AI butler that acts and clears out your backlog. Write `[ ] Fix the search auth bug` in a scratchpad. Three minutes later, without you at the keyboard, CORE picks it up, pulls the relevant context from your codebase, drafts a plan in the task description, and spins up a Claude Code session in the background to do the work. You review the output in the task chat and unblock it when it gets stuck. Every AI tool today is reactive. You open a chat, brief the agent, it responds. Before anything moves, you've already done the real work: opened the Sentry error, found the commit, read the Slack thread, grabbed the Linear ticket, and stitched it all together into a prompt. The model isn't the bottleneck. You are. Demo Video: https://www.youtube.com/watch?v=PFk4RJvQg1Y CORE removes you from that loop. The interface is a shared scratchpad, think a page you and a colleague both have open. You write what's on your mind. When you write a checkbox line like `[ ] Fix the search bug`, CORE converts it into a task and starts working on it after a short delay (long enough for you to add context if you want to). No prompt template. No workflow to configure. The reason it can do this without you re-explaining everything: CORE keeps a persistent memory built from your tasks, conversations, and connected apps (Linear, Gmail, GitHub, Slack etc.). When it spins up a Claude Code session, it arrives with your codebase and project context already loaded. A real example: we wrote `[ ] Create a widget in Linear integration`, about 14 minutes later, CORE had opened a PR . What CORE is _not_: it's not Devin (no autonomous web browsing or shell loops you can't see), and it's not "Claude Code with memory bolted on." It's the layer above it that decides what should run, gathers the context, hands it to the right agent, and keeps the receipts in one place. Today the agent backend it spins up most often is Claude Code; the orchestration, scratchpad, memory, and integrations are CORE. Open source, self-hostable with `docker compose up` and it supports multiple models. GitHub: https://ift.tt/9NWGre2 Website: https://getcore.me (you can chat with Harshith's butler there) Demo: https://www.youtube.com/watch?v=PFk4RJvQg1Y https://www.getcore.me/ April 23, 2026 at 10:14PM

Show HN: Netlify for Agents https://ift.tt/yUno4jd

Show HN: Netlify for Agents I launched Netlify with a Show HN more than 11 years today, for humans. Today we're launching our Agent first version of Netlify. Super early days for this, but I expect it to become as important as our original launch over time. It's as hard to perfect these flows as it was to perfect some of the initial human DX flows, since the agents are non-deterministic and keeps changing and evolving, and we'll have more to show soon on our eval tooling for this. Try it out with an agent, and we would love feedback on what works and what doesn't as we keep iterating on making Netlify better for our new agent friends. https://netlify.ai April 22, 2026 at 11:57PM

Show HN: A free tool for non-technical folks to easily publish a website https://ift.tt/aXDjhpx

Show HN: A free tool for non-technical folks to easily publish a website It's easier than ever for anyone to make a website, even without paying for a drag-and-drop builder like Squarespace. But there are still too many barriers for your average non-technical person to publish a site on the web. I'd bet most people don't know there are free ways to host a website, and even if they find an explainer, technical platforms like Cloudflare and GitHub (let alone the command line) can be intimidating. So I made weejur, which is basically a super simple UI front-end for GitHub Pages. You log in with OAuth, and then you can just paste HTML or upload files to publish a website. If you don't have a GitHub account, you can sign up right in the OAuth flow. It's completely free, and you can view the source here [1]. My hope is this makes it easier for people who don't know anything about web hosting to create and share their own websites. Feel free to try it out and please share any questions/ideas/feedback! [1] https://ift.tt/IMGqwFJ https://weejur.com April 22, 2026 at 11:06PM

Show HN: Ctx – a /resume that works across Claude Code and Codex https://ift.tt/6Bt2TUw

Show HN: Ctx – a /resume that works across Claude Code and Codex ctx is a local SQLite-backed skill for Claude Code and Codex that stores context as a persistent workstream that can be continued across agent sessions. Each workstream can contain multiple sessions, notes, decisions, todos, and resume packs. It essentially functions as a /resume that can work across coding agents. Here is a video of how it works: https://ift.tt/8Wgb4DE I initially built ctx because I wanted to try a workstream that I started on Claude and continue it from Codex. Since then, I’ve added a few quality of life improvements, including the ability to search across previous workstreams, manually delete parts of the context with, and branch off existing workstreams.. I’ve started using ctx instead of the native ‘/resume’ in Claude/Codex because I often have a lot of sessions going at once, and with the lists that these apps currently give, it’s not always obvious which one is the right one to pick back up. ctx gives me a much clearer way to organize and return to the sessions that actually matter. It’s simple to install after you clone the repo with one line: ./setup.sh, which adds the skill to both Claude Code and Codex. After that, you should be able to directly use ctx in your agent as a skill with ‘/ctx [command]’ in Claude and ‘ctx [command]’ in Codex. A few things it does: - Resume an existing workstream from either tool - Pull existing context into a new workstream - Keep stable transcript binding, so once a workstream is linked to a Claude or Codex conversation, it keeps following that exact session instead of drifting to whichever transcript file is newest - Search for relevant workstreams - Branch from existing context to explore different tasks in parallel It’s intentionally local-first: SQLite, no API keys, and no hosted backend. I built it mainly for myself, but thought it would be cool to share with the HN community. https://ift.tt/moFVkZp April 20, 2026 at 11:35PM

Show HN: Agentkit-CLI, one canonical context file for AI coding agents https://ift.tt/E8gBR2a

Show HN: Agentkit-CLI, one canonical context file for AI coding agents https://mikiships.github.io/agentkit-cli/ April 20, 2026 at 10:04PM

Show HN: A privacy-first, local-LLM note app for iOS (Google Keep alternative) https://ift.tt/KrmxHaX

Show HN: A privacy-first, local-LLM note app for iOS (Google Keep alternative) https://ift.tt/P6rQswD April 19, 2026 at 11:59PM

Show HN: Free PDF redactor that runs client-side https://ift.tt/dbNrwXy

Show HN: Free PDF redactor that runs client-side I recently needed to verify past employment and to do so I was going to upload paystubs from a previous employer, however I didn't want to share my salary in that role. I did a quick search online and most sites required sign-up or weren't clear about document privacy. I conceded and signed up for a free trial of Adobe Acrobat so I could use their PDF redaction feature. I figured there should be a dead simple way of doing this that's private, so I decided to create it myself. What this does is rasterize each page to an image with your redactions burned in, then it rebuilds the PDF so the text layer is permanently destroyed and not just covered up and easily retrievable. I welcome any and all feedback as this is my first live tool, thanks! https://redactpdf.net April 20, 2026 at 01:39AM

Show HN: Faceoff – A terminal UI for following NHL games https://ift.tt/9gnRhIw

Show HN: Faceoff – A terminal UI for following NHL games Faceoff is a TUI app written in Python to follow live NHL games and browse standings and stats. I got the inspiration from Playball, a similar TUI app for MLB games that was featured on HN. The app was mostly vibe-coded with Claude Code, but not one-shot. I added features and fixed bugs by using it, as I spent way too much time in the terminal over the last few months. Try it out with `uvx faceoff` (requires uv). https://ift.tt/NVuyAMC April 20, 2026 at 12:44AM

Show HN: Google Gemini Is Scanning Your Photos – and the EU Said No https://ift.tt/q2CGbs6

Show HN: Google Gemini Is Scanning Your Photos – and the EU Said No Google has expanded its Personal Intelligence feature so that Gemini can now access your Google Photos face data, Gmail, YouTube history, and search activity to generate personalized AI images — live for US paid subscribers as of April 2026. https://ift.tt/r5T7NsL... April 19, 2026 at 11:36PM

Show HN: AI Subroutines – Run automation scripts inside your browser tab https://ift.tt/jJLSZRb

Show HN: AI Subroutines – Run automation scripts inside your browser tab We built AI Subroutines in rtrvr.ai. Record a browser task once, save it as a callable tool, replay it at: zero token cost, zero LLM inference delay, and zero mistakes. The subroutine itself is a deterministic script composed of discovered network calls hitting the site's backend as well as page interactions like click/type/find. The key architectural decision: the script executes inside the webpage itself, not through a proxy, not in a headless worker, not out of process. The script dispatches requests from the tab's execution context, so auth, CSRF, TLS session, and signed headers get added to all requests and propagate for free. No certificate installation, no TLS fingerprint modification, no separate auth stack to maintain. During recording, the extension intercepts network requests (MAIN-world fetch/XHR patch + webRequest fallback). We score and trim ~300 requests down to ~5 based on method, timing relative to DOM events, and origin. Volatile GraphQL operation IDs are detected and force a DOM-only fallback before they break silently on the next run. The generated code combines network calls with DOM actions (click, type, find) in the same function via an rtrvr.* helper namespace. Point the agent at a spreadsheet of 500 rows and with just one LLM call parameters are assigned and 500 Subroutines kicked off. Key use cases: - record sending IG DM, then have reusable and callable routine to send DMs at zero token cost - create routine getting latest products in site catalog, call it to get thousands of products via direct graphql queries - setup routine to file EHR form based on parameters to the tool, AI infers parameters from current page context and calls tool - reuse routine daily to sync outbound messages on LinkedIn/Slack/Gmail to a CRM using a MCP server We see the fundamental reason that browser agents haven't taken off is that for repetitive tasks going through the inference loop is unnecessary. Better to just record once, and get the LLM to generate a script leveraging all the possible ways to interact with a site and the wider web like directly calling backed API's, interacting with the DOM, and calling 3P tools/APIs/MCP servers. https://ift.tt/J5mrUDp April 18, 2026 at 04:03AM

Show HN: Praxis – Lab data to publication-ready figures in one Python package https://ift.tt/itwyvOA

Show HN: Praxis – Lab data to publication-ready figures in one Python package https://ift.tt/u5Nj9xO April 19, 2026 at 01:15AM