Profiles / temporal-community
Temporal Agent Harness
Temporal Agent Harness 0.6.0 puts Code Mode in workflow workers and makes history compatibility part of the upgrade.
No longer tracked. Frontier stopped following Temporal Agent Harness on 2026-10-24: a community reference harness with little outside adoption (about 120 GitHub stars at retirement); its durable-execution design remains a useful precedent, but it no longer earns a weekly read. What follows is the last dated posture, from 2026-10-13; check the project's own release notes for anything newer.
Operator Stance / as of 2026-10-13
- Use it for
- Pilot durable tool approvals if your team already operates Temporal and can own experimental worker upgrades.
- Avoid it for
- Shared consoles without caller authentication and authorization; inspect the approval and message routes.
- Watch next
- A recorded replay of existing histories against the 0.6.0 Code Mode change.
Where it stands, 2026-10-13
On 3 October 2026, 0.6.0 moved Code Mode, its script interpreter, into workflow workers and replaced sandbox snapshots with replay against recorded tool results. For an operator moving 0.5.0 histories, the next job is testing worker compatibility.
For a bounded Temporal pilot, install temporal-agent-harness[ui]==0.6.0.
0.6.0 is a GitHub prerelease,
with Pre-Alpha status and Python >=3.11 on PyPI.
The README calls it experimental and warns that APIs will change.
Budget to own the experiment.
Check approval authority, worker compatibility, and optional integrations before choosing your pilot.
Who can release a waiting tool
Protect the server before connecting real tools. It binds to 0.0.0.0 by
default
and accepts approvals, messages and callback results without authenticating
the caller.
Since 0.5.0, wildcard CORS permits cross-origin reads and JSON requests when
the browser and network allow access.
Bind with --host 127.0.0.1 and add authentication and origin checks. Loopback
alone leaves that browser-permitted path open.
Remove or gate handlers that can relax approval policy. Gated calls park as
workflow waits for approval.
0.5.0 replaced the packaged skip-all route with first-class messages,
but examples offer policy handlers with a dangerously_skip_all choice.
model_callable=False filters the default generated toolset;
HTTP callers
and parents granted dangerously_allow_all() can still reach those
handlers.
A Temporal client can override the starting policy.
Relaxing it releases permitted calls already waiting.
Decide who may change policy before adapting the examples.
Try auto approval for routine decisions, then audit its denials. Auto mode shipped in 0.5.0 and can approve or deny unattended; errors and unusable results escalate. Enable the policy, define criteria and wire an evaluator.
For Jev, the TypeSafe-backed approval evaluator,
install the jev extra and set TYPESAFE_API_KEY on the worker.
Pin a concrete model instead of the jev-latest default;
Jev’s confidence and irreversibility checks are evaluator-specific.
Allow for arguments, criteria and optional state
going to TypeSafe
and the request entering workflow history.
For this Temporal pilot, compare time saved on routine prompts with time spent writing criteria, reviewing denials, controlling console access and testing worker upgrades. Keep auto approval only if it improves completed jobs per hour of human attention.
Keep argument-sensitive tools out of Always allow. The coding example’s
OpenCode shim maps an “always” reply to remember=true,
granting the bare tool name
and bypassing auto mode while that name remains allowed.
What changes on the workers
Replay-test Code Mode, the script interpreter, before moving existing
workflow histories to 0.6.0.
Install temporal-agent-harness[ui,code-mode]==0.6.0 on every workflow
worker serving Code Mode, retaining pydantic-monty 1.0.0.
Keep relevant old histories on compatible workers until a versioned cutover
passes a recorded replay of representative 0.5.0 histories on 0.6.0
workers, recording worker and Monty versions and outcomes; no compatibility path was found in the change.
Make activity-backed tool effects idempotent: the default supplies a
30-second start-to-close timeout without an explicit retry override.
Migrate 0.4.0 clients and agents together. Follow the message migration, the state migration and the lifecycle migration. Handle invalid initialization as a terminal start failure, and put essential failure cleanup elsewhere because teardown does not run on workflow failure. Keep console and server aligned with the 0.5.0 state-patch guard.
Refresh checkout locks separately from the harness version. The 0.6.0 root lock and Nexus lock retain urllib3 2.7.0. Its affected streaming path can spin indefinitely on a malicious chunked Deflate response; 2.8.0 fixes it. The root update is main-only and leaves Nexus unchanged. Inspect installed versions and affected call paths; wheel resolution can differ from checkout locks.
What the optional integrations require
Review the generated plan before pressing Run. DAG Studio is a checkout-only example for inspecting generated plans before executing them with a separate Run action. Inspect the script and per-step tools. Packaged preflight checks syntax and types without dispatching host tools; it also briefly starts and discards a clean script. The example uses simulated tools and skips their approvals. Set real authorization before replacing them. Preflight cannot decide what a plan should be allowed to do.
Give chat approval controls only to intended approvers. The repository-only Slack/Discord bridge lets anyone who reaches its buttons under platform permissions decide, without an owner or permitted-user check. Choose the channel’s participants accordingly: every message handler is also offered there.
Size shared storage when adopting the Gemini conversation helper. 0.6.0 stops retrying Gemini 4xx errors other than 408 and 429. In custom loops, adopt the optional helper that sends the full conversation in every model activity input where needed. For multiple hosts, configure shared payload offload; the default is local disk at 1,500,000 bytes.
Pin npm client versions and recorded integrity hashes. The separate TypeScript client at 0.1.0 has no recorded provenance attestation; neither do React 0.1.0 or Svelte 0.1.0.
Use a checkout for Nexus MCP. Its published extra requires
temporal-nexus-mcp,
which the release documents as checkout-only.
Use the documented checkout/workspace
or explicitly verify a trusted private index.
Keep main’s file viewer out of shared consoles. As of this profile’s
date, virtual filesystems, memory bundles, the viewer and the separate
typesafe extra are main-only.
The viewer takes caller-supplied filesystem configuration and a task queue
without a session identity.
Wait for authenticated access limited to the session’s mounts before sharing
it.
What is unresolved
- Test the browsers that will reach your server. Test cross-origin reads and JSON requests against 0.6.0. Record browser versions, network policy and results to establish reachability under the shipped CORS configuration.
- Require released access controls before sharing a console. A tagged implementation and route tests rejecting unauthenticated callers, disallowed origins and cross-session file access would show whether the viewer boundary has changed.
- Resolve payload custody before using sensitive inputs. Check Temporal Cloud history-reader permissions and retention for agent payloads, and TypeSafe’s processing and retention of Jev requests before sending sensitive data. Published guidance and terms from each provider for those payloads would settle each service’s part.
- Verify npm archives against their stated source. An archive-to-source build comparison and a recorded source-linked provenance attestation would answer the two publication questions.
- Test the OpenCode shim before relying on protocol compatibility. Pin OpenCode and harness versions, exercise changed protocol fields and record whether the shim fails closed to settle behavior for that tested version pair.
Profile date and evidence
This profile is dated 2026-10-13. Use the evidence method to check it. This page establishes no later state.
Verification
open source commits / evidence floor: official docs / updated 2026-10-13
Verified claims
- 2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-cors / verified 2026-10-13
- 2026-09-21-temporal-agent-harness-in-the-coding-example-opencode-always-maps-to-remember-true-which-allow-lists-the-tool-by / verified 2026-10-13
- 2026-09-21-temporal-agent-harness-the-caller-s-agentconfig-approval-policy-wins-over-the-agent-s-default-dangerously-skip / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-0-5-0-ships-wildcard-cors-on-the-unauthenticated-all-interface-server / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-first-class-messages-shipped-in-0-5-0-the-packaged-skip-all-route-is-gone-and-the-examples / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-auto-mode-can-approve-or-deny-without-a-person-but-a-remembered-tool-name-bypasses-the-eva / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-0-6-0-moves-code-mode-into-the-workflow-old-code-mode-histories-need-a-tested-cutover / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-0-5-0-and-0-6-0-publishing-shas-match-their-current-tags-npm-clients-lack-recorded-provena / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-the-nexus-mcp-extra-cannot-resolve-from-public-pypi-alone-as-observed / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-the-repository-chat-server-sends-approvals-to-slack-and-discord-without-its-own-approver / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-0-6-0-adds-workflow-held-gemini-conversations-and-stops-retrying-nontransient-gemini-4xx / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-main-after-0-6-0-8-commits-unreleased-code-mode-gets-a-virtual-filesystem-and-agent-memory / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-0-5-0-guards-console-state-patches-against-prototype-chain-paths / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-0-5-0-adds-inspectable-agent-dag-scripts-and-code-mode-preflight-checks / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-release-locks-match-19-dependency-advisories-the-root-lock-update-is-main-only / verified 2026-10-13
- 2026-10-13-temporal-agent-harness-0-5-0-replaces-runner-state-and-authored-run-methods-with-declared-state-and-lifecycle-hoo / verified 2026-10-13
Featured in
- The Handoff Has an API / 2026-10-13
- Before the First Turn / 2026-09-21
Source policy: what Frontier watches and accepts as evidence
Edited and maintained by Bitter Frontier.