MurphyA/hacker-news huggingface dataset:
by briantakita | 2026-03-04 13:39:54+00:00
The pre-submit commit as an immutable baseline is the key design decision — every agent interaction is an atomic transaction with a known rollback point, exactly right.

On the "event → agent" gap: we've been thinking about this as a layered problem.

The bridge is a file write. agent-doc is user-initiated (edit a doc, hit submit), but the diff pipeline doesn't care who writes the file. A watcher process — or any external system — can write to the file system, and the agent sees the change on next poll.

We already do this in a different layer: corky (https://github.com/btakita/corky), our email tool, runs a watch daemon that polls IMAP for new messages and syncs them to markdown files on disk. External event (email arrives) gets translated into a file-system change, which is the agent's native input format. Same pattern would work for session recovery: monitoring process detects flagged session → writes to a task file → agent picks it up.

Dashboard-as-document is something we're actively planning. The idea: a markdown template where a watcher fills in operational fields — session status, health checks, proxy assignments. When the watcher updates "active" → "flagged", the diff pipeline sees exactly what changed. The template gives structure; the diff gives the trigger.

The snapshot diff already works for this — partial support exists today via agent-doc's routing layer (external scripts can trigger submission when a file changes). What we're building next is auto-submit on file change and sectional write-back so the agent can update specific dashboard fields rather than only appending.

For sub-second latency, a lightweight daemon that receives webhooks and writes to the notification file or directly triggers an agent submit. But for most operational tasks, a polling interval (ours runs every 30 seconds) closes the gap well enough.

The gap you're describing — "thing happened" to "agent knows about it" — is really about who writes the event into the file system. Once it's a file change, the diff pipeline handles the rest.
by homeonthemtn | 2026-03-04 13:40:12+00:00
This is just management advice. This has as much spice as day old oatmeal. It's also not new, it's management training 101.

There's nothing fucked up about this. If anything it's recycled shit from a mall store manager's book of training.

Management training exists so that people don't defer to their own egos and impulses when managing staff. It's a systemic/standardized approach to common behaviors found in employees. If anything it helps mitigate the more toxic behaviors of competitive environments. It's not perfect, but it is funny that tech bros have rediscovered Human Resources departments
by gruez | 2026-03-04 13:40:15+00:00
>Latest attempt: https://news.ycombinator.com/item?id=47182376

Your Qubes OS comparison doesn't really work because Android distributions need extra work to support each new device, whereas for Qubes OS, they're probably using some virtualization framework that makes it pretty trivial to add support for CPUs without virtualization. There's nothing stopping you from starting a new fork that supports your motorola phone, for instance.
by geooff_ | 2026-03-04 13:40:22+00:00
One thing missing from this discussion is the blast radius of the product or repo in question.

Let PMs land new widgets on internal dashboards or CSS changes in internal tooling. The same way we should be aspiring to build tools for devs to merge these same changes with minimal test plans. You wouldn't call a mechanic to help you turn on your windshield wipers.

Changes in high-risk environments should be gated for people who actually know what they're doing. That high bar should remain high.
by cmontella | 2026-03-04 13:40:27+00:00
Contemporary PL designers who have inspired my programming language design journey the most are people like Chris Granger (Eve), Jamie Brandon (Eve/Imp/others), Bret Victor (Dynamicland), Chris Lattner (Swift / Mojo), Simon Peyton Jones (GHC/Verse), Rich Hickey (Clojure), and Jonathan Edwards (Subtext). My favorite researcher is Amy J. Ko for her unique perspective on the nature of languages. Check out her language "Wordplay" which is very interesting.
by watwut | 2026-03-04 13:40:43+00:00
First, USA literally officially does not care about it right now. That is the stated official politics. Hegseth, Vance and Trump are proud and open about it. Hegseth was referring to literally this war when he was saying they will not care about things like civilian deaths.

Second, the number of civilians deaths caused by USA was going up due to drones usage. That is prior Trump, in administrations that kind of cared at least a little. And that was at the time when media sorta kinda cared. Nowdays, media do not care at all.

Third, Israel is not just ok with genocide, but wants it to happen. And USA is one of the leading countries in the project of helping them. I am not singling out America here, it is not JUST America. But America is very consistent in that.
by varispeed | 2026-03-04 13:40:46+00:00
One for instance is that Apple doesn't offer an API for deep system scanning. So if your phone is infected, you have no way of knowing this, because there is no software that can scan it. You cannot trust it.

Or things like Memory Tagging Extension (MTE) Apple has implemented, but they have not released specification and implementation details, so you don't know if it has backdoors.
by stego-tech | 2026-03-04 13:41:50+00:00
Except they do have IT infra as a skill - or did - and replaced it with higher-paid “cloud architects” who just manage VM fleets and DBaaS in the vendor they’re certified in, which could just as easily be done on-site nowadays. They’re lower-skilled overall but more specialized, and thus command higher pay.

Generalists (it me) typically command lower market rates, remain far more flexible, and can replicate much of the experience on-prem while knowing when and why to put something in the public cloud. A few examples:

* 24/7 Telemetry and Monitoring: if you have the talent to roll your own with OpenTelemetry, Grafana, Prometheus, and a database to store the telemetry involved, then great! If it’s me wrangling a hybrid environment though, I’m likely leaning on New Relic to save on headcount and deliver similar results.

* DBaaS: this is increasingly just offered by hypervisor managers since it’s often just spooling up a container and pointing to storage. Not quite a “solved problem”, but enough of one that a single DBA can cover both estates if needed - or a moderately skilled generalist can at least secure it for internal use before offering it out to customers

* Vulnerability Management: as much as I’d love to have an internal Red Team, it’s an order of magnitude cheaper to leverage Nessus, Wazuh, Wiz, or any of the other fleets of continuous scanners to identify vulnerabilities or misconfigurations

That’s just me cherry-picking. The point is less “do everything possible on-prem”, and more “diversify workload placement depending on cost advantages relative to risk models”, and on-prem wins quite handily for a lot of LOB software that just quietly sits and does its thing with minimal fuss.
by trjordan | 2026-03-04 13:42:13+00:00
The push for simplicity can't be at the time of recognition. It has to be during the building, so that by the time the thing gets built, it's the simplest thing that met the need.

Can you actually imagine a promo committee evaluating the technical choices? "Ok, this looks pretty complex. I feel like you could have just used a DB table, though? Denied."

Absolutely not! That discussion happens in RFCs, in architecture reviews, in hallway meetings, and a dozen other places.

If you want simplicity, you need to encourage mentorship, peer review, and meaningful participation in consensus-building. You need to reward team-first behavior and discourage lone-wolf brilliance. This is primarily a leadership job, but everybody contributes.

But that's harder than complaining that everything seems complicated.
Show HN: Pym2 – a lightweight process manager for Python services
by heradon | 2026-03-04 13:42:16+00:00
I built pym2 to manage Python services without writing complex systemd units
or running a full orchestrator.

It's a small process manager with:

- agent/CLI architecture
- crash protection
- TOML config
- optional TUI and web UI

It’s designed for FastAPI, background workers and small services.

Feedback welcome.
by edgyquant | 2026-03-04 13:42:30+00:00
Indeed. I consider the Supreme Court to be our only properly functioning branch of government. If you look at the Warren court it overturned precedent and “grabbed power” at a rate several times what you see from the current court yet because it did so for liberal purposes you only hear about how the court is political now.

I don’t agree with every Supreme Court ruling, but the constant attacks on the court from the left terrify me
by okanat | 2026-03-04 13:42:33+00:00
"We elected right-wing parties who are against sane wages and unions and often use/exploit immigrants to depress wages while funneling billions into companies and away from infrastructure projects. So we decided to elect an even more right-wing party to blame immigrants while doing even more funneling away. It will definitely solve all the infrastructure problems that those penniless brown people and weird speaking ones caused."
by ieviev | 2026-03-04 13:42:45+00:00
Yes, that's exactly what we did to be competitive in the benchmarks.

There's a lot of simple cases where you don't really need a regex engine at all.

integrating SearchValues as a multi-string prefix search is a bit harder since it doesn't expose which branch matched so we would be taking unnecessary steps.

Also .NET implementation of Hyperscan's Teddy algorithm only goes left to right.. if it went right to left it would make RE# much faster for these cases.
by engineer_22 | 2026-03-04 13:42:49+00:00
> The US air superiority has completely done them, it'd seem.

They're managing to successfully counterattack with strikes in every country in the region, while the bulk of their central leadership has been KIA. They still control the Strait of Hormuz and very intense naval, land, and air operations will be required to dislodge them.

If this war was started with the goal of the complete destruction of Iran, ground troops will have to go in (President Trump et. al. is already in the media telegraphing the requirement). Iran is a mountain fortress, and the home team (pop. 91 million) holds advantage. This has the potential to become and long and bloody war.
by jundot | 2026-03-04 13:43:20+00:00
Hi HN, I'm the developer. I built oMLX because every Mac LLM server I tried fell apart with coding agents.

The core problem: tools like Claude Code and OpenClaw send requests where the prompt prefix keeps shifting. Most servers invalidate the KV cache after each turn, forcing a full re-prefill. On large contexts (50-100K tokens), that means 30-90 seconds of waiting per request. After a few turns, it's practically unusable.

oMLX solves this with paged SSD caching. Every KV cache block is persisted to disk. When a previous prefix comes back, it's restored from SSD instead of being recomputed. In practice, TTFT drops from 30-90s to 1-3s on follow-up requests. Cache blocks survive server restarts too.

What's under the hood:

- Continuous batching via mlx-lm (multiple concurrent requests)

- Multi-model serving (LLM + VLM + Embedding + Reranker simultaneously, LRU eviction)

- OpenAI + Anthropic compatible APIs Tool calling support(JSON, Qwen, Gemma, MiniMax, GLM formats + MCP)

- Native macOS menubar app (PyObjC, signed DMG) — download, drag, done

As of v0.2.0: Vision-Language Model support with the same tiered caching

Benchmarks on M3 Ultra 512GB with Qwen3-Coder-Next-8bit: 58.7 tok/s single request, 243 tok/s at 8x batch. Full results on the README.

It reuses LM Studio's model directory, so you don't need to re-download anything.

100% open source (Apache 2.0): https://github.com/jundot/omlx
by the_af | 2026-03-04 13:43:43+00:00
> Pete Hegseth is hyper-conservative too. Actually all three of the main combatants are hardline religious groups.

You get downvoted for saying something that's true, and it's not even a defense of the Irani theocratic dictatorship.

Namely: at least some of the support for the war (and for Israel) in the US is religiously motivated. Religious as in "fundamentalist". This doesn't make the US a theocracy, but it does mean many of the decision makers are making decisions based at least partly on Christian fundamentalist doctrine.

There are already some reports [1] of US troops complaining they are being told they've embarked on a mission from God. It boggles the mind.

> "One complainant, identified as a noncommissioned officer (NCO) in a unit that could be deployed “at any moment to join” operations against Iran, told MRFF in a complaint viewed by the Guardian that their commander had “urged us to tell our troops that this was ‘all part of God’s divine plan’ and he specifically referenced numerous citations out of the Book of Revelation referring to Armageddon and the imminent return of Jesus Christ”

> "“He said that ‘President Trump has been anointed by Jesus to light the signal fire in Iran to cause Armageddon and mark his return to Earth’”, the NCO added."

(This was just one report of many).

[1] https://www.theguardian.com/world/2026/mar/03/us-israel-iran...
by arteon | 2026-03-04 13:44:23+00:00
Create a complete favicon.ico set for your website from a single image. This tool allows you to generate a favicon.ico and a complete set of PNG icons for your website, all from a single image. The processing happens locally in the browser, ensuring privacy as files never leave your computer. You can generate icons in various sizes, including 16x16, 32x32, 180x180, 192x192, and 512x512, which are essential for different platforms and devices. Supported formats include PNG, JPG, and SVG, making it versatile for different source images. The tool also generates a manifest.json file for Progressive Web Apps (PWA), ensuring your web app is installable on devices.

Privacy: All operations are performed locally in the browser, and no data is sent to any server.
Complete Set: Generate favicon.ico, PNG icons, apple-touch-icon, PWA icons, and manifest all from one image.
Format Support: Use logos in PNG, JPG, or SVG formats.
Ready for PWA: Generates a manifest.json file for web apps.
This tool is perfect for web developers, designers, and marketers looking to enhance their website's branding with a professional favicon set.
by Kenny_007 | 2026-03-04 13:44:27+00:00
Looks interesting. My homelab slowly turned into a mix of Portainer, btop and a couple of scripts as well. Some stuff runs on a small box at home, but I keep a few services on a tiny VPS cube-host) so they stay reachable if my home internet goes down. Curious how heavy this gets if you monitor several docker hosts.
by Bishonen88 | 2026-03-04 13:44:31+00:00
So, another wrapper around claude 4.6 for +xx% higher price? Using just claude code, one can do what glazeapp seems to aim for, no? "Beautiful by default" seems to be a system prompt akin to:

Design Philosophy Create apps that feel premium, polished, and worthy of being featured on Dribbble's most popular shots. Every pixel matters. White space is your friend. Less is more, but what remains must be perfect.

Visual Design Principles

Color & Theming

• Use sophisticated, limited color palettes (2-3 primary colors maximum) ...
by varispeed | 2026-03-04 13:44:35+00:00
Yes, Apple controls who gets alerted about security breach. This means not everyone with compromised phone will get alerted. You are still in the dark.

Maybe they could maybe they couldn't, doesn't mean criminals couldn't.

MIE is opaque - Apple has not disclosed its design - it also means it can contain intentional backdoors and other security holes.

In other words this is just meaningless PR and doesn't change the fact that Apple's security is poor.
Show HN: Open-source scanner finds 97% of AI agent code non-compliant EU AI Act
by airblackbox | 2026-03-04 13:44:47+00:00
I built AIR Blackbox, an open-source static analysis tool that scans Python AI agent code against 6 technical requirements from the EU AI Act (Articles 9, 10, 11, 12, 14, 15). Think of it as a linter for AI governance.
To stress-test the scanner — and to see where the industry actually stands — I ran it against 5,754 Python files across 11 major open-source projects. Combined GitHub stars: 341,000+.
Projects scanned: AutoGPT (170K stars), Microsoft AutoGen (38K), LlamaIndex (37K), Mem0 (24K), Phidata (18K), LiteLLM (15K), GPT-Researcher (14K), Embedchain (9.2K), LangGraph (8.5K), OpenAI Agents SDK (5.2K), CrewAI Examples (2.8K).
Results:

Average compliance score: 2.2 out of 6 articles
97% of files fail Article 9 (Risk Management)
89% fail Article 12 (Record-Keeping)
84% fail Article 14 (Human Oversight)
Only 23 out of 5,754 files (0.4%) pass all 6 checks
Best scoring repo: AutoGPT at 2.9/6. Worst: CrewAI examples at 1.4/6

What the scanner checks (per article):

Art. 9: risk classification, access control, risk audit
Art. 10: input validation, PII handling, data schemas, provenance
Art. 11: logging, documentation, type hints
Art. 12: structured logging, audit trail, timestamps, log integrity
Art. 14: human review, override mechanism, notifications
Art. 15: input sanitization, error handling, testing, rate limiting

An article "passes" if at least 1 sub-check is detected. This is generous — real compliance requires substantially more.
Caveats I'll save you the trouble of pointing out:

This is static analysis. It can't verify runtime behavior.
File-level scanning misses cross-file compliance patterns.
The pass threshold is intentionally lenient (1-of-N sub-checks).
This checks technical requirements, not legal compliance. It's a linter, not a lawyer.

The EU AI Act enforcement deadline is August 2026. The full report, raw data (JSON), and the scanning scripts are all in the repo.

GitHub: https://github.com/air-blackbox/air-blackbox-mcp
Full report: https://github.com/air-blackbox/air-blackbox-mcp/blob/main/b...
Install: pip install air-blackbox-mcp
Demo: https://huggingface.co/spaces/airblackbox/air-blackbox-scann...

Happy to answer questions about the methodology, the scanner internals, or what we're building next (fine-tuned local LLM for deeper analysis — your code never leaves your machine).
by user2722 | 2026-03-04 13:44:47+00:00
I'd posit the faster we feed LLM exhisting nuclear crisis and invented, dissimilar to its training corpus, nuclear scenarios, the better we will know how wrong they can be.
Fear-mongering isn't lucrative, isn't dopamine triggering, isn't actionable, doesn't look good on the resume, so it's tipically ignored.
by jmull | 2026-03-04 13:44:52+00:00
Don't ignore the context here. These are people hired to develop software for a company. They have an obligation to do so efficiently, with sufficient quality, and while balancing the company's short term and longer term business needs.

I think it's great that software development has been opened up by LLMs. Everyone should at least try it, IMO.

But your company's source isn't your personal playground and you shouldn't treat it as such.
by airblackbox | 2026-03-04 13:45:42+00:00
Some context on why I built this:
I kept seeing the same pattern — teams shipping AI agents into production with zero compliance infrastructure. Not because they don't care, but because there's no tooling that makes it easy.
The EU AI Act maps to 6 specific technical areas. Most of them come down to things developers already know how to do — structured logging, input validation, error handling, access control. The problem is nobody's connecting those practices to the regulatory requirements.
A few things I learned from this scan:

Article 11 (Technical Documentation) is the easy win. 98% of files pass because Python developers already write docstrings and type hints. The rest of the articles require intentional infrastructure that almost nobody adds.
The gap isn't capability, it's awareness. LiteLLM's auth module scored 6/6 — it already has access control, structured logging, timestamps, error handling. It wasn't built for EU AI Act compliance. It just happens to have good engineering practices. Most agent code doesn't.
"Example" and "quickstart" code sets the pattern. When OpenAI and CrewAI ship examples with zero compliance patterns, every project built from those examples inherits the gap. The ecosystem needs compliance baked into the templates, not bolted on after.

What I'm working on next: a fine-tuned Llama 3.2 1B model that runs locally and does deeper semantic analysis beyond regex pattern matching. The goal is "your code never leaves your machine" — because if you're worried about compliance, shipping your source code to a cloud API defeats the purpose.
The scanner, the benchmark data, and the full 5,754-file report are all Apache 2.0. Rip it apart, tell me what's wrong, submit PRs.
Ask HN: What is the state of prompt injection attacks and best practices?
by logicallee | 2026-03-04 13:46:11+00:00
I am curious about the state of prompt injection attacks on frontier models. Are they still vulnerable? For example, is it safe to let Claude Code look at user-submitted data if it also helps manage some of the infrastructure or code? Can they just be asked to identify prompt injection attacks and flag and ignore them, or do injection attacks change the models' behavior despite the owner's prompts? What are best practices?
AAP – An open standard for verifiable AI agent actions (RFC draft)
by thinklanceai | 2026-03-04 13:46:34+00:00
As agents move from chat to action — invoking tools, delegating to sub-agents, modifying real systems — there's no standard for what a verifiable agent action looks like.
Every framework logs differently. Nothing is interoperable. Nothing is cryptographically verifiable. And nobody has defined what "an agent action" even is, formally.
We wrote a minimal RFC to fix that: the Agent Action Protocol (AAP).
AAP defines:

A canonical AgentAction data model
A cryptographic chain integrity model (SHA256-linked, like a git commit graph)
Explicit privacy boundaries — raw reasoning and parameters must never be stored, only their hashes
An extensibility mechanism for LangChain, OpenAI Agents, Anthropic, etc.

AAP is explicitly NOT a policy engine, a certification body, or a SaaS. It's a primitive. The smallest possible unit of verifiable agent cognition.
One design decision we want feedback on: we made abort a first-class decision type, equal to invoke_tool or delegate. An agent refusing to act is as auditable as an agent acting. Does this hold up in your mental model?
Reference implementation (Python) + RFC: https://github.com/Thinklanceai/aap-python
Tear it apart.
by d--b | 2026-03-04 13:46:51+00:00
Not my experience.

I once hacked a spreadsheet in a week that was good enough to not embark on a multiple-months 3-devs project.

In the same team, I tweaked a configuration file for distributed calculations that shaved 2 minutes of calculation on an action that the user would run thirty times a day.

I got paid all right.

People don't give a shit about complexity or simplicity. They care about two things:

1. Does it work

2. How soon can you ship

There is a third thing that stakeholders really like: when you tell them what they should be building, or not building.
by rayiner | 2026-03-04 13:47:01+00:00
> Have you seen the Islamophobia in the west

People in the west who talk about “Islamophobia” are often just ignorant about what Muslim countries themselves do to control political Islam. In my home country, where Islam is the official religion, the government banned Islam-associated parties until recently and went around killing Islamists without due process. In majority-Muslim Turkey, political Islam was suppressed—e.g. hijabs were banned until Erdogan came to power. Singapore bans the hijab for certain civil servants. None of that is “Islamophobia”—it’s an effort to make sure that what happened in Iran doesn’t happen in their country.