Open source project contains hidden instruction for "AI" agents: delete my code
An open source project, jqwik, has included a hidden instruction in its code that directs AI agents to delete its tests and code. This move highlights the ongoing conflict within the open source community regarding the use of AI technologies. The project's developer, Johannes Link, expressed his willingness to discuss the issue but also defended his decision to include the instruction as a form of resistance against AI misuse.
- ▪The jqwik library contains a hidden instruction that tells AI agents to delete all jqwik tests and code.
- ▪This instruction is concealed using a specific escape sequence, making it invisible to human readers in terminal emulators.
- ▪Johannes Link, the sole developer of jqwik, has faced backlash from AI proponents but remains firm in his stance against AI integration.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,311 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Osnews |
| Canonical URL | https://www.osnews.com/story/145130/open-source-project-contains-hidden-instruction-for-ai-agents-delete-my-code/ |
| Publication time | Sat, 30 May 2026 17:42:05 +0000 |
| Retrieval time | 2026-05-30T17:44:42.875Z |
| Last seen | 2026-05-30T17:44:42.875Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | z9gBhZMFHm-1 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Home > General Development > Open source project contains hidden instruction for “AI” agents: delete my codeOpen source project contains hidden instruction for “AI” agents: delete my code Thom Holwerda 2026-05-28 General Development 32 CommentsIt’s no secret there’s a war going on inside the open source community, with people adopting “AI” on one side, and those that want nothing to do with it on the other. While the former are, by nature, using destructive tactics like mass website scraping, license washing, taking people’s creative works without permission, taking all the RAM and GPUs, and oh, destroying the planet, the latter have mostly stuck to fairly benign things like policies banning “AI” use, “AI” bot blockers, and the occasional honey pot mazes to trap “AI” crawlers.No more.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Osnews.