Skip to content

remove references to now-archived VSCode debugger plugin #494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
angelazhou32 merged 1 commit into from
Sep 17, 2026
Merged

remove references to now-archived VSCode debugger plugin #494

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions docs/tutorials/typescript/background-check/durable-execution.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,6 @@ keywords:
- tests
- typescript
- typescript sdk
- vscode debugger extension
tags:
- determinism
- durable-execution
Expand All @@ -28,7 +27,6 @@ tags:
- tests
- typescript
- typescript-sdk
- vscode-debugger-extension
---

When it comes to the Temporal Platform's ability to durably execute code, the SDK's ability to [Replay](https://docs.temporal.io/encyclopedia/temporal-sdks#replays) a Workflow Execution is a major aspect of that.
Expand Down Expand Up @@ -420,14 +418,6 @@ Progress:
BinaryChecksum:da7cae1f96abf543ca8b6e7c3f3ab072}
```

### VSCode Debugger extension {#static-analysis}

Non-deterministic code can be hard to catch while developing Workflows.
You can leverage the Temporal TypeScript VSCode extenstion to debug your Workflows by their ID or Workflow Event History file.
Use the [Temporal Debugger for VS Code](https://marketplace.visualstudio.com/items?itemName=temporal-technologies.temporalio).

See the [vscode-debugger-extension README](https://github.com/temporalio/vscode-debugger-extension/blob/main/README.md) for details on how to use it.

### Does this mean Temporal can't be used for AI? {#temporal-for-ai}

No — the opposite. Workflow determinism is exactly what makes Temporal a strong fit for AI applications. LLM calls, tool use, and agent steps are non-deterministic by nature, so you place them in Activities. This separation makes the orchestration dependable even though these individual steps are non-deterministic, so your agent can recover from crashes, retry failed LLM calls, and resume long-running tasks without losing state.
Expand Down