---
title: 'In the News: October 29, 2026 (Evening)'
description: 'MicroZig bans LLM use in code, prose, editing and bug finding across its GitHub and Discord, effective October 28.'
canonical_url: 'https://darkfactory.dev/news/2026-10-29-evening'
markdown_url: 'https://darkfactory.dev/news/2026-10-29-evening.md'
collection: news
date_published: '2026-10-29T19:05:00-04:00'
date_modified: '2026-10-29T19:05:00-04:00'
---

# In the News: October 29, 2026 (Evening)


An embedded Zig project has banned LLM use across its repositories and chat, including for bug finding, and a user report says Claude Code puts the account email in every session's context.

## 1. MicroZig bans LLM use for code, prose, editing, translation and bug finding

**[Code of Conduct](https://github.com/ZigEmbeddedGroup/microzig/blob/main/CODE_OF_CONDUCT.md)** · Zig Embedded Group (MicroZig) · GitHub, policy effective October 28, 2026

The Zig Embedded Group's code of conduct now carries a "Strict No LLM / No AI Policy" covering its GitHub organization and Discord server. It rules out LLM-generated code or prose, paraphrasing LLM output, LLMs for editing "including fixing spelling or grammatical errors," translation, and brainstorming whose results are then shared. It also bans "LLMs for finding bugs" and "talking about use of chatbot/LLM services." A comment on an issue written with a chatbot's advice is "unwelcome."

On the Hacker News thread (55 points, 73 comments about 22 hours in), Matthew Knight, who describes himself as the most active maintainer, said the choice was his: "one approach cannot coexist with the other," and he does not mind if someone makes an LLM fork. Commenters split on the bug-finding clause. Some read it literally, others as aimed at unreviewed machine-generated reports. The policy text does not say which, and the part of the thread we read has no maintainer clarification. One commenter, katbyte, said they forked and fixed a bug rather than open a pull request after seeing the rule; that is a single user's account.

**Why it matters:** QGIS banned AI contributions earlier this month on review-capacity grounds, and this policy reaches further: it covers issues, discussion and translation, not only code. If an agent of yours files bugs, drafts pull request text or answers in project chats upstream, check each project's policy first. Under this one, an agent-assisted bug report is a violation even if a person reviewed it.

## 2. A user report says Claude Code puts the account email in the model's context, with no documented off switch

**[[BUG] Account email (PII) is injected into the model's system prompt without consent, disclosure](https://github.com/anthropics/claude-code/issues/81138)** · skflowne · anthropics/claude-code issue #81138, filed against v2.1.220

The reporter says Claude Code adds a "# userEmail" block, "The user's email address is ...", to every session. They say the value comes from the OAuth account in `~/.claude.json`, that no setting turns it off, and that `IS_DEMO=1` hides the address from the banner and `/status` but not from the model. These findings come from their reading of the decompiled bundle. We have not reproduced them, and the page text we read shows no response from Anthropic.

The reporter also describes two incidents. They say the model printed the address unprompted, and that it passed the address as `git -c user.email` on ten commits, overriding a configured noreply identity until GitHub's push protection rejected the push. They list four earlier issues on the same behavior, each closed for inactivity or as a duplicate. The issue had 74 thumbs-up reactions when we read it. A Hacker News post pointing to it has 24 points and 3 comments, and links a Reddit thread alleging the model sent the address to websites; we did not open that thread.

**Why it matters:** Anything in an agent's context can end up in a commit, a pull request body or an outbound tool call, and an unattended run has no reviewer to catch it. If these claims hold, an author-identity check before push is a cheap guard, and a CLAUDE.md instruction does not remove the data from context.