[web][web-shared][core] Make encrypted markers clickable and detect encryption before span selection by karthikscale3 · Pull Request #1716 · vercel/workflow

karthikscale3 · 2026-04-13T21:12:29Z

Summary

Early encryption detection: Added a lightweight probe that fetches a single event with full data after initial load to detect whether a run contains encrypted fields. This surfaces the Decrypt button in both the trace and events tabs before the user selects any span.
Clickable encrypted markers: Encrypted placeholders in JSON inspector views and attribute panels are now clickable buttons labeled "Decrypt" that trigger the decryption flow directly, rather than requiring the user to find and click the top-level Decrypt button.
hasEncryptedFields utility: New exported function in web-shared that checks a hydrated resource for encryption markers across input, output, metadata, error, and eventData fields.
Persist features.encryption flag in executionContext at run creation so the UI can detect encryption without a probe fetch

How it works

A new DecryptClickContext (React context) threads the onDecrypt callback from EntityDetailPanel and EventListView down to all nested DataInspector and EncryptedFieldBlock instances. When the context is present, encrypted markers render as clickable "Decrypt" buttons; when absent (e.g. no decryption support), they remain static "Encrypted" labels.

The encryption probe in useWorkflowTraceViewerData fires a background request for 1 event with withData: true after the initial load completes. If any field in the hydrated response is an encryption marker, hasEncryptedData is set to true and propagated to the UI.

Test plan

Open a run with encrypted data → Decrypt button appears in trace and events tabs without selecting a span
Expand an event row in the events tab → inline "Decrypt" label is clickable
Select a span in the trace tab → "Decrypt" button in attribute panel fields is full-width and clickable
Click any "Decrypt" marker → triggers decryption flow, data resolves
Open a run without encrypted data → no Decrypt button appears

…ryption at run level before span selection

karthikscale3 · 2026-04-13T23:02:40Z

I think @TooTallNate recently added an encryption tag to the run's context object. Should that be used as a way to detect encryption without fetching an event separately?
Great, yes, that would make this simpler. Will look

The change from #1652 added features.encryption to WorkflowMetadata which is a runtime-only value available inside workflow code via getWorkflowMetadata(). It's computed on-the-fly from whether an encryption key exists. So this wouldn't work for us since the executionContext still doesn't have this flag. I made a change in this PR to persist this flag in the executionContext so runs from this version can be inferred directly and over time we can remove the probe fallback.

ghost · 2026-04-14T01:27:17Z

Backported to stable (df115fd -> f1cc68f).

…ncryption before span selection (#1716) * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection

karthikscale3 · 2026-04-13T21:12:29Z

Summary

Early encryption detection: Added a lightweight probe that fetches a single event with full data after initial load to detect whether a run contains encrypted fields. This surfaces the Decrypt button in both the trace and events tabs before the user selects any span.
Clickable encrypted markers: Encrypted placeholders in JSON inspector views and attribute panels are now clickable buttons labeled "Decrypt" that trigger the decryption flow directly, rather than requiring the user to find and click the top-level Decrypt button.
hasEncryptedFields utility: New exported function in web-shared that checks a hydrated resource for encryption markers across input, output, metadata, error, and eventData fields.
Persist features.encryption flag in executionContext at run creation so the UI can detect encryption without a probe fetch

How it works

A new DecryptClickContext (React context) threads the onDecrypt callback from EntityDetailPanel and EventListView down to all nested DataInspector and EncryptedFieldBlock instances. When the context is present, encrypted markers render as clickable "Decrypt" buttons; when absent (e.g. no decryption support), they remain static "Encrypted" labels.

The encryption probe in useWorkflowTraceViewerData fires a background request for 1 event with withData: true after the initial load completes. If any field in the hydrated response is an encryption marker, hasEncryptedData is set to true and propagated to the UI.

Test plan

Open a run with encrypted data → Decrypt button appears in trace and events tabs without selecting a span
Expand an event row in the events tab → inline "Decrypt" label is clickable
Select a span in the trace tab → "Decrypt" button in attribute panel fields is full-width and clickable
Click any "Decrypt" marker → triggers decryption flow, data resolves
Open a run without encrypted data → no Decrypt button appears

…ryption at run level before span selection

karthikscale3 · 2026-04-13T23:02:40Z

I think @TooTallNate recently added an encryption tag to the run's context object. Should that be used as a way to detect encryption without fetching an event separately?
Great, yes, that would make this simpler. Will look

The change from #1652 added features.encryption to WorkflowMetadata which is a runtime-only value available inside workflow code via getWorkflowMetadata(). It's computed on-the-fly from whether an encryption key exists. So this wouldn't work for us since the executionContext still doesn't have this flag. I made a change in this PR to persist this flag in the executionContext so runs from this version can be inferred directly and over time we can remove the probe fallback.

ghost · 2026-04-14T01:27:17Z

Backported to stable (df115fd -> f1cc68f).

…ncryption before span selection (#1716) * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection

karthikscale3 · 2026-04-13T21:12:29Z

Summary

Early encryption detection: Added a lightweight probe that fetches a single event with full data after initial load to detect whether a run contains encrypted fields. This surfaces the Decrypt button in both the trace and events tabs before the user selects any span.
Clickable encrypted markers: Encrypted placeholders in JSON inspector views and attribute panels are now clickable buttons labeled "Decrypt" that trigger the decryption flow directly, rather than requiring the user to find and click the top-level Decrypt button.
hasEncryptedFields utility: New exported function in web-shared that checks a hydrated resource for encryption markers across input, output, metadata, error, and eventData fields.
Persist features.encryption flag in executionContext at run creation so the UI can detect encryption without a probe fetch

How it works

A new DecryptClickContext (React context) threads the onDecrypt callback from EntityDetailPanel and EventListView down to all nested DataInspector and EncryptedFieldBlock instances. When the context is present, encrypted markers render as clickable "Decrypt" buttons; when absent (e.g. no decryption support), they remain static "Encrypted" labels.

The encryption probe in useWorkflowTraceViewerData fires a background request for 1 event with withData: true after the initial load completes. If any field in the hydrated response is an encryption marker, hasEncryptedData is set to true and propagated to the UI.

Test plan

Open a run with encrypted data → Decrypt button appears in trace and events tabs without selecting a span
Expand an event row in the events tab → inline "Decrypt" label is clickable
Select a span in the trace tab → "Decrypt" button in attribute panel fields is full-width and clickable
Click any "Decrypt" marker → triggers decryption flow, data resolves
Open a run without encrypted data → no Decrypt button appears

…ryption at run level before span selection

karthikscale3 · 2026-04-13T23:02:40Z

I think @TooTallNate recently added an encryption tag to the run's context object. Should that be used as a way to detect encryption without fetching an event separately?
Great, yes, that would make this simpler. Will look

The change from #1652 added features.encryption to WorkflowMetadata which is a runtime-only value available inside workflow code via getWorkflowMetadata(). It's computed on-the-fly from whether an encryption key exists. So this wouldn't work for us since the executionContext still doesn't have this flag. I made a change in this PR to persist this flag in the executionContext so runs from this version can be inferred directly and over time we can remove the probe fallback.

ghost · 2026-04-14T01:27:17Z

Backported to stable (df115fd -> f1cc68f).

…ncryption before span selection (#1716) * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection

karthikscale3 · 2026-04-13T21:12:29Z

Summary

Early encryption detection: Added a lightweight probe that fetches a single event with full data after initial load to detect whether a run contains encrypted fields. This surfaces the Decrypt button in both the trace and events tabs before the user selects any span.
Clickable encrypted markers: Encrypted placeholders in JSON inspector views and attribute panels are now clickable buttons labeled "Decrypt" that trigger the decryption flow directly, rather than requiring the user to find and click the top-level Decrypt button.
hasEncryptedFields utility: New exported function in web-shared that checks a hydrated resource for encryption markers across input, output, metadata, error, and eventData fields.
Persist features.encryption flag in executionContext at run creation so the UI can detect encryption without a probe fetch

How it works

A new DecryptClickContext (React context) threads the onDecrypt callback from EntityDetailPanel and EventListView down to all nested DataInspector and EncryptedFieldBlock instances. When the context is present, encrypted markers render as clickable "Decrypt" buttons; when absent (e.g. no decryption support), they remain static "Encrypted" labels.

The encryption probe in useWorkflowTraceViewerData fires a background request for 1 event with withData: true after the initial load completes. If any field in the hydrated response is an encryption marker, hasEncryptedData is set to true and propagated to the UI.

Test plan

Open a run with encrypted data → Decrypt button appears in trace and events tabs without selecting a span
Expand an event row in the events tab → inline "Decrypt" label is clickable
Select a span in the trace tab → "Decrypt" button in attribute panel fields is full-width and clickable
Click any "Decrypt" marker → triggers decryption flow, data resolves
Open a run without encrypted data → no Decrypt button appears

…ryption at run level before span selection

karthikscale3 · 2026-04-13T23:02:40Z

I think @TooTallNate recently added an encryption tag to the run's context object. Should that be used as a way to detect encryption without fetching an event separately?
Great, yes, that would make this simpler. Will look

The change from #1652 added features.encryption to WorkflowMetadata which is a runtime-only value available inside workflow code via getWorkflowMetadata(). It's computed on-the-fly from whether an encryption key exists. So this wouldn't work for us since the executionContext still doesn't have this flag. I made a change in this PR to persist this flag in the executionContext so runs from this version can be inferred directly and over time we can remove the probe fallback.

ghost · 2026-04-14T01:27:17Z

Backported to stable (df115fd -> f1cc68f).

…ncryption before span selection (#1716) * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection

karthikscale3 · 2026-04-13T21:12:29Z

Summary

Early encryption detection: Added a lightweight probe that fetches a single event with full data after initial load to detect whether a run contains encrypted fields. This surfaces the Decrypt button in both the trace and events tabs before the user selects any span.
Clickable encrypted markers: Encrypted placeholders in JSON inspector views and attribute panels are now clickable buttons labeled "Decrypt" that trigger the decryption flow directly, rather than requiring the user to find and click the top-level Decrypt button.
hasEncryptedFields utility: New exported function in web-shared that checks a hydrated resource for encryption markers across input, output, metadata, error, and eventData fields.
Persist features.encryption flag in executionContext at run creation so the UI can detect encryption without a probe fetch

How it works

A new DecryptClickContext (React context) threads the onDecrypt callback from EntityDetailPanel and EventListView down to all nested DataInspector and EncryptedFieldBlock instances. When the context is present, encrypted markers render as clickable "Decrypt" buttons; when absent (e.g. no decryption support), they remain static "Encrypted" labels.

The encryption probe in useWorkflowTraceViewerData fires a background request for 1 event with withData: true after the initial load completes. If any field in the hydrated response is an encryption marker, hasEncryptedData is set to true and propagated to the UI.

Test plan

Open a run with encrypted data → Decrypt button appears in trace and events tabs without selecting a span
Expand an event row in the events tab → inline "Decrypt" label is clickable
Select a span in the trace tab → "Decrypt" button in attribute panel fields is full-width and clickable
Click any "Decrypt" marker → triggers decryption flow, data resolves
Open a run without encrypted data → no Decrypt button appears

…ryption at run level before span selection

karthikscale3 · 2026-04-13T23:02:40Z

I think @TooTallNate recently added an encryption tag to the run's context object. Should that be used as a way to detect encryption without fetching an event separately?
Great, yes, that would make this simpler. Will look

The change from #1652 added features.encryption to WorkflowMetadata which is a runtime-only value available inside workflow code via getWorkflowMetadata(). It's computed on-the-fly from whether an encryption key exists. So this wouldn't work for us since the executionContext still doesn't have this flag. I made a change in this PR to persist this flag in the executionContext so runs from this version can be inferred directly and over time we can remove the probe fallback.

ghost · 2026-04-14T01:27:17Z

Backported to stable (df115fd -> f1cc68f).

…ncryption before span selection (#1716) * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection

karthikscale3 · 2026-04-13T21:12:29Z

Summary

Early encryption detection: Added a lightweight probe that fetches a single event with full data after initial load to detect whether a run contains encrypted fields. This surfaces the Decrypt button in both the trace and events tabs before the user selects any span.
Clickable encrypted markers: Encrypted placeholders in JSON inspector views and attribute panels are now clickable buttons labeled "Decrypt" that trigger the decryption flow directly, rather than requiring the user to find and click the top-level Decrypt button.
hasEncryptedFields utility: New exported function in web-shared that checks a hydrated resource for encryption markers across input, output, metadata, error, and eventData fields.
Persist features.encryption flag in executionContext at run creation so the UI can detect encryption without a probe fetch

How it works

A new DecryptClickContext (React context) threads the onDecrypt callback from EntityDetailPanel and EventListView down to all nested DataInspector and EncryptedFieldBlock instances. When the context is present, encrypted markers render as clickable "Decrypt" buttons; when absent (e.g. no decryption support), they remain static "Encrypted" labels.

The encryption probe in useWorkflowTraceViewerData fires a background request for 1 event with withData: true after the initial load completes. If any field in the hydrated response is an encryption marker, hasEncryptedData is set to true and propagated to the UI.

Test plan

Open a run with encrypted data → Decrypt button appears in trace and events tabs without selecting a span
Expand an event row in the events tab → inline "Decrypt" label is clickable
Select a span in the trace tab → "Decrypt" button in attribute panel fields is full-width and clickable
Click any "Decrypt" marker → triggers decryption flow, data resolves
Open a run without encrypted data → no Decrypt button appears

…ryption at run level before span selection

karthikscale3 · 2026-04-13T23:02:40Z

I think @TooTallNate recently added an encryption tag to the run's context object. Should that be used as a way to detect encryption without fetching an event separately?
Great, yes, that would make this simpler. Will look

The change from #1652 added features.encryption to WorkflowMetadata which is a runtime-only value available inside workflow code via getWorkflowMetadata(). It's computed on-the-fly from whether an encryption key exists. So this wouldn't work for us since the executionContext still doesn't have this flag. I made a change in this PR to persist this flag in the executionContext so runs from this version can be inferred directly and over time we can remove the probe fallback.

ghost · 2026-04-14T01:27:17Z

Backported to stable (df115fd -> f1cc68f).

…ncryption before span selection (#1716) * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection

karthikscale3 · 2026-04-13T21:12:29Z

Summary

Early encryption detection: Added a lightweight probe that fetches a single event with full data after initial load to detect whether a run contains encrypted fields. This surfaces the Decrypt button in both the trace and events tabs before the user selects any span.
Clickable encrypted markers: Encrypted placeholders in JSON inspector views and attribute panels are now clickable buttons labeled "Decrypt" that trigger the decryption flow directly, rather than requiring the user to find and click the top-level Decrypt button.
hasEncryptedFields utility: New exported function in web-shared that checks a hydrated resource for encryption markers across input, output, metadata, error, and eventData fields.
Persist features.encryption flag in executionContext at run creation so the UI can detect encryption without a probe fetch

How it works

A new DecryptClickContext (React context) threads the onDecrypt callback from EntityDetailPanel and EventListView down to all nested DataInspector and EncryptedFieldBlock instances. When the context is present, encrypted markers render as clickable "Decrypt" buttons; when absent (e.g. no decryption support), they remain static "Encrypted" labels.

The encryption probe in useWorkflowTraceViewerData fires a background request for 1 event with withData: true after the initial load completes. If any field in the hydrated response is an encryption marker, hasEncryptedData is set to true and propagated to the UI.

Test plan

Open a run with encrypted data → Decrypt button appears in trace and events tabs without selecting a span
Expand an event row in the events tab → inline "Decrypt" label is clickable
Select a span in the trace tab → "Decrypt" button in attribute panel fields is full-width and clickable
Click any "Decrypt" marker → triggers decryption flow, data resolves
Open a run without encrypted data → no Decrypt button appears

…ryption at run level before span selection

karthikscale3 · 2026-04-13T23:02:40Z

I think @TooTallNate recently added an encryption tag to the run's context object. Should that be used as a way to detect encryption without fetching an event separately?
Great, yes, that would make this simpler. Will look

The change from #1652 added features.encryption to WorkflowMetadata which is a runtime-only value available inside workflow code via getWorkflowMetadata(). It's computed on-the-fly from whether an encryption key exists. So this wouldn't work for us since the executionContext still doesn't have this flag. I made a change in this PR to persist this flag in the executionContext so runs from this version can be inferred directly and over time we can remove the probe fallback.

ghost · 2026-04-14T01:27:17Z

Backported to stable (df115fd -> f1cc68f).

…ncryption before span selection (#1716) * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection

karthikscale3 · 2026-04-13T21:12:29Z

Summary

Early encryption detection: Added a lightweight probe that fetches a single event with full data after initial load to detect whether a run contains encrypted fields. This surfaces the Decrypt button in both the trace and events tabs before the user selects any span.
Clickable encrypted markers: Encrypted placeholders in JSON inspector views and attribute panels are now clickable buttons labeled "Decrypt" that trigger the decryption flow directly, rather than requiring the user to find and click the top-level Decrypt button.
hasEncryptedFields utility: New exported function in web-shared that checks a hydrated resource for encryption markers across input, output, metadata, error, and eventData fields.
Persist features.encryption flag in executionContext at run creation so the UI can detect encryption without a probe fetch

How it works

A new DecryptClickContext (React context) threads the onDecrypt callback from EntityDetailPanel and EventListView down to all nested DataInspector and EncryptedFieldBlock instances. When the context is present, encrypted markers render as clickable "Decrypt" buttons; when absent (e.g. no decryption support), they remain static "Encrypted" labels.

The encryption probe in useWorkflowTraceViewerData fires a background request for 1 event with withData: true after the initial load completes. If any field in the hydrated response is an encryption marker, hasEncryptedData is set to true and propagated to the UI.

Test plan

Open a run with encrypted data → Decrypt button appears in trace and events tabs without selecting a span
Expand an event row in the events tab → inline "Decrypt" label is clickable
Select a span in the trace tab → "Decrypt" button in attribute panel fields is full-width and clickable
Click any "Decrypt" marker → triggers decryption flow, data resolves
Open a run without encrypted data → no Decrypt button appears

…ryption at run level before span selection

karthikscale3 · 2026-04-13T23:02:40Z

I think @TooTallNate recently added an encryption tag to the run's context object. Should that be used as a way to detect encryption without fetching an event separately?
Great, yes, that would make this simpler. Will look

The change from #1652 added features.encryption to WorkflowMetadata which is a runtime-only value available inside workflow code via getWorkflowMetadata(). It's computed on-the-fly from whether an encryption key exists. So this wouldn't work for us since the executionContext still doesn't have this flag. I made a change in this PR to persist this flag in the executionContext so runs from this version can be inferred directly and over time we can remove the probe fallback.

ghost · 2026-04-14T01:27:17Z

Backported to stable (df115fd -> f1cc68f).

…ncryption before span selection (#1716) * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection * Make encrypted markers clickable to trigger decryption and detect encryption at run level before span selection

karthikscale3 added 30 commits January 27, 2026 10:51

Merge branch 'main' of github.com:vercel/workflow
ad8b7f1

Merge branch 'main' of github.com:vercel/workflow
e0cb61b

Merge branch 'main' of github.com:vercel/workflow
051cadc

Merge branch 'main' of github.com:vercel/workflow
af8ac1f

Merge branch 'main' of github.com:vercel/workflow
e68e7d2

Merge branch 'main' of github.com:vercel/workflow
8305e5b

Merge branch 'main' of github.com:vercel/workflow
f3da688

Merge branch 'main' of github.com:vercel/workflow
f8ee413

Merge branch 'main' of github.com:vercel/workflow
589cbd7

Merge branch 'main' of github.com:vercel/workflow
e979fdf

Merge branch 'main' of github.com:vercel/workflow
d4baed2

Merge branch 'main' of github.com:vercel/workflow
53503a4

Merge branch 'main' of github.com:vercel/workflow
d51e2e4

Merge branch 'main' of github.com:vercel/workflow
5123088

Merge branch 'main' of github.com:vercel/workflow
dd1a307

Merge branch 'main' of github.com:vercel/workflow
00bcfcd

Merge branch 'main' of github.com:vercel/workflow
f6a157b

Merge branch 'main' of github.com:vercel/workflow
816f35b

Merge branch 'main' of github.com:vercel/workflow
2b87dce

Merge branch 'main' of github.com:vercel/workflow
146de28

Merge branch 'main' of github.com:vercel/workflow
0ef6455

Merge branch 'main' of github.com:vercel/workflow
2d8c690

Merge branch 'main' of github.com:vercel/workflow
3513471

Merge branch 'main' of github.com:vercel/workflow
0f5d29e

Merge branch 'main' of github.com:vercel/workflow
c76001e

Merge branch 'main' of github.com:vercel/workflow
f97184f

Merge branch 'main' of github.com:vercel/workflow
f71c531

Merge branch 'main' of github.com:vercel/workflow
530e598

Merge branch 'main' of github.com:vercel/workflow
ea38511

Merge branch 'main' of github.com:vercel/workflow
19b1a3f

vercelBotdeployed to Preview – workflow-docs April 13, 2026 21:30 View deployment

vercelBotdeployed to Preview – example-nextjs-workflow-webpack April 13, 2026 21:31 View deployment

vercelBotdeployed to Preview – workflow-swc-playground April 13, 2026 21:32 View deployment

karthikscale3 added 2 commits April 13, 2026 15:54

Make encrypted markers clickable to trigger decryption and detect enc…
938863e
…ryption at run level before span selection

Make encrypted markers clickable to trigger decryption and detect enc…
91ed4df
…ryption at run level before span selection

vercelBotdeployed to Preview – workbench-hono-workflow April 13, 2026 22:57 View deployment

vercelBotdeployed to Preview – workbench-vite-workflow April 13, 2026 22:57 View deployment

vercelBotdeployed to Preview – workbench-express-workflow April 13, 2026 22:57 View deployment

vercelBotdeployed to Preview – workbench-sveltekit-workflow April 13, 2026 22:57 View deployment

vercelBotdeployed to Preview – workbench-nitro-workflow April 13, 2026 22:57 View deployment

vercelBotdeployed to Preview – workbench-fastify-workflow April 13, 2026 22:57 View deployment

vercelBotdeployed to Preview – workbench-astro-workflow April 13, 2026 22:57 View deployment

vercelBotdeployed to Preview – example-workflow April 13, 2026 22:58 View deployment

vercelBotdeployed to Preview – workbench-nuxt-workflow April 13, 2026 22:58 View deployment

vercelBotdeployed to Preview – example-nextjs-workflow-turbopack April 13, 2026 22:58 View deployment

vercelBotdeployed to Preview – workflow-docs April 13, 2026 22:58 View deployment

vercelBotdeployed to Preview – example-nextjs-workflow-webpack April 13, 2026 22:58 View deployment

karthikscale3 requested a review from TooTallNate April 13, 2026 22:59

vercelBotdeployed to Preview – workflow-swc-playground April 13, 2026 23:00 View deployment

karthikscale3 changed the title ~~[web][web-shared] Make encrypted markers clickable and detect encryption before span selection~~[web][web-shared][core] Make encrypted markers clickable and detect encryption before span selectionApr 13, 2026

VaguelySerious approved these changes Apr 13, 2026
View reviewed changes

karthikscale3 merged commit df115fd into mainApr 14, 2026
101 of 105 checks passed

karthikscale3 deleted the karthik/fix-decryption-itg branch April 14, 2026 00:12

ghost mentioned this pull request Apr 13, 2026
Version Packages (beta) #1711
Merged

karthikscale3 added the backport-stable Cherry-pick this PR to the stable branch when merged label Apr 14, 2026

karthikscale3 mentioned this pull request Apr 14, 2026
[web-shared] Enable in-line decryption for data inspector in detail panel #1722
Merged