Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / temporal-agent-harness

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the signals and issues that cite it, below.

2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-cors

The packaged server binds 0.0.0.0 with no authentication; main adds wildcard CORS. temporal-agent-harness serve, the path the README leads with, listens on every interface with no authentication. Its endpoints approve tool calls (with remember), post callback results, send messages, and at 0.4.0 run operator commands including /approvals skip. Session ids come from GET /api/sessions and tool ids from /api/attach. On main, #139 adds wildcard CORS so a tic-tac-toe HTML file opened from disk can call the API. The code comment justifies it because nothing is credentialed. That reasoning misses the point: the uncredentialed endpoints are the authority. With wildcard CORS, any web page the operator visits can make JSON POSTs to the server and read the responses, subject to whatever local-network protections the browser applies. The coding example’s shim reaches the agent through this same server (coding_agent/README.md “How it maps to the harness”).

Channel: bind default preview-or-beta (0.4.0 wheel); CORS main-unreleased. Half: defect. Date: 0.0.0.0 default present at 0.4.0; CORS added 2026-09-17 in #139 (d7a55f8855).

Operator consequence: Run serve --host 127.0.0.1 on 0.4.0, and do not run the main-branch server with a coding agent attached. The 0.4.0 wheel has no CORS, but its 0.0.0.0 default exposes approvals to the LAN. Watch the next tag for whether #139’s CORS ships, and for a loopback default.

Receipt

Finding metadata

Confidence
medium

Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0

Finding ID: 2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-cors

Accepted signals

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Temporal Agent Harness
    tagged commit file2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-corstemporal-community/temporal-agent-harness / temporal_agent_harness/web/cli.py#L121tagged commit file2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-corstemporal-community/temporal-agent-harness / temporal_agent_harness/web/serve.py#L44tagged commit file2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-corstemporal-community/temporal-agent-harness / temporal_agent_harness/web/app.py#L281-L290tagged commit file2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-corstemporal-community/temporal-agent-harness / README.md#L579-L584commit2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-corsgithub.com/temporal-community/temporal-agent-harness/commit/d7a55f8855c31eb1a3281d2502f626c8a153aa44tagged commit file2026-09-21-temporal-agent-harness-the-packaged-server-binds-0-0-0-0-with-no-authentication-main-adds-wildcard-corstemporal-community/temporal-agent-harness / temporal_agent_harness/web/app.py#L152-L160

Versioned source: run artifact