[thinkinginmath]

Safari blocks HTTPS pages from calling http://127.0.0.1 (mixed content). Chrome and Firefox allow it. This adds an HTTPS listener on loopback with a narrow, locally generated certificate.

Measured on macOS, 2026-09-19. The test page ran from a public HTTPS origin (the SciMigo CDN) and paired, ran checks, streamed output and interrupted.

Browser	http://127.0.0.1:9477	https://127.0.0.1:9478, trusted cert
Chrome 152	✓ after the Local Network Access prompt	–
Firefox 155	✓	–
Safari 26.6	✗ TypeError: Load failed	✓

What's in it

• agent-runtime tls setup | status | remove
  • Creates <runtime dir>/tls/localhost.pem and its key (key 0600, dir 0700).
  • The certificate is RSA 2048 with SAN 127.0.0.1, ::1 and localhost only, serverAuth only, CA:FALSE and no keyCertSign. It's valid for 397 days, and setup renews it within 30 days of expiry.
  • On macOS, setup adds it to the login keychain with SSL-only trust (security add-trusted-cert -r trustRoot -p ssl), which asks for the user's password.
  • Other platforms get no trust step, since their browsers already accept http loopback.
• agent-runtime serve
  • Also listens on https://127.0.0.1:9478 when the certificate exists (--https-port, --no-https, AGENT_RUNTIME_HTTPS_PORT).
  • Both listeners share one app object, so pairing, tokens and kernels are shared and enforced the same way. Only the HTTP listener runs the lifespan.
  • One signal handler stops both listeners (serving.py). Each uvicorn server installs its own handlers, and the last one would win.
  • It falls back to HTTP only, with a message, when 9478 is taken or the certificate has expired. --debug keeps the single auto-reload listener.
• Docs
  • Removes the targetAddressSpace: "local" hint. Chrome 151 rejects it for 127.0.0.1, which is in the loopback address space, and no annotation is needed.
  • integration.md gets the browser table and an HTTPS-then-HTTP detection example.
  • security.md gets a certificate section; the installer mentions tls setup.
• New dependency: cryptography>=42.

Tests

• tests/test_tls.py: certificate names and constraints, validity, key permissions, reuse and renewal, the macOS keychain commands (mocked), and the CLI.
• tests/test_serving.py: an end-to-end agent-runtime serve subprocess. It checks HTTP, verified HTTPS for 127.0.0.1 and localhost, that pairing is enforced on HTTPS (401 without a token), and that one SIGINT stops both listeners with exit 0.
• 132 passed locally on Linux; ruff, format and mypy (strict) are clean. CI adds macOS.

Not tested here

The real keychain trust (tls setup on a Mac) hasn't been run through this code. The manual version it automates (same certificate profile, same security add-trusted-cert flags) is what made Safari pass. Please run agent-runtime tls setup on a Mac before merging.

🤖 Generated with Claude Code