Vibe Check: Temporal SDKs are Not a Thin Client

In this livestream, Chad Retz (Temporal SDK maintainer, 4+ years at Temporal) digs into the open source code that powers your workflows.

We go beyond the surface and explore:
- Why Temporal is fully MIT licensed (and why that matters)
- The difference between the Temporal Server and the SDKs
- How the Python SDK turns your code into durable, replayable workflows
- What really happens when you call execute_workflow
- How workers poll, replay history, and deterministically execute your code
- Interceptors, activations, commands, and the Rust core
- Error handling, retries, and gRPC under the hood
- How to contribute to Temporal’s open source repos
- How Chad uses AI (Claude, Opus) to build SDK features across languages

If you’ve ever wondered how Temporal makes your code durable or why the SDKs are so “smart” then this is for you. 

🔗 Explore the repos: https://github.com/temporalio

Drop your questions in the comments and let us know what you want us to break down next.
---

Temporal is the simple, scalable, open source way to write and run reliable cloud applications. 

Learn more
Blog: https://temporal.io/blog
How Temporal Works: https://temporal.io/how-temporal-works
Community Slack: https://temporal.io/slack

Developer resources
Docs: https://docs.temporal.io
Courses: https://learn.temporal.io/courses
Support forum: https://community.temporal.io