[Durable Objects] Add changelog for ctx.id.name support by iglesiasbrandon · Pull Request #30843 · cloudflare/cloudflare-docs

iglesiasbrandon · 2026-05-15T18:30:07Z

Summary

Adds a changelog entry dated 2026-03-26 documenting that ctx.id.name is now populated inside a Durable Object when accessed via idFromName() or getByName().

The entry:

Highlights that the in-Durable-Object ctx.id.name value now matches what the client sees on the stub's ID.
Explains the prior pain point (TypeScript types implied name would be populated, but it was always undefined inside the Durable Object).
Documents the four cases where name is undefined (unique IDs, idFromString(), names > 1024 bytes).

References

workerd PR: Support ctx.id.name in local dev for Durable Objects workerd#6421
Original issue: bug: DurableObjectId::id.name doesn't work workerd#2240

Add changelog entry dated 2026-03-26 documenting that ctx.id.name is now populated inside a Durable Object when accessed via idFromName() or getByName(), matching the name visible on the client-side stub.

github-actions · 2026-05-15T18:30:49Z

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
`/src/content/changelog/`	`@cloudflare/pm-changelogs`, `@cloudflare/product-owners`

github-actions · 2026-05-15T18:53:59Z

Preview URL: https://64860fe9.preview.developers.cloudflare.com
Preview Branch URL: https://changelog-do-id-name.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/changelog/post/2026-03-26-durable-object-id-name/	https://changelog-do-id-name.preview.developers.cloudflare.com/changelog/post/2026-03-26-durable-object-id-name/

vy-ton · 2026-05-15T20:46:21Z

+date: 2026-03-26
+---
+
+`ctx.id.name` inside a Durable Object now matches what you see client-side. If a Worker accesses a Durable Object via `idFromName()` or `getByName()`, the same name is now available on `ctx.id.name` inside the object — no need to pass it through method arguments or persist it in storage.


Lead with your second sentence. The first sentence is confusing to a user - what is "what you see client-side".

When your Worker accesses a Durable Object via getByName()oridFromName(), ...

good to frame direct to user

vy-ton · 2026-05-15T20:50:18Z

+
+`ctx.id.name` inside a Durable Object now matches what you see client-side. If a Worker accesses a Durable Object via `idFromName()` or `getByName()`, the same name is now available on `ctx.id.name` inside the object — no need to pass it through method arguments or persist it in storage.
+
+Previously, the TypeScript type for `ctx.id` declared `name` as `string | undefined`, which led developers and LLM-based coding assistants to assume the name would be available inside the Durable Object. In reality, it was always `undefined` from inside, forcing manual workarounds.


let's remove focus on what wasn't supported, distracts here. Instead can emphasize this now correctly matches the Workers runtime types

vy-ton · 2026-05-15T20:50:35Z

+
+```js
+export class ChatRoom extends DurableObject {
+  async fetch(request) {


feature a RPC method over fetch()

vy-ton · 2026-05-15T20:51:59Z

+products:
+  - durable-objects
+  - workers
+date: 2026-03-26


The note on https://wiki.cfdata.org/spaces/PS/blog/2026/05/15/1406850466/Cloudflare+Observability+Where+we+go+from+here mentions 2026-03-15 so should these dates match?

hey @vy-ton did you add the correct link here?

struggling to find what I was looking at, should just confirm @maxmcd when ctx.id.name was first available

2026-03-15 is the notable date: https://developers.cloudflare.com/durable-objects/api/id/#name

vy-ton · 2026-05-15T20:56:13Z

+
+A few things to note about when `ctx.id.name` is set:
+
+- **Populated** when the Durable Object is accessed via `idFromName()` or `getByName()`.


already said so can remove to avoid repeat

I would mention something about alarms - we want users to understand that ctx.id.name is something that is available no matter how the DO is invoked. For example, the passing in name as arguement doesnt work for alarms

Does ctx.id.name work locally?

it seems so!
https://github.com/cloudflare/workerd/pulls?q=6421

vy-ton · 2026-05-15T20:57:53Z

+- **Populated** when the Durable Object is accessed via `idFromName()` or `getByName()`.
+- **`undefined`** for Durable Objects created with `newUniqueId()`.
+- **`undefined`** when accessed via `idFromString()`, even if the ID was originally created from a name.
+- **`undefined`** for names longer than 1,024 bytes.


This raises user question of what the limit for DO names are. Let's make sure thats documented

…30897) Addresses review feedback from #30843: - Rename file and update frontmatter date to 2026-03-15 to match the production rollout date documented in src/content/docs/durable-objects/api/id.mdx. - Lead with the user-facing 'When your Worker accesses...' framing. - Remove the TypeScript-types backstory; emphasize that runtime now matches the Workers runtime types. - Replace the fetch() code example with an RPC method. - Drop the redundant 'Populated' bullet; link the 1,024-byte caveat to the API reference. - Call out alarms as a primary use case. - Note that this works in local development with wrangler dev. Co-authored-by: iglesiasbrandon <5313116+iglesiasbrandon@users.noreply.github.com>

[Durable Objects] Add changelog for ctx.id.name support

64860fe

Add changelog entry dated 2026-03-26 documenting that ctx.id.name is now populated inside a Durable Object when accessed via idFromName() or getByName(), matching the name visible on the client-side stub.

iglesiasbrandon requested a review from a team as a code owner May 15, 2026 18:30

github-actions Bot added product:changelog size/s labels May 15, 2026

rianvdm approved these changes May 15, 2026

View reviewed changes

rianvdm merged commit 3fa3683 into production May 15, 2026
18 checks passed

rianvdm deleted the changelog-do-id-name branch May 15, 2026 20:34

vy-ton reviewed May 15, 2026

View reviewed changes

This was referenced May 18, 2026

[Durable Objects] Address review feedback on ctx.id.name changelog #30897

Merged

[Durable Objects] Document ctx.id.jurisdiction and improve ctx.id.name scanability #30900

Merged


		`ctx.id.name` inside a Durable Object now matches what you see client-side. If a Worker accesses a Durable Object via `idFromName()` or `getByName()`, the same name is now available on `ctx.id.name` inside the object — no need to pass it through method arguments or persist it in storage.

		Previously, the TypeScript type for `ctx.id` declared `name` as `string \| undefined`, which led developers and LLM-based coding assistants to assume the name would be available inside the Durable Object. In reality, it was always `undefined` from inside, forcing manual workarounds.


		A few things to note about when `ctx.id.name` is set:

		- Populated when the Durable Object is accessed via `idFromName()` or `getByName()`.

Uh oh!

Conversation

iglesiasbrandon commented May 15, 2026

Summary

References

Uh oh!

github-actions Bot commented May 15, 2026

Uh oh!

github-actions Bot commented May 15, 2026

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants