Status: Future idea, not scheduled (currently considered a non-goal). Lives in the v0.5+ ""maybe"" bucket of the roadmap.
Summary
A no-Temporal-required dev/test mode for quick iteration without spinning up a worker + server.
Why this might matter
Local dev / unit tests / quick prototyping shouldn't need a full Temporal stack.
Why not scheduled (and why it's a non-goal today)
- Temporal IS the runtime; a non-durable variant splits the library's audience.
- Existing solutions (
testcontainers Temporal dev server) cover most local-dev needs.
- Would only revisit if the OSS community explicitly asks for it.
Open questions
- Would this fragment examples / docs?
- Could be done via a thin in-memory Temporal-API shim rather than a parallel agent runtime?
Status: Future idea, not scheduled (currently considered a non-goal). Lives in the v0.5+ ""maybe"" bucket of the roadmap.
Summary
A no-Temporal-required dev/test mode for quick iteration without spinning up a worker + server.
Why this might matter
Local dev / unit tests / quick prototyping shouldn't need a full Temporal stack.
Why not scheduled (and why it's a non-goal today)
testcontainersTemporal dev server) cover most local-dev needs.Open questions