October 2026 Summaries

No summary generated yet.

Temporal announced that the Oso team has joined the company to accelerate development of AI agent security and authorization capabilities within its enterprise agent platform. The move addresses the risks posed by agents, which can act across tools, services, and sensitive data without the natural restraint people typically apply to their access permissions, particularly during failures, retries, and crashes. Temporal’s Durable Execution platform already retains workflow state, approvals, rejections, and execution history through disruptions, enabling guardrails such as ensuring a refund agent cannot repeat or bypass an approval after restarting. With Oso’s authorization expertise, Temporal plans to add more precise identity propagation and policy enforcement so each agent action can be tied to the person it represents and their permitted authority. Existing Durable Execution, visibility, and Nexus connectivity remain available today, while the acquisition is intended to speed authorization features already under development without changing current product functionality.

A Rust SDK team member created Durable Trivia for RustConf to test whether a Replay 2026 ESP32-S3 conference badge could function as a real Temporal Activity Worker rather than relying on an HTTP proxy. In the game, Temporal Cloud stores durable Workflow state while a MacBook runs the Workflow Worker and controller, and badges poll a shared Task Queue, display questions, heartbeat while awaiting button input, and complete Activities with players’ answers. A deliberate button combination simulates a Worker crash by stopping heartbeats, allowing Temporal to retry the unanswered question on another badge while preserving scores, deadlines, and game state. Porting the Rust SDK required limited ESP-IDF compatibility patches for Tokio-related platform assumptions, missing 64-bit atomics, embedded platform discovery, and an unused parser that caused an Xtensa compiler failure, producing an 8.44 MB firmware image that fit comfortably in the badge’s application partition. Development also involved automated hardware-in-the-loop testing, Workflow versioning to revise task scheduling safely, external contributions from the SDK team, and a travel router to avoid venue-network uncertainty. Although getting the Worker running proved more feasible than expected, operating ten badges reliably revealed practical challenges, particularly an idle-sleep feature whose slow wake behavior confused booth visitors and had to be removed and reflashed during the conference.

Temporal describes Camper, a workflow-based system built on Temporal to coordinate security and other cross-repository campaigns, where completion means every finding has a recorded outcome such as a merged fix, documented exception, archived repository, or rejected proposal. Developed after manual coordination across Jira, GitHub, scanners, and Slack proved time-consuming, Camper creates durable campaign and finding workflows that can discover issues, create tickets, generate or request changes, open pull requests, wait for CI and reviews, retry failures, and retain state through restarts. Campaign specifications define scope, approval requirements, integrations, remediation tools, policies, and target repositories, while allowing operators to update guidance or add targets during execution. Camper uses deterministic Deputy transformations for supported changes, Codex for context-dependent candidate fixes, or ticket-only workflows when human remediation is preferable, while keeping maintainers in control of review and merging. By September 29, 2026, it had opened at least 150 public pull requests across 72 Temporal repositories, with 111 merged, and a Release Engineering credential migration demonstrated its applicability beyond Security. Camper can run locally with simulated integrations or connect to Temporal Cloud using the same workflow model, though it remains private and early as Temporal develops operational tooling, credential boundaries, and documentation ahead of a planned open-source release.