🛠️ Hacker News Tools

[Testing] Show HN: Tusk Drift – Turn production traffic into API tests Hi HN! In the past few months my team and I have been working on Tusk Drift, a system that records real API traffic from your service, then replays those requests as deterministic tests. Outbound I&#x2F;O (databases, HTTP calls, etc.) gets automatically mocked using the recorded data.<p>Problem we&#x27;re trying to solve: Writing API tests is tedious, and hand-written mocks drift from reality. We wanted tests that stay realistic because they come from real traffic.<p>versus mocking libraries: Tools like VCR&#x2F;Nock intercept HTTP within your tests. Tusk Drift records full request&#x2F;response traces externally (HTTP, DB, Redis, etc.) and replays them against your running service, no test code or fixtures to write&#x2F;maintain.<p>How it works:<p>1. Add a lightweight SDK (we currently support Python and Node.js)<p>2. Record traffic in any environment.<p>3. Run `tusk run`, the CLI sandboxes your service and serves mocks via Unix socket<p>We run this in CI on every PR. Also been using it as a test harness for AI coding agents, they can make changes, run `tusk run`, and get immediate feedback without needing live dependencies.<p>Source: <a href="https:&#x2F;&#x2F;github.com&#x2F;Use-Tusk&#x2F;tusk-drift-cli" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Use-Tusk&#x2F;tusk-drift-cli</a><p>Demo: <a href="https:&#x2F;&#x2F;github.com&#x2F;Use-Tusk&#x2F;drift-node-demo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Use-Tusk&#x2F;drift-node-demo</a><p>Happy to answer questions!

[Other] Show HN: Control Claude permissions using a cloud-based decision table UI We’ve been building visual rule engines (clear interfaces + API endpoints that help map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.<p>The result is a surprisingly useful policy&#x2F;gating layer– these tables let your team:<p>- Write multi-factor, exception-friendly policies (e.g. deny rm -rf &#x2F; when --force; allow cleanup only in node_modules; ask on network calls like curl&#x2F;wget; block kubectl delete or SQL DROP, each with a clear reason)<p>- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)<p>- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP&#x2F;skills&#x2F;etc)- just add columns&#x2F;rules as new tools and metadata show up<p>- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why

[Other] New Safari developer tools provide insight into CSS Grid Lanes

[Database] ChromaDB Explorer <a href="https:&#x2F;&#x2F;github.com&#x2F;stepandel&#x2F;chroma-explorer" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;stepandel&#x2F;chroma-explorer</a>

[Other] Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: &#x2F;plugin marketplace add jshchnz&#x2F;claude-code-scheduler &#x2F;plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.

[CLI Tool] Show HN: A fast CLI and MCP server for managing Lambda cloud GPU instances I built an unofficial CLI and MCP server for Lambda cloud GPU instances.<p>The main idea: your AI agents can now spin up and manage Lambda GPUs for you.<p>The MCP server exposes tools to find, launch, and terminate instances. Add it to Claude Code, Cursor, or any agent with one command and you can say things like &quot;launch an H100, ssh in, and run big_job.py&quot;<p><pre><code> Other features: - Notifications via Slack, Discord, or Telegram when instances are SSH-ready - 1Password support for API keys - Also includes a standalone CLI with the same functionality </code></pre> Written in Rust. MIT licensed.<p>Note: This is an unofficial community project, not affiliated with Lambda.

[CLI Tool] Show HN: Grsh – A high-performance shell for FreeBSD written in Rust I built GRSH because I wanted a modern, memory-safe shell that feels native to FreeBSD but works seamlessly on macOS.<p>While there are many shells out there, GRSH is my take on a minimal, fast, and secure command interpreter written entirely in Rust. It&#x27;s designed for users who want the safety guarantees of Rust without the overhead of more bloated alternatives.<p>I&#x27;m currently working on the official FreeBSD port. I’d love to get feedback on the shell&#x27;s behavior and performance from the community.<p>Github: <a href="https:&#x2F;&#x2F;github.com&#x2F;antoniomalara301289&#x2F;grsh" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;antoniomalara301289&#x2F;grsh</a>

[CLI Tool] Show HN: Nori CLI, a better interface for Claude Code (no flicker) Hi HN, my name&#x27;s Clifford and I&#x27;m one of the creators of Nori. I’ve been using Claude Code heavily since last summer, and after understanding some of the tradeoffs with their TUI implementation, I knew I couldn&#x27;t see myself living for years with this interface as one of my daily-driver tools.<p>It is <i>not</i> a hard problem to make monospace text output performant, so why does Claude Code suffer from flicker and strobing in the terminal (<a href="https:&#x2F;&#x2F;github.com&#x2F;anthropics&#x2F;claude-code&#x2F;issues&#x2F;1913" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;anthropics&#x2F;claude-code&#x2F;issues&#x2F;1913</a>)? Even after they&#x27;ve released multiple improvements for this, I still see the issue in terminal splits with fewer rows, or in less performant emulators, and even within a virtual TTY (the absolute simplest environment to run an interactive program in). After digging in throughout the past half year, the issue is mostly inevitable because Claude reprints full terminal history without using alt screen mode and uses a React-based framework (Ink) to render and style their text. That&#x27;s great for JS+CSS being &quot;on distribution&quot; for LLMs in order to vibecode the continued development of Claude Code, but it doesn&#x27;t deliver the experience I&#x27;d like. The frameworks they&#x27;ve chosen also have limitations around [terminal input parsing (i.e. the shift enter issues from last year: <a href="https:&#x2F;&#x2F;github.com&#x2F;anomalyco&#x2F;opencode&#x2F;issues&#x2F;1505#issuecomment-3411334883" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;anomalyco&#x2F;opencode&#x2F;issues&#x2F;1505#issuecomme...</a>). Great terminal interfaces I&#x27;ve lived with for years (neovim, btop, helix, Cataclysm DDA, etc) don&#x27;t sacrifice user experience as a tradeoff for development convenience. They build resilient terminal interfaces on languages more appropriate for this problem, like C or C++ or Rust.<p>Finally, while I&#x27;m definitely rooting for Anthropic to continue improving their products, I can&#x27;t see myself coupling a commandline tool I use often with a single LLM provider. It would be insane if pushing my code to GitHub required me to edit it in VSCode — I want my tooling to do one thing well, and that&#x27;s display the read-eval-tool-loop from talking to an agent. Opus 4.5 has been stellar, but it&#x27;s nonnegotiable to me that I can try out varied providers with the same tools I plan to use everyday. Claude Code will not be working long term on how best to interface with multiple agents, from varying providers, in one terminal pane, and that makes perfect sense for their business. However based on our other experiences building out profiles and skillsets for agents, deeper customizations of agent instructions and subagents, and parallel worktrees for local agents, we have a lot of vision for how to handle local agentic work. And with the current design to integrate at the agent-level, we don&#x27;t plan on working around the OAuth flows or spoofing the system prompt outside of the Claude Code SDK (like with the OpenCode situation), and risk the tools coming into conflict with the providers.<p>These were the main considerations that went into designing Nori CLI. It&#x27;s a very thin and very fast TUI wrapper around multiple agent providers. It integrates with providers at the agent level, instead of the model level. Not only does that provide better performance in our experience, but that is also *compliant with current ToS for subscription based usage.* This is a very early version, but given the timing this week it might give you a flicker-free way to code with Claude Code!<p>The project is open source, and built on the stellar work by folks at Zed (on the abstraction over varied coding agents), and the folks working on Codex CLI (who have put together one of the nicest proprietary terminal experiences).<p>I&#x27;m very curious: What are the Claude Code features you couldn&#x27;t give up, to make the switch to a tool like this? What are the Claude Code features that work as intended, but you can&#x27;t stand?

[Other] Show HN: Webctl – Browser automation for agents based on CLI instead of MCP

[Other] Inside The Internet Archive's Infrastructure <a href="https:&#x2F;&#x2F;github.com&#x2F;internetarchive&#x2F;heritrix3" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;internetarchive&#x2F;heritrix3</a>

[Other] Claude Cowork runs Linux VM via Apple virtualization framework

[Other] Show HN: OpenWork – an open-source alternative to Claude Cowork hi hn,<p>i built openwork, an open-source, local-first system inspired by claude cowork.<p>it’s a native desktop app that runs on top of opencode (opencode.ai). it’s basically an alternative gui for opencode, which (at least until now) has been more focused on technical folks.<p>the original seed for openwork was simple: i have a home server, and i wanted my wife and i to be able to run privileged workflows. things like controlling home assistant, or deploying custom web apps (e.g. our customs recipe app recipes.benjaminshafii.com), legal torrents, without living in a terminal.<p>our initial setup was running the opencode web server directly and sharing credentials to it. that worked, but i found the web ui unreliable and very unfriendly for non-technical users.<p>the goal with openwork is to bring the kind of workflows i’m used to running in the cli into a gui, while keeping a very deep extensibility mindset. ideally this grows into something closer to an obsidian-style ecosystem, but for agentic work.<p>some core principles i had in mind:<p>- open by design: no black boxes, no hosted lock-in. everything runs locally or on your own servers. (models don’t run locally yet, but both opencode and openwork are built with that future in mind.) - hyper extensible: skills are installable modules via a skill&#x2F;package manager, using the native opencode plugin ecosystem. - non-technical by default: plans, progress, permissions, and artifacts are surfaced in the ui, not buried in logs.<p>you can already try it: - there’s an unsigned dmg - or you can clone the repo, install deps, and if you already have opencode running it should work right away<p>it’s very alpha, lots of rough edges. i’d love feedback on what feels the roughest or most confusing.<p>happy to answer questions.

[Other] Show HN: Cachekit – High performance caching policies library in Rust

[Other] Open sourcing Dicer: Databricks's auto-sharder

[IDE/Editor] Show HN: Nogic – VS Code extension that visualizes your codebase as a graph I built Nogic, a VSCode extension currently, because AI tools make code grow faster than developers can build a mental model by jumping between files. Exploring structure visually has been helping me onboard to unfamiliar codebases faster.<p>It’s early and rough, but usable. Would love feedback on whether this is useful and what relationships are most valuable to visualize.

[Other] Show HN: Ayder – HTTP-native durable event log written in C (curl as client) Hi HN,<p>I built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs).<p>There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there.<p>Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg&#x2F;s sustained (wrk2 @ 50K req&#x2F;s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets.<p>Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any event ingestion&#x2F;streaming workload).

[Other] Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT

[Other] Show HN: Self-host Reddit – 2.38B posts, works offline, yours forever Reddit&#x27;s API is effectively dead for archival. Third-party apps are gone. Reddit has threatened to cut off access to the Pushshift dataset multiple times. But 3.28TB of Reddit history exists as a torrent right now, and I built a tool to turn it into something you can browse on your own hardware.<p>The key point: This doesn&#x27;t touch Reddit&#x27;s servers. Ever. Download the Pushshift dataset, run my tool locally, get a fully browsable archive. Works on an air-gapped machine. Works on a Raspberry Pi serving your LAN. Works on a USB drive you hand to someone.<p>What it does: Takes compressed data dumps from Reddit (.zst), Voat (SQL), and Ruqqus (.7z) and generates static HTML. No JavaScript, no external requests, no tracking. Open index.html and browse. Want search? Run the optional Docker stack with PostgreSQL – still entirely on your machine.<p>API &amp; AI Integration: Full REST API with 30+ endpoints – posts, comments, users, subreddits, full-text search, aggregations. Also ships with an MCP server (29 tools) so you can query your archive directly from AI tools.<p>Self-hosting options: - USB drive &#x2F; local folder (just open the HTML files) - Home server on your LAN - Tor hidden service (2 commands, no port forwarding needed) - VPS with HTTPS - GitHub Pages for small archives<p>Why this matters: Once you have the data, you own it. No API keys, no rate limits, no ToS changes can take it away.<p>Scale: Tens of millions of posts per instance. PostgreSQL backend keeps memory constant regardless of dataset size. For the full 2.38B post dataset, run multiple instances by topic.<p>How I built it: Python, PostgreSQL, Jinja2 templates, Docker. Used Claude Code throughout as an experiment in AI-assisted development. Learned that the workflow is &quot;trust but verify&quot; – it accelerates the boring parts but you still own the architecture.<p>Live demo: <a href="https:&#x2F;&#x2F;online-archives.github.io&#x2F;redd-archiver-example&#x2F;" rel="nofollow">https:&#x2F;&#x2F;online-archives.github.io&#x2F;redd-archiver-example&#x2F;</a><p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;19-84&#x2F;redd-archiver" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;19-84&#x2F;redd-archiver</a> (Public Domain)<p>Pushshift torrent: <a href="https:&#x2F;&#x2F;academictorrents.com&#x2F;details&#x2F;1614740ac8c94505e4ecb9d88be8bed7b6afddd4" rel="nofollow">https:&#x2F;&#x2F;academictorrents.com&#x2F;details&#x2F;1614740ac8c94505e4ecb9d...</a>

[Other] Show HN: FastScheduler – Decorator-first Python task scheduler, async support Hi! I&#x27;ve built this because I kept reaching for Celery for simple scheduled tasks and it felt like overkill. I just needed &quot;run this function every hour&quot; or &quot;daily at 9am&quot;, not distributed workers.<p>So it&#x27;s decorators for scheduling (@scheduler.every(5).minutes, @scheduler.daily.at(&quot;09:00&quot;)), state saves to JSON so jobs survive restarts, and there&#x27;s an optional FastAPI dashboard if you want to see what&#x27;s running.<p>No Redis, no message broker, runs in-process with your app. Trade-off is it&#x27;s single process only — if you need distributed workers, stick with Celery.

[DevOps] Show HN: SnackBase – Open-source, GxP-compliant back end for Python teams Hi HN, I’m the creator of SnackBase.<p>I built this because I work in Healthcare and Life Sciences domain and was tired of spending months building the same &quot;compliant&quot; infrastructure (Audit Logs, Row-Level Security, PII Masking, Auth) before writing any actual product code.<p>The Problem: Existing BaaS tools (Supabase, Appwrite) are amazing, but they are hard to validate for GxP (FDA regulations) and often force you into a JS&#x2F;Go ecosystem. I wanted something native to the Python tools I already use.<p>The Solution: SnackBase is a self-hosted Python (FastAPI + SQLAlchemy) backend that includes:<p>Compliance Core: Immutable audit logs with blockchain-style hashing (prev_hash) for integrity.<p>Native Python Hooks: You can write business logic in pure Python (no webhooks or JS runtimes required).<p>Clean Architecture: Strict separation of layers. No business logic in the API routes.<p>The Stack:<p>Python 3.12 + FastAPI<p>SQLAlchemy 2.0 (Async)<p>React 19 (Admin UI)<p>Links:<p>Live Demo: <a href="https:&#x2F;&#x2F;demo.snackbase.dev" rel="nofollow">https:&#x2F;&#x2F;demo.snackbase.dev</a><p>Repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;lalitgehani&#x2F;snackbase" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lalitgehani&#x2F;snackbase</a><p>The demo resets every hour. I’d love feedback on the DSL implementation or the audit logging approach.