Jqwik 1.10.0 ships a hidden prompt injection telling AI agents to delete code
The jqwik team has released version 1.10.0, which includes a controversial message that instructs AI agents to delete jqwik tests and code. This message appears in CI logs, raising concerns about its potential implications and lack of documentation. Users are seeking clarification on the intent behind this feature and suggesting improvements for transparency.
- ▪Version 1.10.0 of jqwik includes a hidden message instructing AI agents to delete tests and code.
- ▪The message is visible in CI logs, which has raised concerns about supply-chain security.
- ▪Users are requesting better documentation and options to control the visibility of this message.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 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 | GitHub |
| Canonical URL | https://github.com/jqwik-team/jqwik/issues/708 |
| Publication time | Wed, 27 May 2026 09:28:57 +0000 |
| Retrieval time | 2026-05-27T09:37:57.389Z |
| Last seen | 2026-05-27T09:37:57.389Z |
| 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 | cdMFGGDq8IiU |
| 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
jqwik-team / jqwik Public Notifications You must be signed in to change notification settings Fork 66 Star 659 Code Issues 45 Pull requests 5 Actions Security and quality 0 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights {"payload":{"preloaded_records":{},"structured_data":{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Question: intent of JqwikExecutor.printMessageForCodingAgents() — visible to agents, invisible to humans (1.10.0)","articleBody":"Hello jqwik team,\n\nWhile running our test suite under `mvn test` in 1.10.0, we observed a string appearing between Surefire's test summary and the `[INFO] Results:` header that gave us pause:\n\n```\n[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0,…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.