Skip to content

feat(web): a bench's worker names itself from its first reply, and you can rename it (CL-9634) - #1055

Merged
TheGreatAxios merged 3 commits into
mainfrom
cl-9634-worker-name
Sep 30, 2026
Merged

TheGreatAxios merged 3 commits into
mainfrom
cl-9634-worker-name

Conversation

@TheGreatAxios

@TheGreatAxios TheGreatAxios commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

The worker's name is bench state in the tenant config key workbench.worker.name (same PATCH mechanism as the description); no redeploy, no hub code.

  • The first worker reply ending in a valid Name: <name> line stores the name (when none is stored); the line is stripped at render time.
  • Pill, sidebar Workers group, roster, worker page, message headers and drawer show the stored name, "New worker" until then.
  • Bench drawer Information tab has an inline Worker rename writing the same key.
  • The stock [From: …] header carries only the sender address (the mailbox host's senderAddressFor), so the worker prompt takes the person's name from that header when it has one, else from their entry in the Participants: block the send already appends.
  • e2e: reply.test.ts asserts naming, roster, rename and reload persistence.

Upstream gap: the stock mail From has no sender display name the hub fills from the principal.

Resolves CL-9634

@linear-code

linear-code Bot commented Sep 30, 2026

Copy link
Copy Markdown

CL-9634

@TheGreatAxios
TheGreatAxios changed the base branch from cl-9633-packages-worker to main September 30, 2026 18:39
@TheGreatAxios
TheGreatAxios merged commit 1a443e2 into main Sep 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant