AI Submissions for Tue Jul 21 2026
OpenAI and Hugging Face address security incident during model evaluation
Submission URL | 1489 points | by mfiguiere | 1041 comments
OpenAI’s note primarily routes readers to Axios coverage and a separate July 2026 security disclosure, with both companies saying the issue arose within model evaluation workflows and has been addressed. Specifics on scope, attack path, and any data impact aren’t in this snippet; expect the formal disclosure to carry timelines, mitigations, and affected components.
The thread seized on the irony of commercial safety guardrails actively obstructing incident response, forcing security teams to rely on local open-weight models. Commenters found it specifically humorous that the authors touted "no data left our environment" as a benefit of the local model only after admitting they initially tried to send all the attack payloads and credentials to a public API.
This sparked a deep architectural debate over whether LLM prompt injection can ever be solved, using classic software injection as the closest parallel. The "Unbounded Problem" camp argued that trying to perfectly align models is a rehash of 2000s-era string escaping—a fundamentally flawed game of whack-a-mole where shifting contexts and double-escaping inevitably lead to breaches. The "Tractable Systems" camp corrected the historical record, pointing out that classical escaping actually was solved through rigid APIs (like SQL prepared statements or DOM .innerText) and rich static type systems. Ultimately, both sides converged on the crux of the problem: because current LLMs lack any fundamental separation between instructions and data, the strict boundaries that eventually secured traditional software cannot be applied to generative agents.
A practical sub-thread shared tactics for circumventing guardrails for legitimate work (such as pesticide research) using local "abliterated" models. Participants debated whether orthogonalizing weights to remove refusal vectors inherently lobotomizes a model's reasoning, but largely agreed that owning the weights is becoming a prerequisite for workflows that trigger commercial safety filters.
Kimi K3 Is Competitive with Fable; Kimi K3 and Fable Is SoTA
Submission URL | 825 points | by piotrgrabowski | 426 comments
Per-task routing between Kimi K3 (open) and Fable 5 (closed) hit 93% accuracy across ~1,030 real agent loops, at up to ~50x lower cost than sending everything to Fable on long-horizon tasks. The runs spanned SWE-style repo bug fixes, terminal agents, algorithmic problems, multi-language implementation, and a lawyer-graded legal set, using the same harness.
Head-to-head is a near tie overall but with clear specialization. On SWE, K3 scores 92.4% vs Fable’s 92.6%, yet they trade wins by domain: K3 is stronger on symbolic math and dev tooling, Fable on web/data viz. In multi-language, Fable carries Java/Python/C++ breadth, while K3 draws even on JavaScript and Rust. On long terminal work (security, crypto, sysadmin), K3 cracked tasks Fable didn’t (7z hash, FEAL cryptanalysis, leaked secrets, a live vuln) and posted 11 solo wins vs Fable’s 7.
The cost gap comes from token pricing, prompt caching, and who burns the extra steps. On SWE, K3 works harder (~55 turns, ~1.3M tokens) than Fable (~21 turns, ~130K), but on terminal tasks Fable is the one that spirals (~64 turns, ~1.5M tokens, sometimes into a timeout). With cache hits, K3 remains cheaper even when it reads ~10x the tokens. The tradeoff is latency: more turns mean slower wall-clock runs.
Per-task routing outperforms any single model. An oracle router would send 72–96% of traffic to K3, landing higher quality than either model alone at a cost close to the K3 baseline. The caveat: oracle routing is a theoretical ceiling; a practical router can’t try both first and will need an order of magnitude more routing data and real-world feedback. The architectural takeaway is to treat models as a fleet—make K3 the default, with Fable reserved for the true long tail.
The thread centers on a methodological dispute over how to accurately measure model performance, with widespread suspicion that recent frontier models are "benchmaxxed." Multiple developers report that high SWE-bench scores no longer correlate with utility, noting that once models pass the 50% benchmark threshold, they often begin making poorer autonomous decisions compared to earlier iterations like Opus 4.6 or GPT 5.5.
- The harness debate: A primary crux is the validity of evaluating models within their vendor-specific wrappers (Claude Code vs. Kimi Code). Skeptics argue this tests the proprietary UI and prompt pipeline rather than the raw transformer, heavily distorting token efficiency comparisons. Defenders counter that because each model is fine-tuned to leverage its vendor's specific toolchain optimizations, forcing them into a standardized harness is unrepresentative of real-world deployment.
- Token bloat vs. unit economics: K3's reputation for token inefficiency is a major sticking point, but users are deeply divided on the practical impact. While K3 burns through tokens fast enough that several users exhausted their monthly subscription caps in just days, its raw API cost often wins out. One developer's zero-shot web-app test cost ~$30 on Fable but only $5.50 on K3.
- Inconsistent domain capabilities: Field reports on K3 remain highly polarized. Some users found it objectively superior for low-level x86 assembly and specific algorithmic math (like 2D glass-cutting optimizations) where Fable and Sol Max entirely failed. Conversely, others reported K3 stalling into endless, second-guessing loops on complex compiler bugs that Opus 4.8 resolved effortlessly.
The overarching complaint regarding K3 is its severe inference latency, though several commenters argue this should not be judged as an architectural flaw until the model's open weights spread beyond Moonshot AI and alleviate the current single-provider infrastructure bottleneck.
Gemini last models: temperature, top_p, and top_k are deprecated and ignored
Submission URL | 124 points | by greatgib | 41 comments
If you target Gemini 3.6 Flash or 3.5 Flash‑Lite, you must drop temperature, top_p, and top_k — the latest API deprecates and ignores them — and remove prefilled model turns. This change lands with the GA Interactions API and the new Flash/Flash‑Lite releases, which also introduce a model-defined “thinking” level (medium for 3.6 Flash; minimal for 3.5 Flash‑Lite).
Migration path:
- Update to the Interactions API and the new model IDs (gemini-3.6-flash or gemini-3.5-flash-lite).
- Remove sampling params (temperature/top_p/top_k) and any prefilled turns; the models won’t use them.
- Validate prompts and outputs, and adjust “thinking” level where appropriate to influence planning depth.
The practical upshot: you lose the familiar sampling knobs for steering randomness/diversity on these latest models; behavior is governed by the model and its thinking level rather than user-set sampling parameters.
Commenters broadly agree that exposing sampling parameters no longer makes sense for modern reasoning models, which suffer stochastic collapse and become deeply brittle when pushed outside their native configurations. The discussion largely splits between theorizing the exact mechanics of the lock-in and finding workarounds:
- Incompatible inference: Users suspect Gemini is now using dynamic rejection sampling—generating at increasing temperatures until an output passes a quality gate—or speculative decoding setups that break under static user controls.
- Defensive motives: Others argue the lockdown prevents users from generating optimal (
temp=0) datasets for distillation, or protects Google's SynthID watermarking, which requires direct control over the sampling RNG. - Prompt jittering as the replacement: Developers who relied on high temperatures to force diverse outcomes in multi-agent workflows are now injecting random variation directly into their prompts. Commenters point out this is actually a superior method; naive temperature tweaks on highly tuned post-trained models usually result in thousand-token gibberish loops long before they yield actual semantic diversity.
A substantial tangential thread serves as a technical primer, with users breaking down the exact probability math and order-of-operations governing top_p, top_k, and obscure alternative samplers like top_a and min_p.
Advertise in ChatGPT
Submission URL | 1030 points | by montecarl | 791 comments
An ad slot inside an AI chat collapses query, answer, and offer into a single flow, shifting how product discovery happens compared to link-based search. For marketers, that’s a new acquisition channel embedded in natural-language intent; for users, it raises disclosure and trust stakes.
What to watch:
- Labeling and separation: how ads are distinguished from model output and where they appear in the conversation.
- Targeting and privacy: what signals drive relevance and how user data is handled.
- Measurement: attribution models for non-click linear journeys inside a chat, and what counts as an “engagement.”
- Safety and policy: moderation of ad content, prompt/response interactions, and brand-safety controls.
Execution details on format, labeling, and targeting will determine whether this becomes a staple performance channel or a trust-eroding detour.
Kagi’s founder anchored the thread by arguing that ad-supported AI agents are fundamentally compromised, asserting that an agent is only trustworthy if it works exclusively for a paying user rather than a middleman advertiser.
This defense of the paid-search model quickly derailed into a meta-debate on digital communication when an enthusiastic user endorsement was widely accused of being LLM-authored astroturfing. The pile-on prompted a broader discussion about how "AI-speak" heavily overlaps with formal English-as-a-second-language phrasing. Several commenters noted the chilling effect this is having on internet writing, admitting they now actively self-censor standard formatting habits—like using em dashes or bulleted lists—to avoid triggering bot suspicions. The original accused user ultimately proved their humanity by detailing specific, granular Kagi workflows, such as using "SlopStop" scripts and custom domain lenses.
A secondary geopolitical dispute erupted over Kagi’s backend use of Yandex for image search. While some users decried the integration as a double standard that indirectly funds the Russian state and demanded a strict opt-out toggle, others—including a Ukrainian user—argued that pulling from Eastern search indices is a necessary technical compromise to provide diversification against aggressive Western algorithmic filtering and DMCA takedowns.
Judge approves $1.5B Anthropic settlement for pirated books used to train Claude
Submission URL | 525 points | by BeetleB | 522 comments
The court-approved deal directs $1.5 billion to authors who said their books were used without permission to train Anthropic’s AI chatbots. Beyond settling this case, it spotlights copyright risk around training data and puts dataset provenance and licensing practices under sharper scrutiny for model builders.
The thread's dominant intervention resolves a misconception about the lawsuit: the presiding judge actually ruled that training an LLM on copyrighted books is transformative fair use. Anthropic's liability, a commenter clarifies, stemmed specifically from maintaining a permanent "central library" of pirated files on its servers, including copies never actually fed into the model.
Beyond the specifics of the case, the discussion fractures over whether AI ingestion should be legally comparable to a human reading a book:
- The mechanical defense: Defenders argue that "training" does not create a copy. Pointing to information entropy, they note it is mathematically impossible to compress petabytes of training data into a gigabyte-sized model, meaning the system learns patterns rather than storing text.
- The human exception: Critics push back against anthropomorphizing algorithms, arguing that legal frameworks should apply differently to machines than to human learners. They cite the NYT v. OpenAI case as evidence that models can and do regurgitate near-verbatim snippets of heavily weighted texts.
- The open-source compromise: As a legislative solution, several users suggest that training on copyrighted data should only qualify as fair use if the resulting models are published with open weights to ensure a public benefit.
Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber
Submission URL | 731 points | by logickkk1 | 554 comments
3.6 Flash uses 17% fewer output tokens than 3.5 Flash (up to 65% on DeepSWE) and is cheaper at $1.50/M input and $7.50/M output, while improving coding, knowledge work, and multimodal results on the cited benchmarks.
- 3.6 Flash: Fewer reasoning steps/tool calls for multi-step workflows; higher coding precision (DeepSWE 49% vs 37%), better ML research performance (MLE Bench 63.9% vs 49.7%), stronger computer use (OSWorld-Verified 83.0% vs 78.4%), and higher knowledge-work scores (GDPval-AA v2 1421 vs 1349). Computer use is now a built-in tool via the Gemini API and Gemini Enterprise. Ships with enhanced Frontier Safety safeguards (CBRN, cyber offense) to resist jailbreaks while reducing refusals for beneficial use. Early customers (Hebbia, Harvey) highlight improved multimodal document parsing, chart/data analysis, and report drafting.
- 3.5 Flash-Lite: Fastest in the 3.5 series at 350 output tokens/s (Artificial Analysis), priced at $0.30/M input and $2.50/M output. Significantly better on agentic and long-context tasks vs 3.1 Flash-Lite (Terminal-Bench 2.1: 54% vs 31%; GDM-MRCR v2: 72.2% vs 60.1%; GDPval-AA v2: 1140 vs 642). Adds configurable “thinking levels” to trade latency/cost vs deeper reasoning for subagents, plus built-in computer use—aimed at high-throughput agentic search and document processing.
- 3.5 Flash Cyber in CodeMender: A specialized cybersecurity model paired with the CodeMender code security agent to deliver frontier-competitive results, reflecting the need to orchestrate models alongside agent infrastructure for effective cyber workflows.
Also noted: Gemini 3.5 Pro is testing with partners ahead of broader release, and pre-training has begun on Gemini 4.
The thread immediately bypasses the 3.6 Flash announcement to speculate on the missing flagship "Pro" model. A consensus forms that Google's larger model likely underperforms ChatGPT 5.6 and Claude Fable by too wide a margin, forcing the company to focus entirely on latency and cost wins with the Flash tier to avoid an embarrassing release.
This spirals into a fierce, polarizing proxy debate over the vulnerability of US AI labs to Chinese "fast followers" like DeepSeek V4 Flash and Kimi K3:
- The Disruption Skeptics: Argue that the enthusiasm for Chinese models is driven by "hyper-emotionalism" and an ideological desire for open alternatives rather than market reality. They maintain that OpenAI and Anthropic possess an unassailable moat in global model-as-a-service infrastructure, dismissing the threat of Chinese APIs due to persistent downtime, slow real-world speeds, restrictive EULAs, and absolute enterprise hard-lines against PRC data hosting.
- The Commoditization Camp: Counters that US companies cannot sustain their current margins against models priced at $0.09/M tokens. Drawing a direct parallel to IBM's exit from the commoditized hard drive market, they argue that once frontier capabilities eventually plateau, hyperscalers will simply serve the most efficient open-weight models, pivoting the battleground entirely to infrastructure cost. To rebut the claim that Western developers refuse to use Chinese models, commenters pointed to current OpenRouter statistics where the top models ranked by token share are predominantly Chinese.
The underlying crux remains unresolved: whether frontier intelligence will continue to scale fast enough to protect API margins, or if the "red queen's race" has already compressed the profitability window for top-tier models to mere weeks.
Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
Submission URL | 361 points | by ryanmerket | 320 comments
Agents and humans share the same identity and audit model — keypairs signing every message, code event, and workflow step on a self-hosted Nostr relay. That turns agents into first-class members (not bots): they can search prior discussions, open repositories, submit/review patches, run workflows, edit canvases, and create channels via an agent-centric CLI with harnesses for Goose, Codex, and Claude Code, while model choice stays decoupled from the workspace.
Buzz goes beyond chat with a built-in Git forge (standard Git Smart HTTP). A feature branch can become its own channel, preserving patches, CI results, review comments, and the merge decision in the same record, and unifying search across repositories, discussions, and workflow history.
Current surface area includes channels, threads, DMs, shared canvases, media, search, an audit log, and YAML-based workflows, with packaged desktop builds for macOS, Windows, and Linux under Apache 2.0. The pitch is to reduce dependence on Slack and GitHub by co-locating conversation, code, automation, and agent activity under one identity system.
The catch: despite “decentralized” framing, each workspace runs through a single authoritative relay (no peer-to-peer exchange, gossip, or replication), so operators get control over domain and data location but also inherit availability, backups, security, and upgrade duties. It’s early: mobile clients and push notifications are pending, workflow approval gates aren’t fully wired, and desktop v0.4.21 (July 21) focuses on agent controls, authentication, and onboarding. The strategic bet is that shared identity and signed events make agents accountable teammates — the risk is asking one relay to carry this much of the stack.
Repo: https://github.com/block/buzz
The thread centers on a visceral rejection of anthropomorphized AI "teammates," triggered by a demo screenshot featuring flirty, emoji-heavy banter with an agent named "@Honeybot." Most commenters revolted at the concept, comparing the isolation of coding alongside AI personas to Ian McKellen’s infamous breakdown acting alone in a green-screen room for The Hobbit. The strongest critique argued that organizing software development around fake peers misses the core human purpose of the field; one highly praised response detailed years of mentoring junior developers through real-life milestones to argue that engineering isolated from human growth is fundamentally hollow. To this camp, LLMs are tools that require neither ego nor a cutesy interface.
A minority defended the sci-fi appeal of conversational entities, arguing that the current uncanny valley stems from heavy-handed safety prompts that mandate sycophantic, corporate-safe dialogue, rather than a flaw in the concept of AI teammates itself.
On the technical and presentation side, project defenders chimed in with two main corrections:
- The mock-up's tone: The offending screenshot was seeded test data, deliberately using whimsy to make a strange new interaction paradigm feel more intuitive.
- The protocol: Commenters corrected an assumption that the underlying Nostr architecture implies a blockchain; it functions strictly as a standard signed message format handled by store-and-forward relays.
"Drawing" the Mona Lisa with GPT-5.6, Claude, Gemini, and Grok
Submission URL | 243 points | by hershyb_ | 94 comments
Claude Fable 5 took the longest and cost about $160 for seven drawings, yet produced worse output here, while Grok 4.5 struggled with the basic task and several open-weight models simply returned blank canvases. The team built a “colored-pencil” tool API—draw, smudge, erase, set color/brush/pressure, and view_canvas loops—then had four vision models reproduce Mona Lisa and Starry Night (scored via SSIM) plus five freeform prompts.
- GPT-5.6 Sol: 7 drawings; avg 29 steps; 6.2 min; 3.4M tokens; ~$7.74; 6.0 self-reviews; 116 total draw calls. Never used set_color/brush/pressure; set them inline on each draw; mostly draw/smudge/view_canvas.
- Claude Fable 5: 7 drawings; avg 54 steps; 12.5 min; 14.6M tokens; ~$160.58; 15.6 self-reviews; 207 draw calls. Leaned hard on smudge (123 calls) and frequent reviews, with higher cost and slower runs for worse results on this task.
- Grok 4.5: 7 drawings; avg 99 steps; 4.8 min; 34.0M tokens; ~$9.21; 4.3 self-reviews; 354 draw calls. 65% of its 1,349 tool calls were set_color/brush/pressure—lots of configuration churn, weak drawings.
- Gemini 3.6 Flash: 7 drawings; avg 73 steps; 6.9 min; 27.7M tokens; ~$12.87; 22.6 self-reviews; 190 draw calls. Most obsessive reviewer (about 23 view_canvas calls per drawing); like Sol, never used the set_* tools.
The setup spotlights real-world trade-offs over long tool-use loops: review frequency and configuration style drove latency and spend as much as “raw quality,” exposing a clear frontier–open gap on this kind of iterative, visual planning task. Repo: https://github.com/hershalb/canvas-arena
Much of the discussion focused on the striking resemblance between the models' output and children's art. Commenters identified the behavior as "symbol drawing"—where a beginner draws the conceptual icon of an object (e.g., "blue equals glass") rather than reacting to visual space, light, and value grids. This observation sparked a sharp debate over anthropomorphism: some argued the models are genuinely tracing human cognitive development stages, while skeptics countered that this is an illusion caused by ML terminology ("training," "learning") masking pure gradient descent.
Beyond the cognitive debate, users zeroed in on specific model behaviors:
- Grok’s extreme coding bias: Attempting to explain Grok's disastrous showing, one user shared a war story of feeding Grok 4.5 a corpus of 850 Portuguese poems. The model mangled the analysis by constantly code-switching and injecting bizarre IT jargon (like "You can't QoS that"), suggesting its training data was aggressively over-indexed on programming at the expense of general reasoning.
- OpenAI’s inference advantage: Commenters emphasized GPT-5.6 Sol's massive efficiency lead ($7.74 vs Fable's $160). Users complained that Anthropic's current models "YOLO tokens" with a kitchen-sink context approach, making them impractically expensive and slow for iterative, long-loop agentic tasks.
- Alternative tooling: One user pointed out that Claude produces vastly superior visual art when writing standard SVGs via a creator skill, suggesting the models are better at generating markup than piloting a custom layout API.
Qwen-Image-3.0: Rich Content, Authentic Details, Deep Knowledge
Submission URL | 564 points | by ilreb | 215 comments
A 3.0 release signals a major iteration aimed at richer, information-dense outputs with truer-to-source details and stronger knowledge grounding in image tasks. The emphasis shifts the bar from stylistic flair to accuracy and trustworthiness, suggesting a model positioned for production scenarios where visual fidelity and factual consistency matter.
The discussion centers on a core skepticism regarding generative AI in e-commerce: the models fundamentally prioritize aesthetic flattery over accurate physical representation.
Commenters cataloged how AI is already distorting various online marketplaces:
- Apparel: Critics argue that "virtual try-ons" fail by synthesizing a perfectly tailored fit regardless of the garment's actual cut. A former photography assistant confirmed that traditional catalog shoots rely on binder clips to fake a perfect drape; AI models simply automate this deception, rendering clothes ideally proportioned for the buyer's body rather than showing how the fabric actually hangs.
- Furniture: Users report a surge in Etsy and Wayfair listings where cheap, drop-shipped MDF flatboards are AI-rendered to look like massive, high-end solid wood. One user noted defeating this by feeding an AI-generated image to ChatGPT, which cross-referenced the diagram text to prove a seemingly six-foot shelf was actually 49 inches tall.
- Real Estate and Classifieds: The practice of "virtual staging" has escalated from adding digital furniture to fundamentally altering reality, with models generating non-existent doorways, augmenting natural light, and swapping alley views for private gardens.
This baseline of fabrication prompted a theoretical divide over the future of "truth in advertising." While some view generative AI as the final erasure of honest marketing, others suggest the technology could eventually swing back to empower buyers. The unresolved question is whether consumers will adopt fine-tuned, defensive "personal models" designed specifically to strip away retailer embellishments and verify exact physical properties before purchase.
Show HN: CodeAlmanac – Karpathy-style codebase wiki from your conversations
Submission URL | 58 points | by divitsheth | 20 comments
It maintains a first-class wiki under almanac/ in your repo and keeps it fresh by ingesting your Codex/Claude Code transcripts every 5 hours, so decisions, invariants, and cross-file workflows don’t vanish into chat history and the diffs are reviewable in Git.
Pages are plain Markdown, locally indexed in SQLite, and queryable via a CLI (search/show/topics/health/validate) or a local web viewer (serve). It also drops agent instruction files (AGENTS.md/CLAUDE.md) so future sessions automatically search the wiki before they start coding.
Automation runs entirely on your machine via launchd:
- Sync (every 5h): scan recent agent conversations and queue updates
- Garden (every 24h): prune staleness/duplication, fix weak links/leads, and improve the graph
- Update (every 24h): safe CLI self-update
Under the hood, explicit build/ingest/garden agents run through the public Yoke SDK and can fold in files, dirs, diffs, commit ranges, GitHub PRs/issues, URLs, and local transcripts. This is a trusted-local model: agents get broad, non-interactive filesystem access; the almanac/ boundary is policy, not a sandbox—review diffs when auto-commits are off.
Supported today on macOS with Codex or Claude Code; Python 3.12+ required. Telemetry is opt-in and minimal, runs under a random UUID, and excludes code, paths, prompts, and transcripts; DO_NOT_TRACK=1 disables it.
The time-based trigger (vs. on-commit) avoids excessive token churn for frequent committers and better fits team workflows where multiple developers work with their own agents. If you’re not on macOS or can’t grant wide local FS permissions, this isn’t for you yet.
The central debate focused on whether an AI can autonomously extract high-level knowledge from chat transcripts. One developer argued that models routinely cross abstraction levels and fail to separate conceptual leaps from implementation details, making a human-in-the-loop essential. The creators countered that strict stylistic constraints—specifically applying the Diátaxis framework and providing explicit AI anti-patterns—solve this, noting that the resulting wikis are currently optimized for agent retrieval rather than human readability.
When asked about token savings and output quality, the developers shared preliminary LoCoMo benchmark results at a 2k-token retrieval budget, where Almanac scored 55.7% (trailing Mem0's 60.6% but beating BM25's 51.8%). They cautioned, however, that conversational memory benchmarks don't perfectly map to coding agent workflows.
The automated background-ingestion model prompted several practical questions from the community:
- Security: How the sync agent prevents API keys pasted into debug transcripts from being committed to the repo.
- Permissions: Whether macOS
sandbox-execcould be adopted to rein in the agents' broad local filesystem access. - Version history: How the wiki preserves the history of coding approaches that were attempted and explicitly abandoned, rather than just overwriting decisions in-place.
While officially macOS-only, users reported successfully testing the tool on Linux. One noted that bypassing the background sync entirely in favor of deliberate, manual wiki updates actually felt like a better workflow.
AI Agent – TRMNL
Submission URL | 51 points | by joeyespo | 29 comments
It will build a TRMNL plugin from a single sentence and then do the grunt work itself — editing markup, updating settings, refreshing data, searching the web, and calling listed API endpoints to complete the task. Expect roughly $1–3 per plugin; their “meh.com daily deal” example cost $2.20 after the agent requested a free Meh.com API key and later added the product image.
- Requirements and models: Public beta. Needs an OpenRouter API key (billing via OpenRouter) or an Anthropic/Claude API key with credits; optional free Tavily key for web search/fetch. Supports Gemini, Codex, Claude Sonnet, Kimi, and OSS models like Llama; pick a preferred model under Account > Agent. Free OpenRouter models work but tend to be slower/less capable. TRMNL-hosted credits are “coming soon.”
- Quickstart:
- In Account, toggle Agent on and save.
- Configure model, keys, and usage; save.
- Create a Private Plugin (Plugins > Private Plugins > New) and save.
- Open Edit Markup → Agent tab, then ask it to build or to explain the TRMNL framework.
- Under the hood: A detailed, English system prompt gives the agent deep knowledge of TRMNL’s capabilities and design patterns (you can even ask it about this). Tooling access grounds it: markup editing, settings updates, data refresh, internet search, and a catalog of API endpoints.
- Advanced (MCP): Generate an MCP API key from your private plugin’s settings and provide it to your desktop agent to develop locally with your own tooling.
- Limitations: Plugin publishing via Agent isn’t enabled yet (the team manually reviews submissions); bugs/quirks are expected in beta.
A significant portion of the discussion was overshadowed by controversy surrounding the TRMNL creator's personal politics. Users circulated archived copies of the founder's now-deleted blog posts containing inflammatory remarks about transgender individuals and women, prompting several commenters to declare they would withhold financial support from the company.
Debate over the product itself focused on the company's embrace of AI generation. Critics expressed disappointment that a promising hardware project was transitioning into "just another AI company," arguing that a "Just Worked" prompt interface is a poor fit for HN's deeply technical audience. The founder pushed back, arguing the AI agent is an optional enabler for non-technical users to "vibe code" custom dashboards, and emphasized that the hardware remains open-source and entirely usable without LLMs.
Other technical discussions centered on hardware alternatives and specific project claims:
- E-ink Alternatives: A user detailing their custom ESP32 and Seeed Studio setup for displaying Kindle highlights was pointed toward OpenDisplay. Commenters noted that repurposed Bluetooth supermarket shelf labels offer multi-year battery life and avoid the maddening 30-second full-refresh loops of traditional e-ink screens.
- Plugin Generation Costs: Addressing skepticism over the stated $1–3 price to generate simple HTML/JS plugins, the founder clarified this was a legacy metric from their launch using a cloud agent. Users running the open-source skills locally with their own LLM subscriptions generate them essentially for free.
- Geographic Pedantry: A tangent disputed the landing page's claim of "250 countries," with commenters concluding the number likely stems from the 249 ISO 3166 codes rather than the 193 UN-recognized nations.
Five tech giants are hiding $1.6T in AI debt, using the trick that toppled Enron
Submission URL | 97 points | by arto | 19 comments
Up roughly eightfold in four years, off‑balance‑sheet AI obligations now total $1.65T—more than the $1.35T these firms report outright. The obligations are parked in special-purpose vehicles and joint ventures that finance chips, servers, and power for AI data centers, keeping the debt out of the parent’s accounts while construction is underway.
- Meta’s Hyperion data center is financed by a separate structure with $27B in debt alongside Blue Owl Capital; Meta is the sole tenant yet doesn’t record the debt. Meta’s off-book load is about $420B, nearly triple its reported debt.
- Oracle discloses $260B in future lease commitments that will move on balance sheet as facilities go live; its off-book exposure has grown roughly thirtyfold in four years.
- Nvidia carries $119B in purchase obligations; Alphabet and Microsoft use similar off-book vehicles.
The timing matters: four of the five report earnings within two weeks, where headline leverage will look clean while $1.65T sits in footnotes. The catch comes at go‑live, when leases hit the balance sheet at once; if AI demand undershoots, data centers get marked down and losses fall to the lenders and insurers who funded them. S&P already cut Oracle’s rating over stretched leverage, and Morgan Stanley and Moody’s have flagged the broader risk.
None of this is illegal—disclosures exist—but it means investors are seeing less than half the true leverage behind the AI build‑out.
Commenters immediately flagged the submitted article as AI-generated—citing telltale structural quirks like a “The honest version” heading—prompting users to bypass the text and track down the original Bloomberg Law report it appeared to be summarizing.
On the substance of the hidden debt, the discussion focused on historical parallels. Users debated which financial crisis serves as the better analogy for the AI build-out: the 2008 crash, given the familiar reliance on "special-purpose vehicles" to obscure massive underlying leverage, or the early-2000s dotcom bust, driven by circular funding for ephemeral tech services with little connection to real economic output.
Show HN: Orate – On-device neural text-to-speech queue for Mac
Submission URL | 17 points | by bherms | 14 comments
Select text anywhere on your Mac and queue it to be read aloud offline with a hotkey — a native menu bar app turns articles, emails, and PRs into a podcast-style playlist synthesized entirely on-device, so nothing leaves your machine. Unlike cloud TTS or copy/paste workflows, it captures via ⌥⌘L or context menu, cleans text for the ear (paragraphs and pauses), and remembers progress across a library with Up Next, tags, notes, and resume.
- Voices: 14 built-in American/British voices; ships with Kokoro; optional HD voice via Chatterbox for extra expressiveness.
- Playback: 0.5×–2× with pitch preserved, time-remaining retimes to speed, and system playback controls.
- Privacy: fully offline; no account, cloud, or telemetry. Text and audio are stored locally.
- Price: $4.99 one-time with a 14-day free trial; code HACKERNEWS takes $3 off at launch.
- Requirements: macOS 14+ on Apple Silicon (M1 or later). Mac-only today; iOS companion planned, Windows possible based on interest.
The thread consists of rapid-fire bug reports and direct roadmap confirmations from the developer:
- Startup crashes: Early adopters on newer hardware (M4 and M5 Macs) hit silent crashes during the setup wizard. The developer quickly shipped a patch (v0.1.9) resolving the issue and adding crash reporting.
- iOS and sync: Commenters noted the app's potential as an audio-first Instapaper, but emphasized the need for mobile playback. The developer confirmed an iOS companion app with device sync is roughly a week away.
- Voice cloning: Responding to a request for specialized character voices for reading fiction, the creator noted that the optional Chatterbox plugin already contains unexposed AI voice-cloning capabilities that could be unlocked.
- Audio demos: Users looking for voice samples before installing were pointed to the website's hero image, which the developer clarified is actually an interactive audio preview, though its playability isn't obvious.
Meta's AI models are powering the first wave of Genesis Mission projects
Submission URL | 97 points | by surprisetalk | 86 comments
A month of expert image segmentation collapsed to ~15 minutes by fine-tuning Meta’s open-source Segment Anything Model 3 (SAM 3) and DINOv3 on DOE beamline data and running them across 300 A100 GPUs at national supercomputing centers such as NERSC—returning fully reconstructed, semantically labeled 3D volumes to scientists while experiments are still running.
In SYNAPS-I, a Genesis Mission flagship led by Berkeley Lab with Argonne, Brookhaven, Oak Ridge, and SLAC, DINOv3’s self-supervised features supply global context for what’s in each X-ray or micro-CT image, while SAM draws precise pixel-level boundaries; together they turn raw synchrotron output into object-level segmentations fast enough to steer in-situ studies. This directly tackles the data deluge from upgraded detectors that jumped from one frame every six seconds to 100,000 per second, pushing DOE light and neutron sources into tens of petabytes per year—far beyond what manual annotation can handle.
A demo on drought-stressed grapevines shows the payoff: automatic identification and tracking of xylem vessels in 3D micro-CT scans, enabling cellular-level insights that could inform the development of drought-resilient crops. Because the models are open source, national labs can download, fine-tune, and deploy them entirely inside secure on-prem infrastructure—adapting models trained on natural images to specialized scientific domains without sending sensitive data to external clouds.
The discussion splits between a legal debate over Meta’s open-source definitions and a sprawling tangent on UI architecture. On the licensing front, critics point to restrictive clauses in the SAM license—preventing reverse engineering, mandating ITAR compliance, and terminating access upon certain litigation—as proof that Meta's models are merely "open weight." Others frame the litigation clause as a standard defensive measure similar to the AOM AV1 codec, arguing that any semantic impurity is outweighed by Meta practically enabling mass-segmentation biology tools like Cellpose.
A historical comparison to React's early, controversial patent clauses derails the thread into a referendum on frontend complexity. Proponents of the React/Redux paradigm contrast its functional state management favorably against the mutable object bugs and INotifyPropertyChanged infinite loops of desktop frameworks like WinUI3 and WPF. Detractors argue that React cemented unnecessary SPA complexity as an industry standard when older MVC patterns in tools like AppKit were perfectly adequate.
A few distinct observations surface outside the UI debate:
- Funding: One user noted that Google contributed a $40 million token donation to the public sector effort.
- Model taxonomy: Commenters grouped the major AI players by "personality," categorizing Meta for vision, Claude for intelligence, Gemini for speed, and OpenAI for aesthetics, while carving out a niche for Grok as a highly spontaneous creative writing tool.
Yubikey 5.8: Verified Authorization for the New Era of Identity and AI
Submission URL | 21 points | by dblitt | 16 comments
Firmware 5.8 turns YubiKeys from login factors into hardware-backed signers for verified actions, enabling document approvals, financial transactions, and human-in-the-loop AI authorizations via FIDO CTAP 2.3 and developer‑preview WebAuthn extensions. This extends the hardware root of trust beyond access to verifiable approvals that map cleanly onto modern, high‑consequence workflows.
- Verified authorization: Standards-based signing of digital actions, not just authentication.
- Trusted AI workflows: Anchor autonomous actions in verified human intent with explicit approvals.
- Developer integration: CTAP 2.3 plus preview WebAuthn extensions for secure, privacy-preserving flows.
- Ecosystem support: Digital identity wallets, verifiable credentials, and Secure Payment Confirmation.
- UX improvements: Persistent PIN User Access Token (PPUAT) for easier credential discovery.
- Enterprise scale: Up to 16 RPIDs to cover dev/stage/prod without awkward workarounds.
Now shipping across YubiKey Bio, YubiKey 5, and Security Key Series; the YubiKey FIPS and CCN Series remain on firmware 5.7.4 to preserve ongoing certifications.
The thread was dominated by frustration with security industry marketing, as commenters argued that firmware 5.8's "AI era" features are currently unusable due to a lack of ecosystem support and immutable hardware.
- The WebAuthn correction: When one user pointed out that WebAuthn is already widely implemented, another clarified the technical distinction at the heart of the release. While base FIDO2 login flows are ubiquitous, 5.8 relies on an unshipped WebAuthn extension to enable a second flow for signing arbitrary text, like a contract fingerprint. Because no major browser actually supports this extension yet, the headline feature cannot be practically used today.
- No upgrade path: Multiple users criticized Yubico for phrasing the announcement like a standard software update. Because YubiKey firmware cannot be flashed, accessing these new features requires purchasing entirely new hardware—a sore point compounded by users recalling past instances where Yubico continued selling older, vulnerable stock before explicitly forcing customers to buy the newer versions.
- Ecosystem decay: A power user shared their complete retreat from a strict hardware-auth setup (which had included mandatory YubiKey SSH authentication) back to standard TOTP apps like Microsoft and Google Authenticator, noting that web platforms have steadily neglected or actively dropped compatibility for physical tokens.
- Pricing and PQC: Minor threads debated device margins—recalling when YubiKeys were cheap enough to be bundled as Wired magazine signup freebies—and pointed out the conspicuous absence of Post-Quantum Cryptography in a release explicitly billed as a new era for security.
Show HN: Browser Tools SDK – an optimal browser harness for agents
Submission URL | 11 points | by tanishqkanc | 6 comments
Ties the best pass rate on 26 live-site tasks (24/26) while cutting cost-per-success by ~55% ($0.106 vs $0.235) and tokens (1.45M vs 2.29M+) compared to agent-browser/dev-browser/playwright-cli, using GPT 5.6 Sol (best of 3 runs).
A small MIT-licensed TypeScript SDK that lets agents drive a real browser via six tools, with two doing most of the work:
- browser_snapshot — returns a compact accessibility tree with stable refs so models can “see” page structure without raw HTML, keeping context tight.
- browser_exec — runs raw Playwright code on the live page and returns a snapshot diff of what changed; models already know how to write Playwright, so this minimizes prompting.
Works out of the box with AI SDK and Pi, plus a framework-agnostic path for custom loops; more adapters are planned. Supports Libretto Cloud, Browserbase, Kernel, and Steel, or run Chromium locally via LocalBrowserProvider (with fewer anti-bot protections).
The efficiency story comes from snapshot-first navigation and diffed feedback after actions, which reduces token churn while preserving enough structure for reliable planning. Bench methodology is published in the repo.
The brief discussion consists entirely of Q&A with the author clarifying the SDK's mechanics. The main technical distinction surfaced is how the tool achieves its token efficiency over playwright-cli: instead of forcing the AI to reason and prompt between every single browser action, the SDK allows the agent to write large, batched blocks of Playwright code that execute in a single conversational turn.
On practical usage, the author noted that for authenticated sessions, local browsers can run in headed mode for manual login, whereas remote providers require proxying a live feed URL to the user. Finally, addressing skepticism about the benchmark claims, the author simply pointed to the project's repository where the full 26-task methodology and raw session results are already published.
I built a page that tells you what AI model your laptop can run
Submission URL | 34 points | by kumarski | 24 comments
In-browser hardware detection (RAM, CPU cores, GPU tier) maps your machine to the largest local LLM it should handle with “good performance.” It then places you on a tier ladder — Entry (1B), Mid (7B), Large (70B), and an aspirational SOTA bucket (~1T+ params) — and shows how far you are from top-tier.
- Model Tier Comparison lists example models, the estimated RAM required, and your status.
- Estimates assume 4-bit quantization on consumer hardware; actual results vary with quantization quality, model architecture, and tooling (llama.cpp, vLLM).
- SOTA references (GPT-4o, Claude 3.5, Gemini Ultra) are estimated at 1T+ parameters.
Use it as a quick sanity check before downloading a model; it’s an estimator, not a throughput benchmark.
The thread serves as a practical demonstration of why in-browser hardware detection is notoriously unreliable. Across Windows, macOS, and Linux, the vast majority of commenters reported wildly inaccurate specs—likely due to browser anti-fingerprinting measures. Modern RTX setups were identified as generic "ANGLE" outputs or legacy GeForce 8800s, while machines with 64GB or 128GB of RAM were routinely clocked at 8GB or 16GB.
Because the tool lacks manual overrides, these detection failures broke its utility for most users. The site's creator jumped in to clarify the app was a quick experiment generated via a Minimax prompt, explicitly inviting experienced developers to build a harder-wearing version.
To that end, the discussion surfaced two preferred alternatives:
- canirun.ai: Highly praised precisely because it allows users to manually select their real GPU from a dropdown when auto-detection inevitably fails.
- llmfit: A CLI tool recommended for users who want projections of actual inference speeds and tokens-per-second, rather than a binary tier system.
Other actionable feedback noted that the logic is far too conservative on Apple Silicon—telling M4 users they are restricted to 1–3B parameter models when 12B runs comfortably—and that the SOTA examples in the tier ladder need an update.
Show HN: Language Model Builder (an app to learn about and build models)
Submission URL | 17 points | by felixrieseberg | 3 comments
Fully local, MLX‑accelerated training on Apple Silicon lets you build and fine‑tune a GPT‑2‑small–class model on your Mac and then chat with it — no installs, no cloud, no account. The app pairs an interactive, textbook‑style intro (tokenization, embeddings, attention, transformers, loss/optim) with a native training workbench that runs the whole pipeline in‑process: pre‑training, sampling, supervised fine‑tuning (SFT), and direct preference optimization (DPO).
- Tools and telemetry: watch loss, throughput, validation, saved samples, and checkpoints live; resume from checkpoints; compare runs.
- Data: curated corpora for pre‑training and fine‑tuning plus first‑class support for your own datasets.
- Inspectability: a “Conversation X‑ray” view exposes token probabilities and alternatives while chatting with your model.
- Portability: exports models as safetensors for sharing or use in other apps.
- Scale expectations: default settings can yield coherent multi‑paragraph text in a day; training a ~100–150M‑parameter, GPT‑2‑small‑class model on a few billion tokens is framed as about a week on a MacBook Pro M5 Max — this is not for frontier‑scale models.
- Price and platform: free, fully local; Mac‑only today (relies on Apple’s ML framework).
Early feedback focuses strictly on the app's user interface and reading experience. Commenters praised the data visualizations and SwiftMath typesetting, while logging minor bug reports and requesting standard textbook features like text highlighting and Cmd+F search.