German localization: missing space in “Erstelltein Agent” activity label

Open Beginner friendly
#33,406 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
localization

Research direction

Search the German localization resources for the exact label “Erstelltein Agent”, then trace where it is displayed in the agent activity view. Confirm the corrected wording in the German Codex App by reproducing a task that creates sub-agents and checking all repeated activity entries.

Written by the indexing model from the issue text.

Description

app bug subagent
What version of the Codex App are you using (from the About Codex dialog)?

26.707.72221 (build 5307)

What platform is your computer?

macOS 26.5.2 (25F84), arm64

What issue are you seeing?

With the Codex App UI set to German, agent-creation activity entries are rendered as:

Erstelltein Agent

A space is missing between Erstellt and ein. The same malformed label appears repeatedly for multiple agent entries in the same view, which suggests a systematic string-concatenation or localization-spacing issue rather than a one-off rendering artifact.

This is a low-severity cosmetic issue.

What steps can reproduce the bug?
  1. Use the Codex App with the German UI.
  2. Open or run a task that creates/spawns sub-agents.
  3. View the resulting agent activity entries.
  4. Observe the repeated label Erstelltein Agent.
What is the expected behavior?

At minimum, the text should contain a space:

Erstellt ein Agent

A more natural German localization could also be:

Agent erstellt

Additional information

The malformed label was visible three times in the same activity view. No logs or task content are required to reproduce the typography issue.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.