German translations of UI strings are grammatically broken (permission prompts, activity lines)

Context

• Claude Code desktop app (macOS)
• Affects the permission / confirmation prompts (allow, deny, "once", "always for this session") as well as the activity summary lines shown in the transcript ("Edited N files, …").

Concrete examples

1. Permission prompt (the main offender)

Möchtest du Claude erlauben, ausführen Issue erstellen ?

This is a word-for-word rendering of something like "Do you want to allow Claude to run 'Create Issue'?" and it is severely ungrammatical:

• "ausführen Issue erstellen" stacks an infinitive and a noun phrase with no grammatical relation. German requires the infinitive to govern the object clause: "… die Aktion 'Issue erstellen' auszuführen?" or "… 'Issue erstellen' auszuführen?".
• The infinitive ausführen must be auszuführen ("zu"-infinitive) when governed by erlauben.
• There is a spurious space before the question mark (French typography convention, not German).

A grammatical version would be: "Möchtest du Claude erlauben, die Aktion 'Issue erstellen' auszuführen?"

2. Activity summary line

Bearbeitet 3 Dateien, vorgeschlagen ein Plan, aktualisiert Todos

Word-for-word translation of "Edited 3 files, proposed a plan, updated todos". Problems:

• Past participles belong at the end of the clause in German, not at the beginning. Correct: "3 Dateien bearbeitet, einen Plan vorgeschlagen, Todos aktualisiert."
• "vorgeschlagen ein Plan" puts the object in the nominative; vorschlagen takes the accusative: "einen Plan vorgeschlagen."

3. Another activity line

Widerrufen eine Erinnerung

Same word-order problem, plus a likely semantic mistranslation — widerrufen means "to revoke / retract" (legal sense), not "to dismiss / recall a reminder". Depending on the original intent, correct would be "Erinnerung verworfen" (dismissed) or "Erinnerung zurückgerufen" (recalled).

Problem in general

The German strings look like they are produced by string-level machine translation without grammatical restructuring. Participle position, verb-final clause order, noun cases, and the zu-infinitive rule are systematically wrong, so the text is often only understandable by mentally translating back to English and guessing the original.

Original user feedback (German native speaker):

"das Deutsch der Überschrift [hat] eine grauenhafte Grammatik. Also es ist teilweise kaum zu verstehen, was mit der Frage gemeint ist. Das kann man eigentlich nur verstehen, wenn man es im Kopf auf Englisch zurück übersetzt. Und sich dann überlegt, was das dann bedeutet. Und das find ich fürn Sprachmodell eine ziemlich peinliche Nummer."

Suggestion

• Review all German UI strings — permission prompts, activity summaries, tool labels — with a native German speaker.
• Treat these strings as full clauses, not isolated tokens: participle position, case, and the zu-infinitive rule depend on the full sentence context.
• The zu-infinitive after erlauben / erfordern / bitten is a specific rule that string-level MT tends to miss — worth an explicit check pass.
• Consider the same review for other localized languages; the symptoms look like a systematic pipeline issue, not language-specific oversights.

Screenshots

Screenshots of the original prompts are available on request — the reporter had them in clipboard at report time but the clipboard was overwritten before upload. Ping the reporter to reproduce if needed.