fix(cloudflare): Set agent conversation id on the onRequest path

[sergical]

An Agent that handles a plain HTTP request — a webhook, a REST endpoint — produces AI spans with no gen_ai.conversation.id, so Sentry can't group its turns into a conversation. Chat agents and @callable() RPC agents work fine.

How the agent is reached	Handler	gen_ai.conversation.id
Chat	onChatMessage	set
@callable() over WebSocket	onMessage	set
HTTP	onRequest	missing — fixed here

We set the id inside the onChatMessage and onMessage proxies. An HTTP request touches neither: it arrives through the obj.fetch proxy in durableobject.ts, which never sets it. This PR wraps onRequest the same way the other two are wrapped.

Review notes:

• Wrapping after construction is safe — agents installs onRequest as an own property in the Agent constructor, same as onMessage.
• It stays out of the obj.fetch proxy, which instrumentDurableObjectWithSentry shares — plain Durable Objects shouldn't run agent-specific code.

ai-streaming.test.ts already drove both fixture agents over HTTP but never asserted this attribute, which is why CI was green. It does now, plus unit tests that fail without the src change. Confirmed on a deployed Worker.

Closes#22845

[JPeer264]

I could have sworn I added this already. I think I got so many different experiments and different branches that on my clean up that got removed. Thanks for adding that.

[sergical]

An Agent that handles a plain HTTP request — a webhook, a REST endpoint — produces AI spans with no gen_ai.conversation.id, so Sentry can't group its turns into a conversation. Chat agents and @callable() RPC agents work fine.

How the agent is reached	Handler	gen_ai.conversation.id
Chat	onChatMessage	set
@callable() over WebSocket	onMessage	set
HTTP	onRequest	missing — fixed here

We set the id inside the onChatMessage and onMessage proxies. An HTTP request touches neither: it arrives through the obj.fetch proxy in durableobject.ts, which never sets it. This PR wraps onRequest the same way the other two are wrapped.

Review notes:

• Wrapping after construction is safe — agents installs onRequest as an own property in the Agent constructor, same as onMessage.
• It stays out of the obj.fetch proxy, which instrumentDurableObjectWithSentry shares — plain Durable Objects shouldn't run agent-specific code.

ai-streaming.test.ts already drove both fixture agents over HTTP but never asserted this attribute, which is why CI was green. It does now, plus unit tests that fail without the src change. Confirmed on a deployed Worker.

Closes#22845

[JPeer264]

I could have sworn I added this already. I think I got so many different experiments and different branches that on my clean up that got removed. Thanks for adding that.

[sergical]

An Agent that handles a plain HTTP request — a webhook, a REST endpoint — produces AI spans with no gen_ai.conversation.id, so Sentry can't group its turns into a conversation. Chat agents and @callable() RPC agents work fine.

How the agent is reached	Handler	gen_ai.conversation.id
Chat	onChatMessage	set
@callable() over WebSocket	onMessage	set
HTTP	onRequest	missing — fixed here

We set the id inside the onChatMessage and onMessage proxies. An HTTP request touches neither: it arrives through the obj.fetch proxy in durableobject.ts, which never sets it. This PR wraps onRequest the same way the other two are wrapped.

Review notes:

• Wrapping after construction is safe — agents installs onRequest as an own property in the Agent constructor, same as onMessage.
• It stays out of the obj.fetch proxy, which instrumentDurableObjectWithSentry shares — plain Durable Objects shouldn't run agent-specific code.

ai-streaming.test.ts already drove both fixture agents over HTTP but never asserted this attribute, which is why CI was green. It does now, plus unit tests that fail without the src change. Confirmed on a deployed Worker.

Closes#22845

[JPeer264]

I could have sworn I added this already. I think I got so many different experiments and different branches that on my clean up that got removed. Thanks for adding that.

[sergical]

An Agent that handles a plain HTTP request — a webhook, a REST endpoint — produces AI spans with no gen_ai.conversation.id, so Sentry can't group its turns into a conversation. Chat agents and @callable() RPC agents work fine.

How the agent is reached	Handler	gen_ai.conversation.id
Chat	onChatMessage	set
@callable() over WebSocket	onMessage	set
HTTP	onRequest	missing — fixed here

We set the id inside the onChatMessage and onMessage proxies. An HTTP request touches neither: it arrives through the obj.fetch proxy in durableobject.ts, which never sets it. This PR wraps onRequest the same way the other two are wrapped.

Review notes:

• Wrapping after construction is safe — agents installs onRequest as an own property in the Agent constructor, same as onMessage.
• It stays out of the obj.fetch proxy, which instrumentDurableObjectWithSentry shares — plain Durable Objects shouldn't run agent-specific code.

ai-streaming.test.ts already drove both fixture agents over HTTP but never asserted this attribute, which is why CI was green. It does now, plus unit tests that fail without the src change. Confirmed on a deployed Worker.

Closes#22845

[JPeer264]

I could have sworn I added this already. I think I got so many different experiments and different branches that on my clean up that got removed. Thanks for adding that.

[sergical]

An Agent that handles a plain HTTP request — a webhook, a REST endpoint — produces AI spans with no gen_ai.conversation.id, so Sentry can't group its turns into a conversation. Chat agents and @callable() RPC agents work fine.

How the agent is reached	Handler	gen_ai.conversation.id
Chat	onChatMessage	set
@callable() over WebSocket	onMessage	set
HTTP	onRequest	missing — fixed here

We set the id inside the onChatMessage and onMessage proxies. An HTTP request touches neither: it arrives through the obj.fetch proxy in durableobject.ts, which never sets it. This PR wraps onRequest the same way the other two are wrapped.

Review notes:

• Wrapping after construction is safe — agents installs onRequest as an own property in the Agent constructor, same as onMessage.
• It stays out of the obj.fetch proxy, which instrumentDurableObjectWithSentry shares — plain Durable Objects shouldn't run agent-specific code.

ai-streaming.test.ts already drove both fixture agents over HTTP but never asserted this attribute, which is why CI was green. It does now, plus unit tests that fail without the src change. Confirmed on a deployed Worker.

Closes#22845

[JPeer264]

I could have sworn I added this already. I think I got so many different experiments and different branches that on my clean up that got removed. Thanks for adding that.

[sergical]

An Agent that handles a plain HTTP request — a webhook, a REST endpoint — produces AI spans with no gen_ai.conversation.id, so Sentry can't group its turns into a conversation. Chat agents and @callable() RPC agents work fine.

How the agent is reached	Handler	gen_ai.conversation.id
Chat	onChatMessage	set
@callable() over WebSocket	onMessage	set
HTTP	onRequest	missing — fixed here

We set the id inside the onChatMessage and onMessage proxies. An HTTP request touches neither: it arrives through the obj.fetch proxy in durableobject.ts, which never sets it. This PR wraps onRequest the same way the other two are wrapped.

Review notes:

• Wrapping after construction is safe — agents installs onRequest as an own property in the Agent constructor, same as onMessage.
• It stays out of the obj.fetch proxy, which instrumentDurableObjectWithSentry shares — plain Durable Objects shouldn't run agent-specific code.

ai-streaming.test.ts already drove both fixture agents over HTTP but never asserted this attribute, which is why CI was green. It does now, plus unit tests that fail without the src change. Confirmed on a deployed Worker.

Closes#22845

[JPeer264]

I could have sworn I added this already. I think I got so many different experiments and different branches that on my clean up that got removed. Thanks for adding that.

[sergical]

An Agent that handles a plain HTTP request — a webhook, a REST endpoint — produces AI spans with no gen_ai.conversation.id, so Sentry can't group its turns into a conversation. Chat agents and @callable() RPC agents work fine.

How the agent is reached	Handler	gen_ai.conversation.id
Chat	onChatMessage	set
@callable() over WebSocket	onMessage	set
HTTP	onRequest	missing — fixed here

We set the id inside the onChatMessage and onMessage proxies. An HTTP request touches neither: it arrives through the obj.fetch proxy in durableobject.ts, which never sets it. This PR wraps onRequest the same way the other two are wrapped.

Review notes:

• Wrapping after construction is safe — agents installs onRequest as an own property in the Agent constructor, same as onMessage.
• It stays out of the obj.fetch proxy, which instrumentDurableObjectWithSentry shares — plain Durable Objects shouldn't run agent-specific code.

ai-streaming.test.ts already drove both fixture agents over HTTP but never asserted this attribute, which is why CI was green. It does now, plus unit tests that fail without the src change. Confirmed on a deployed Worker.

Closes#22845

[JPeer264]

I could have sworn I added this already. I think I got so many different experiments and different branches that on my clean up that got removed. Thanks for adding that.

[sergical]

An Agent that handles a plain HTTP request — a webhook, a REST endpoint — produces AI spans with no gen_ai.conversation.id, so Sentry can't group its turns into a conversation. Chat agents and @callable() RPC agents work fine.

How the agent is reached	Handler	gen_ai.conversation.id
Chat	onChatMessage	set
@callable() over WebSocket	onMessage	set
HTTP	onRequest	missing — fixed here

We set the id inside the onChatMessage and onMessage proxies. An HTTP request touches neither: it arrives through the obj.fetch proxy in durableobject.ts, which never sets it. This PR wraps onRequest the same way the other two are wrapped.

Review notes:

• Wrapping after construction is safe — agents installs onRequest as an own property in the Agent constructor, same as onMessage.
• It stays out of the obj.fetch proxy, which instrumentDurableObjectWithSentry shares — plain Durable Objects shouldn't run agent-specific code.

ai-streaming.test.ts already drove both fixture agents over HTTP but never asserted this attribute, which is why CI was green. It does now, plus unit tests that fail without the src change. Confirmed on a deployed Worker.

Closes#22845

[JPeer264]

I could have sworn I added this already. I think I got so many different experiments and different branches that on my clean up that got removed. Thanks for adding that.