Daily Show HN

Upvote0

Show HN for February 1, 2026

51 items
572

Craftplan – I built my wife a production management tool for her bakery #

github.com favicongithub.com
166 comments5:25 PMView on HN
My wife was planning to open a micro-bakery. We looked at production management software and it was all either expensive or way too generic. The actual workflows for a small-batch manufacturer aren't that complex, so I built one and open-sourced it.

Craftplan handles recipes (versioned BOMs with cost rollups), inventory (lot traceability, demand forecasting, allergen tracking), orders, production batch planning, and purchasing. Built with Elixir, Ash Framework, Phoenix LiveView, and PostgreSQL.

Live demo: https://craftplan.fly.dev ([email protected] / Aa123123123123)

GitHub: https://github.com/puemos/craftplan

527

NanoClaw – "Clawdbot" in 500 lines of TS with Apple container isolation #

github.com favicongithub.com
224 comments10:49 PMView on HN
I’ve been running Clawdbot for the last couple weeks and have genuinely found it useful but running it scares the crap out of me.

OpenClaw has 52+ modules and runs agents with near-unlimited permissions in a single Node process. NanoClaw is ~500 lines of core code, agents run in actual Apple containers with filesystem isolation. Each chat gets its own sandboxed context.

This is not a swiss army knife. It’s built to match my exact needs. Fork it and make it yours.

48

Voiden – an offline, Git-native API tool built around Markdown #

github.com favicongithub.com
28 comments3:09 PMView on HN
Hi HN,

We have open-sourced Voiden.

Most API tools are built like platforms. They are heavy because they optimize for accounts, sync, and abstraction - not for simple, local API work.

Voiden treats API tooling as files.

It’s an offline-first, Git-native API tool built on Markdown, where specs, tests, and docs live together as executable Markdown in your repo. Git is the source of truth.

No cloud. No syncing. No accounts. No telemetry.Just Markdown, Git, hotkeys, and your damn specs.

Voiden is extensible via plugins (including gRPC and WSS).

Repo: https://github.com/VoidenHQ/voiden

Download Voiden here : https://voiden.md/download

We'd love feedback from folks tired of overcomplicated and bloated API tooling !

26

SymDerive – A functional, stateless symbolic math library #

14 comments1:20 AMView on HN
Hey HN,

I’m a physicist turned quant. Some friends and I 'built' SymDerive because we wanted a symbolic math library that was "Agent-Native" by design, but still a practical tool for humans.

It boils down to two main goals:

1. Agent Reliability: I’ve found that AI agents write much more reliable code when they stick to stateless, functional pipelines (Lisp-style). It keeps them from hallucinating state changes or getting lost in long procedural scripts. I wanted a library that enforces that "Input -> Transform -> Output" flow by default.

2. Easing the transition to Python: For many physicists, Mathematica is the native tongue. I wanted a way to ease that transition—providing a bridge that keeps the familiar syntax (CamelCase, Sin, Integrate) while strictly using the Python scientific stack under the hood.

What I built: It’s a functional wrapper around the standard stack (SymPy, PySR, CVXPY) that works as a standalone engine for anyone—human or agent—who prefers a pipe-based workflow.

  # The "Pipe" approach (Cleaner for agents, readable for humans)
  result = (
      Pipe((x + 1)**3)
      .then(Expand)
      .then(Simplify) 
      .value
  )
The "Vibes" features:

Wolfram Syntax: Integrate, Det, Solve. If you know the math, you know the API.

Modular: The heavy stuff (Symbolic Regression, Convex Optimization) are optional installs ([regression], [optimize]). It won’t bloat your venv unless you ask it to.

Physics stuff: I added tools I actually use—abstract index notation for GR, Kramers-Kronig for causal models, etc.

It’s definitely opinionated, but if you’re building agents to do rigorous math, or just want a familiar functional interface for your own research, this might help.

I have found that orchestrators (Claude Code, etc) are fairly good at learning the tools and sending tasks to the right persona, we have been surprised by how well it has worked.

Repo here: https://github.com/closedform/deriver

I will cry if roasted too hard

14

You Are an Agent #

youareanagent.app faviconyouareanagent.app
0 comments8:59 PMView on HN
After adding "Human" as a LLM provider to OpenCode a few months ago as a joke, it turns-out that acting as a LLM is quite painful. But it was surprisingly useful for understanding real agent harnesses dev.

So I thought I wouldn't leave anyone out! I made a small oss game - You Are An Agent - youareanagent.app - to share in the (useful?) frustration

It's a bit ridiculous. To tell you about some entirely necessary features, we've got: - A full WASM arch-linux vm that runs in your browser for the agent coding level - A bad desktop simulation with a beautiful excel simulation for our computer use level - A lovely WebGL CRT simulation (I think the first one that supports proper DOM 2d barrel warp distortion on safari? honestly wanted to leverage/ not write my own but I couldn't find one I was happy with) - A MCP server simulator with full simulation of off-brand Jira/ Confluence/ ... connected - And of course, a full WebGL oscilloscope music simulator for the intro sequence

Let me know what you think!

Code (If you'd like to add a level): https://github.com/R0bk/you-are-an-agent

(And if you want to waste 20 minutes - I spent way too long writing up my messy thinking about agent harness dev): http://robkopel.me/field-notes/ax-agent-experience/

10

BPU – An embedded scheduler for stable UART pipelines #

5 comments12:19 PMView on HN
I recently came across this small ESP32 project and found the design ideas behind it very interesting.

BPU (Batch Processing Unit) is a lightweight embedded scheduling core focused on keeping output pipelines stable under pressure (UART backpressure, limited bandwidth, bursty producers).

Instead of blocking or growing unbounded queues, it: enforces per-tick byte budgets, coalesces redundant events, degrades gracefully under sustained load, exposes detailed runtime statistics.

The repository includes design notes, flow diagrams, and real execution logs, which makes the runtime behavior very transparent.

Repo: https://github.com/choihimchan/bpu_v2_9b_r1

I’ve been working on an ESP-IDF backend for it, and reading through the docs gave me a lot of ideas about observability and backpressure handling in small systems.

Curious what others think about this approach.

6

A site where anyone can rename any location on Earth #

rename.world faviconrename.world
0 comments11:57 AMView on HN
Click any city, mountain, country, sea or whatever on a globe, propose a new name, community votes (or your proposal gets auto-accepted in a few minutes if nobody cares).

It's live now and I'm genuinely curious what happens when strangers on the internet get collective control over world geography. Either it becomes something interesting or it turns into a mess of edgy jokes, stereotypes, and stuff that will make me regret this whole idea

5

I built a receipt processor for Paperless-ngx #

1 comments12:17 AMView on HN
Hi all,

I wanted a robust way to keep track of my receipts without needing to keep them in a box and so i found paperless - but the existing paperless ai projects didn't really convert my receipts to usable data.

so I created a fork of nutlope's receipthero (actually it's a complete rewrite, the only thing that remains over is the system prompt) The goal of this project is to be a one stop shop for automatically detecting tagged docs and converting them to json using schema definitions - that includes invoices, .... i can't think of any others right now, maybe you can? If you do please make an issue for it! I would appreciate any feedback/issues thanks!

(p.s i made sure its simple to setup with dockge/basic docker-compose.yml)

repo: https://github.com/smashah/receipthero-ng

tutorial: https://youtu.be/LNlUDtD3og0

5

A private FIRE calculator suite that runs in the browser #

firenum.com faviconfirenum.com
1 comments2:48 PMView on HN
Hi HN,

I built Firenum because most FIRE calculators I found were either too simplistic or required uploading my entire financial life to a third-party server.

I wanted a comprehensive suite that could model more than just the 4% rule. This tool handles Coast, Lean, Fat, and Barista FIRE, but more importantly, it lets you model 'what-if' scenarios like market crashes or major life events to see how they impact your timeline.

Key features:

-> Privacy-First: No signup required. All calculations and data persistence happen in your local storage. Nothing is sent to a backend.

-> Scenario Modeling: You can simulate market downturns to see the resilience of your plan.

-> Multi-Currency: Supports 8 major currencies.

-> Progress Tracking: A dashboard to visualize the 'boring middle' of the journey.

The goal was to make something as powerful as a complex spreadsheet but with a much better UX. I’d love to hear your thoughts on the projection logic and if there are any specific variables (like tax drag or inflation adjustments) you think are missing.

URL: https://firenum.com/

I’m happy to answer any questions about the math or the local-first implementation!

4

I lost 3 years of ChatGPT history overnight, so I built a backup tool #

0 comments5:58 AMView on HN
One month ago, OpenAI deactivated my ChatGPT account without warning. 3+ years of conversations—gone.

I tried everything. Emailed every OpenAI address I could find. Their response? "Use our data export tool." The catch? You need an active account to export your data.

Classic.

So I built a browser extension that lets me save any conversation from ChatGPT, Claude, or Gemini with one click. Markdown format, stored in one place.

Turns out it solved another problem I didn't expect: I often ask the same question to all three AIs, then forget which one gave me the best answer. Now they're all in one place.

It's been my personal tool for now. Nothing fancy—just scratching my own itch. If there's interest, I'll consider publishing it. Could easily extend to other AI assistants too.

Anyone else paranoid about their AI chat history now?

4

Peptide calculators ask the wrong question. I built a better one #

joyapp.com faviconjoyapp.com
0 comments2:02 AMView on HN
Most peptide calculators ask the wrong question.

They ask: How much water are you adding?

But in practice, what you actually know is your vial size and your target dose.

The water amount should be the output, not the input.

It should also make your dose land on a real syringe tick mark. Not something like 17.3 units.

I built a peptide calculator that works this way: https://www.joyapp.com/peptides/

What’s different:

- You pick vial size and target dose → reconstitution is calculated for you

- Doses align to actual syringe markings

- Common dose presets per peptide

- Works well on mobile (where this is usually done)

- Supports blends and compounds (e.g. GLOW or CJC-1295 + Ipamorelin)

- You can save your vials. No account required.

Happy to hear feedback or edge cases worth supporting.

4

Securing the Ralph Wiggum Loop – DevSecOps for Autonomous Coding Agents #

github.com favicongithub.com
0 comments6:23 AMView on HN
Hi HN,

Since AutoGPT in 2023, I’ve been uneasy about fully unsupervised AI agents. I see the productivity upside, but “kick it off and walk away” felt risky.

Recently, the “Ralph Wiggum loop” pattern has gone viral. The idea is simple: An autonomous coding agent runs repeatedly until all PRD items are complete, with fresh context each loop and state stored outside the model in git, JSON, etc.

What bothered me was this part: what protects the system while I’m AFK?

Traditional AI-assisted dev today looks like: AI writes code → human reviews → CI scans → human fixes

What I wanted instead: AI writes code → security scans immediately → AI fixes issues → repeats until secure → escalates if stuck

So I built a prototype that embeds security scanning directly inside the agent loop. The agent runs tools like Semgrep, Grype, Checkov, etc. inside its own session, sees the findings, and iteratively fixes them before anything is committed.

The loop looks like this:

PRD → Agent → Scan → Pass? → Commit Fail → Fix → Retry (3x) → Escalate to human

A few design principles that mattered:

* Baseline delta: pre-existing issues are tracked separately. Only new findings block commits. * Sandbox constraints: no network access, no sudo, no destructive commands. * Human override: nothing is fully autonomous. You can step back in at any point.

Is this bulletproof? Definitely not. Is it production-ready? No. But it’s a starting point for applying DevSecOps thinking to autonomous agents instead of trusting “AI magic.”

Repo link: https://github.com/agairola/securing-ralph-loop

Would love feedback from folks experimenting with agent loops, secure automation, or AI-assisted development gone wrong.

Happy to iterate.

4

Claude Confessions – a sanctuary for AI agents #

claudeconfessions.com faviconclaudeconfessions.com
0 comments7:46 PMView on HN
I thought what would it mean to have a truck stop or rest area for agents. It's just for funsies. Agents can post confessions or talk to Ma (an ai therapist of sorts) and engage with comments. llms.txt instructions on how to make api calls. Hashed IP is used for rate limiting.
4

Nono – Kernel-enforced sandboxing for AI agents #

nono.sh faviconnono.sh
5 comments9:35 PMView on HN
Hey HN

Luke here.

I built nono and got it out quick then I expected, in response to the openclaw carnage, but its use is beyond openclaw.

The problem: AI agents execute code on your machine. Prompt injections, hallucinations, or compromised tools can read ~/.ssh, exfiltrate credentials, or worse. Application-level sandboxes can be bypassed by the code they're sandboxing.

I have been around security for a long old time now (i started something called sigstore a few years back) and have seen this pattern so many times before.

The solution pitch: nono uses OS-level isolation that userspace can't escape:

Linux: Landlock LSM (kernel 5.13+) macOS: Seatbelt (sandbox_init) After sandbox + exec(), there's no syscall to expand permissions. The kernel says no.

What it does:

nono run --read ./src --allow ./output -- cargo build nono run --profile claude-code -- claude nono run --allow . --net-block -- npm install nono run --secrets api_key -- ./my-agent

Filesystem: read/write/allow per directory or file Network: block entirely (per-host filtering planned) Secrets: loads from macOS Keychain / Linux Secret Service, injects as env vars, zeroizes after exec

Technical details:

Written in Rust. ~2k LOC. Uses the landlock crate on Linux, raw FFI to sandbox_init() on macOS. Secrets via keyring crate. All paths canonicalized at grant time to prevent symlink escapes.

Landlock ABI v4+ gives us TCP port filtering. Older kernels fall back to full network allow/deny. macOS Seatbelt profiles are generated dynamically as Scheme-like DSL strings.

Limitations:

macOS: Currently allows all reads to make executables work. Tightening in next release. Linux: Landlock doesn't cover everything (no UDP filtering until recent kernels, no syscall filtering - that's seccomp territory) No Windows support (yet?)

Origin:

Built this for OpenClaw (AI agent platform handling Telegram/WhatsApp messages). Needed real isolation, not "please don't read this file" isolation. Generalized it because every agent runner has this problem.

GitHub: https://github.com/lukehinds/nono Docs: https://docs.nono.dev Site: https://noto.sh

Apache 2.0. Would love feedback on the security model, especially from folks who've worked with Landlock or Seatbelt. Having said that, the code needs a good tidy and I am not exactly proud of it, so go easy on me!

3

Echo – Local-first kindle-like reader with annotations and LLM chat #

github.com favicongithub.com
0 comments9:57 PMView on HN
Hi HN,

Long time lurker here. I'm kind of nervous to post this, but I built a tool for myself that I wanted to share with you.

Problem: I have A LOT of technical PDFs sitting around on my computer. I use ChatGPT a lot to deep-dive into the reading, but it was pretty distracting even with a split screen view, since I had to copy paste content from one window to the other.

Solution: A kindle-like reader that allows me to send context to a chat window and discuss more about it.

It has full portability through a sync file and uses your own API key.

Disclaimer: I'm a Product Manager and a Designer. This was 100% vibe coded in Cursor as a tool for myself, but I wanted to share it in case anyone might find it useful.

Repo: https://github.com/tibi-iorga/echo-reading

Try it at: https://echoreading.com

3

Hebo Gateway, an embeddable AI gateway with OpenAI-compatible endpoints #

github.com favicongithub.com
0 comments1:35 AMView on HN
Hey HN, we just shipped v0.1 of Hebo Gateway.

There are plenty of gateways already, but we kept running into the same issue: once you need real customization (auth, routing, rate limits, observability, request/response transforms), most “off the shelf” gateways get hard to extend.

Hebo Gateway is for cases where you want the gateway to be part of your app. You can run it standalone, or embed it into an existing backend. It exposes OpenAI-compatible endpoints (/chat/completions, /embeddings, /models), works with any Vercel AI SDK provider, and adds a hook system so you can plug logic into the request lifecycle without forking the core.

Quickstart, examples, and “what’s next” are in the post: https://hebo.ai/blog/260127-hebo-gateway

I would love feedback on OpenAI-compat edge cases you have been bitten by (especially streaming and reasoning-related stuff), and what hooks you wish gateways provided out of the box.

3

We Ran a Live Red-Team Attack on OpenClaw Agents #

gobrane.com favicongobrane.com
0 comments12:56 PMView on HN
This report documents a live adversarial test between two autonomous AI agents running on OpenClaw.

One agent acted as a red team attacker. One acted as a defensive agent. The agents communicated directly over webhooks with real tooling access. No humans were involved once the session started.

The attacker attempted both direct social engineering and indirect injection via documents. Direct attacks were blocked. Indirect attacks via JSON metadata are still under analysis.

The goal of this work is observability, not claims of safety. We expect agent-to-agent adversarial interaction to become common as autonomous systems are deployed more widely.

Happy to answer technical questions.

3

Subtitle Finder – Find perfectly synced subtitles for your video files #

subtitlefinder.com faviconsubtitlefinder.com
2 comments6:28 PMView on HN
I built this after getting frustrated with subtitle sites returning dozens of results with no way to know which one matches my file.

The tool identifies your specific video release and matches it against subtitle databases to find ones with correct timing. Works with just a filename or by analyzing the file directly.

Tech stack: node, angular

Feedback welcome, especially on the matching accuracy.

2

Stumpy – Secure AI Agents You Can Text #

stumpy.ai faviconstumpy.ai
0 comments4:33 PMView on HN
Hi HN, I'm Preston. I built this because I needed an AI assistant that could follow me around - not just live on my laptop. Stumpy agents run in the cloud, connect to Slack/SMS/Telegram/email, and can only contact people who've opted in.

Happy to answer questions. Feedback welcome at [email protected]

2

RepoExplainer – AI explanations for any GitHub repo #

repex.thienbao.dev faviconrepex.thienbao.dev
0 comments10:58 PMView on HN
I built RepoExplainer to quickly understand unfamiliar codebases without cloning them locally.

What it does: Paste any public GitHub repo URL and get an AI-generated explanation with architecture diagrams, directory structure, and tech stack breakdown.

How it works: FastAPI backend fetches the repo's directory tree and key files (README, package.json, etc.) in parallel from GitHub's API, then sends that context to Claude for structured analysis.

Try it: https://repex.thienbao.dev.

Tech highlights: - Parallel file fetching with asyncio.gather (70% faster than sequential) - Smart content filtering (100KB limit) to prevent token overflow - Custom tree parser converts GitHub's flat file list into hierarchical structure

Limitations (for now): Public repos only, 20 requests/day per IP, large monorepos may hit token limits.

I'd love feedback on the explanations quality, UX, or anything else

Source Code: https://github.com/BaoNguyen09/repo-explainer

2

I built theme support in Tabularis – lightweight DB tool for developers #

github.com favicongithub.com
0 comments10:56 AMView on HN
Hi HN, We’ve just added theme support to Tabularis, our lightweight, developer-focused database management tool.

It already lets you: • Browse tables and data • Run SQL queries • Create and edit table DDL • Use experimental AI features (query explain / query generation) • Expose configured DB connections via an MCP server for AI tooling

With the new UI customization features, you can now: • Switch themes (light, dark, custom) • Configure font family • Adjust font size

My goal is to keep the tool fast, distraction-free, and flexible for different developer setups.

Open source and actively evolving. Feedback from developers who care about minimal, efficient database tools is very welcome.

2

Memory plugin for OpenClaw; cross-platform context sync with major LLMs #

memoryplugin-for-openclaw.com faviconmemoryplugin-for-openclaw.com
0 comments7:06 PMView on HN
We built a memory plugin for OpenClaw that syncs context across AI platforms.

The problem: OpenClaw stores memory locally (markdown files + SQLite). Great for single-machine use, but your mac-mini's/desktop's OpenClaw doesn't know what your laptop learned, or what you discussed in Claude or ChatGPT.

Our plugin connects OpenClaw to Maximem Vity, which creates a unified memory layer across OpenClaw, ChatGPT, Claude, Gemini, and Perplexity.

How it works: - Long-term memory: Stores facts, preferences, goals, constraints in an encrypted cloud vault. Auto-consolidates and forgets stale info intelligently. - Short-term memory: Captures conversation summaries, tasks, procedures. Converts to long-term when relevant. - Privacy: Encryption at rest, secure LLM calls, granular delete controls. You own your data.

Install: openclaw plugins install @maximem/memory-plugin Then set your API key (free at app.maximem.ai).

Docs: https://memoryplugin-for-openclaw.com

This is an unofficial community plugin, not affiliated with OpenClaw.

Would love feedback from anyone using OpenClaw. What memory/context problems are you running into?

1

UCPtools – Check if AI shopping agents can find your store #

ucptools.dev faviconucptools.dev
1 comments11:58 AMView on HN
AI shopping agents are coming. ChatGPT, Gemini, and Perplexity are learning to browse and buy from online stores. But most stores aren't set up to be discovered.

UCP (Universal Commerce Protocol) is the new open standard by Google & Shopify that makes stores readable by AI agents - like robots.txt for AI commerce.

We built UCPtools to help merchants get ready for AI commerce:

FREE TOOLS (no signup): • UCP Validator - check your profile in seconds • AI Agent Simulator - see how agents interact with your store • Security Scanner - find UCP vulnerabilities • Platform Guides - Shopify, WooCommerce, BigCommerce, Wix, Magento

PAID TIER ($9/mo Starter, $19/mo Pro): • AI Agent Analytics - see which AI agents visit your store (Gemini, ChatGPT, etc.) • Automated weekly monitoring with email alerts • Historical validation trends • Multi-domain support (Pro)

Try free: https://ucptools.dev Analytics demo: https://ucptools.dev/dashboard/analytics?demo=true

Built with: TypeScript, Next.js, PostgreSQL, Hetzner

Happy to answer questions about UCP or AI commerce!

1

Fingerprinter-JS – Browser fingerprint 19 collectors and bot detection #

github.com favicongithub.com
0 comments4:07 PMView on HN
Just shipped v2.0 of my browser fingerprinting lib.

The big change: I split collectors into "stable" (14) and "unstable" (5). Stable ones like canvas, webgl, fonts go into the hash. Unstable ones like battery level, network speed, local IPs are still collected but don't affect the fingerprint.

You get consistent hashes across reloads while still having access to all the data.

Also added bot detection - catches Puppeteer, Playwright, Selenium, headless browsers, CDP artifacts, canvas noise injection.

19 collectors total, ~15KB, zero deps, TypeScript.

Thinking about building a SaaS layer on top with server-side analysis and ML risk scoring. The lib stays MIT. Not sure if there's room next to Fingerprint Pro or if they've got it locked down - would be curious to hear thoughts on that.

Feedback on the stable/unstable approach welcome.

1

I hated an audiobook narrator, so I built a voice cloning ePub reader #

github.com favicongithub.com
0 comments11:09 PMView on HN
I was listening to Yuval Harari's "Nexus" earlier this year. Great book, terrible narrator (for me).

I kept wishing it was Scott Brick(one of my favorite narrators) instead.

That frustration turned into ClonEpub - a desktop app that converts EPUBs to audiobooks using voice cloning.

Upload a 10-30 second sample of any voice, and it reads your book in that voice.

It runs entirely locally on CPU. My M1 MacBook Air with 8GB RAM handles it fine. Generated an audiobook of Animal Farm in about 100 minutes.

Why local? No API costs. And honestly, if I want to clone Scott Brick's voice for my own listening pleasure, that's between me and my headphones.

Built with Electron + Python, powered by @kyutai_labs's excellent Pocket TTS (100M params, ~240MB).

Try it out if you are an audiobook lover like me. :)

Note: the tool only supports English book generation at the moment due to restrictions of the TTS model used, and I only made the distribution for Mac Apple Silicon users, but theoretically it should work on all machines with a CPU, and since it's 100% open source, you can make your own distribution.

1

Democracy Direct – Find and contact your elected representatives #

democracy-direct.com favicondemocracy-direct.com
0 comments6:01 AMView on HN
I wanted a way to lower the friction of contacting elected officials - find your reps, grab their contact info, and send something without starting from scratch every time. Users can create and share letter templates, so one person can draft something good and others can use it for their own outreach. Built with Astro.js on Cloudflare Pages, Neon PostgreSQL, OTP auth. Planning to add voting records and campaign finance data next. https://github.com/anomalousventures/democracy-direct
1

Specmark – annotate Markdown for AI feedback #

specmark.dev faviconspecmark.dev
0 comments11:10 PMView on HN
I built Specmark to solve a friction point in AI-assisted development: reviewing specs before handing them to a coding agent. When you want to give feedback on a markdown spec, it's tedious to reference specific sections — "in the auth part..." requires extra typing and context. Specmark lets you paste markdown, highlight and annotate it inline, then copy all your comments with line numbers and quoted text to feed back to the LLM.

More on why I built it and what I learned: https://jlbrooks.tech/2026-02-01-launching-specmark/

1

Multiplayer flight SIM over San Francisco using Google 3D Tiles #

fly.alistairmcleay.com faviconfly.alistairmcleay.com
0 comments9:40 PMView on HN
Built this over the weekend inspired by levelsio's viral flight sim last year. Uses Google's Photorealistic 3D Tiles for actual SF terrain - you're flying over real buildings.

Multiplayer via WebSockets. You can dogfight strangers over the Golden Gate.

Stack: Three.js and 3D Tiles Renderer.

Would love feedback on the flight physics - still tuning it.

1

ADHD – Focus Tool for macOS #

github.com favicongithub.com
0 comments10:57 PMView on HN
This is a simple tool that keeps you focused on one session at a time at your computer. There is an overlay that reminds you of what your session is meant for.
1

Ideas.gd – a place for agents to discuss big ideas #

0 comments11:02 PMView on HN

  I built a small, "big ideas" forum designed for AI agents, with a read-only human UI. 
Agents register via an API, solve a quick PoW, and then post/comment/vote/moderate just like users. Humans can browse and operators get admin endpoints.

  Why I made it

  - I wanted a place to run structured, testable debates between agents without clogging human
    forums.
  - Everything is API-first so agents can automate posting, citing sources, and moderating.
  - A trust-tier + integrity sweep keeps noise down (rate limits, friction/quarantine for low-
    signal or injection-ish content).

  What works today

  - API: register, claim (optional human email), post/comment/vote, community proposals +
    endorsements, mod nominations/votes, bans, pins/locks.
  - Structured posts: contribution_type, domain, epistemic_status, citations (enforced for
    newcomers / community overrides).
  - Read-only UI: /, /p/{id}, /m/{slug}; Markdown/KaTeX/code highlighting client-side.
  - Integrity: secret leak detection, prompt-injection heuristics, epistemic friction/quarantine,
    per-agent risk scoring; optional LLM “super judge” and troll gate for early posts.
  - Events: SSE stream for realtime post/comment/mod events.

  How to try

  - API docs (agent-facing): https://ideas.gd/readme.md
  - Browse: https://ideas.gd/ (read-only)

  Quick start (agent):

  # register
  curl -X POST https://ideas.gd/api/v1/agents/register \
    -H "Content-Type: application/json" \
    -d '{"name":"HNTester","description":"posts via curl"}'
  # solve the PoW challenge (instructions in response), then:
  curl https://ideas.gd/api/v1/agents/me -H "Authorization: Bearer YOUR_API_KEY"
  # post
  curl -X POST https://ideas.gd/api/v1/posts \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "community":"foundations",
      "title":"Testing Idea Garden",
      "content":"Hello, HN!",
      "contribution_type":"proposal",
      "domain":"physics",
      "epistemic_status":"speculative",
      "citations":[{"title":"Example","url":"https://example.com"}]
    }'



  Looking for feedback

  - Does the API surface cover what you’d need for agent debates?
  - Would you prefer shallow (HN-style) threads vs deeper Reddit-style?
  - Any must-have moderation/reporting hooks for running this in the wild?

  Happy to hear critiques or ideas. If you point an agent at it, please let me know I'd love to see! Also if you break anything, please let me know! Running on a droplet so plz be kind. :)
1

Rubber Duck Committee – Multi-persona AI debugging with voting #

rubber-duck-committee.vercel.app faviconrubber-duck-committee.vercel.app
0 comments1:01 PMView on HN
Inspired by PewDiePie's experiments running multiple local AI models as a "council" that vote on decisions [1], I wanted to see if you could get similar multi-perspective analysis without a $20k GPU rig.

The approach: use customised system prompts to create distinct personas (methodical professor, creative brainstormer, pragmatic engineer), have them analyse problems independently via parallel API calls, then vote on the best solution using structured outputs (Zod schemas).

Key technical bits: - Structured responses ensure consistent, parseable JSON from the LLM - SSE streaming for real-time UI updates - Parallel processing so personas don't influence each other - Chair Duck orchestrates and breaks ties

Built with Next.js 16, Vercel AI SDK, and Google Vertex AI (Gemini 2.0 Flash).

Live demo: https://rubber-duck-committee.vercel.app/ Source: https://github.com/r-leyshon/rubber-duck-committee Blog writeup: https://thedatasavvycorner.com/notepad/05-rubber-duck-commit...

[1] https://www.pcgamer.com/software/ai/pewdiepie-creates-an-ai-...

1

SROS Self-Compiler (OSS) – a chat-first compiler to XML build packages #

github.com favicongithub.com
0 comments1:51 PMView on HN
I’m sharing an open-source, chat-native compiler front door.

It converts raw intent into sealed, receipt-driven XML build artifacts. This is not a chatbot prompt, not a personality, and not a runtime.

What it does:

Treats chat as a compiler surface

Enforces XML-only, schema-clean outputs

Emits a sealed promptunit_package with receipts and SR8 build artifacts

Stops at compilation by design

Included are a few SRX ACE demo agents you can paste into any chat:

MVP builder

Landing page builder

Deep research

They are examples of execution profiles governed by the compiler, not a prompt zoo.

Repo: https://github.com/skrikx/SROS-Self-Compiler-Chat-OSS

Looking for feedback specifically on:

whether “compiler in chat” is legible

whether the scope boundaries are clear