Repository navigation
feat(computers): the browser computer follows the universe clock, and loads live sites at any date (FD-5706) - #708
Merged
earakely-scale merged 10 commits intoNov 17, 2026
Conversation
… its live sites load at any date The ubuntu-24.04-browser base starts as root, runs the clock follower and the egress proxy under root's supervisord and the session's under its own, and preloads the clock library and the TLS shim, so the page driver serves clock/v1 sync_time and core configures it as it does the desktop. Its clock/ and egress/ are copies of ubuntu-24.04's, which a unit test keeps byte for byte. The egress proxy takes --listen (3130 here, the base's stand-in site proxy holding 3128), and the stand-in and core's site proxy hand it every connection to a public address when the base names it in AGENTENV_EGRESS_PROXY, so a live site loads at any universe date; private and loopback addresses still go straight. The stand-in keeps real time for its network log. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…wser shows real time The playwright-mcp website browser follows no clock, so the pages it opens see real time once a multi env is armed. The step says so, naming the browser computer (browser_envs = ["chromium"]), which follows the gateway as a desktop does, for pages on the universe's date. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the egress proxy's port among the browser computer's Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ollower under the computer's name Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…, marked via egress The site proxies logged the first address a live site resolved to, but the egress proxy resolves it again and decides which address to dial, after the browser's TLS hello. Such a connection's lines now name the egress proxy's address with "via": "egress"; the egress proxy's own log names the address it dialled. The shipped base's file list takes egress/main_test.go. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… CDP, not by a tab's title A tab's title is its URL until its page sets one, so the synthetic site's check, which matched any title, passed before the page had loaded. Each page now loads over CDP and passes only with no error and its word in what it shows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s proxy from one checked copy The clock's and egress proxy's users, folders, permissions and preload were copied by hand into each base's Dockerfile and init, outside what the copy check covered. They are now root/install.sh, run at the build, and root/init, run at boot, and root.conf is one file; the browser base's copies of clock/, egress/, root/ and root.conf must match the desktop's byte for byte. egress serve listens where AGENTENV_EGRESS_PROXY names, else 127.0.0.1:3128, so neither base passes it an address. The browser's Dockerfile says which egress files it leaves unused. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…xy alike The stand-in and core's site proxy each carry their own CONNECT to the egress proxy, since the stand-in has only the standard library in the image. One test now runs the same cases against both: which addresses are public, the CONNECT sent, and established, refused, closed and endless answers, each refused with the same EgressRefused and message. Core's open_live is split into egress_proxy, public and through_egress to match the stand-in's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nnect budget lasts A lookup that took the whole CONNECT_TIMEOUT_S still gave the egress proxy a tenth of a second. It now reports none within the budget, as the direct path does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…CP website browser It keyed on the browser's name and only reached the logs, and the step's log already lists playwright-mcp among the servers it skipped. A task whose pages need the universe's date uses a browser computer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/fd-5706-hb113-the-multi-envs-website-browser
branch
November 17, 2026 06:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A multi env's browser computer (the
chromiumwebsite browser on theubuntu-24.04-browserbase) now follows the universe clock, as the desktop has since HB1.6. A page'sDate.now()shows the universe's date when armed, after a jump, and after a reset. Live sites load at any universe date through the egress proxy, as they do on the desktop.FD-5706 (HB1.13, part of FD-5420).
How
The browser base (
src/agent_env/computers/artifacts/ubuntu-24.04-browser/) now matches the desktop's clock setup:start_as = "root"). Root's supervisord (root.conf, new) runs the clock follower asagentenv-clockand the egress proxy asagentenv-egress. The session's supervisord runs as the session user, and it runs Xvfb, the stand-in site proxy, the driver and Chromium.clock.conf. The root start's init creates the clock page and boots the egress proxy.-s 0 -dpms, as on the desktop.clock/v1sync_timeonce the base has the follower, and core already configures every computer that serves it, at deploy and after a reset.Copies, not a shared image.
clock/,egress/,root/androot.confare copied fromubuntu-24.04/. A base image builds only from its own folder.root/is new, in both bases.install.shruns at the build and sets up the clock's and the egress proxy's users, folders and permissions, the trust files and the preload.initruns at boot and covers the timezone, the clock page,egress bootand root's supervisord. Each base's Dockerfile copies the files into place and runsinstall.sh. Each base's start script handsinittoroot/init, sostart-desktop initstill works for the release's disk boot check.test_computer_browser_clock_base.pyfails if any copy differs from the desktop's by a byte.Live sites at any date. The egress proxy listens where
AGENTENV_EGRESS_PROXYnames, else on 127.0.0.1:3128 as on the desktop. The browser base sets it to 127.0.0.1:3130, since the stand-in site proxy already holds 3128. So the address is set in one place, androot.confis the same file in both bases.site-proxy.py) hands every connection whose addresses are all public to the egress proxy.directlive hosts (site_proxy.open_live).AGENTENV_EGRESS_PROXY, which the base sets. The desktop doesn't set it, so it's unchanged.test_computer_egress_hand_off.pyruns the same cases against both hand-offs: which addresses are public, theCONNECTsent, and established, refused, closed and endless answers. Both raise the sameEgressRefusedwith the same messages.AGENTENV_REAL_TIME=1, so its network log stays on real time.The Playwright MCP website browser stays on real time, as decided on FD-5706. A task whose pages need the universe's date uses a browser computer (
browser_envs = ["chromium"]).Behavior changes worth knowing
docker execalready defaults to root in a computer.splice, decisionreal). One more local hop, nothing else.Verification
On the x86 test host (Linux, local Docker):
tst/integration/computer/browser_clock_test.py, 2 passed:sync_env_clock:chromium, armed;Date.now()is within 3 s of the gateway's universe when armed, after a one-weekadvanceand after areset_env;intercept/outside. github.com's real certificate isn't valid two years back.Date.now()is real time, and https://example.com/ loads, with the egress proxy loggingsplice/realfor it.egress_test.py,chromium_universe_test.pyandcomputer_clock_test.py, so the desktop is unchanged.root/(468e78b, ee59b6c), on the x86 host unless noted:base_computer_test.py,egress_test.py,computer_clock_test.py,chromium_universe_test.py, 17 passed;browser_clock_test.py, the chaos file below,browser_computer_test.py, 32 passed and 4 skipped (Playwright and Puppeteer clients, which need Node 20 or later and npm);disk_boot_test.py), 1 passed;test_docker_image_github_clone.py::…[secrets], hung there and didn't finish; CI runs it on Linux.ERR_TUNNEL_CONNECTION_FAILED, in about 1 s, no hang), synthetic sites still load, and live sites come back once it starts.sync_env_clockarms it again, within 0.3 s.browser_connect_cdp, through the gateway): it reads a page'sDate.now()as two years back (within a second), and loads github.com.no answer.browser_computer_test.py,browser_multi_env_test.pyandwebsite_browser_test.py. That includes the stand-in's live github.com test, now through the egress proxy. One assertion was updated: the browser computer's listening ports now include 3130.go test -race) passes in both copies, including the newserve --listentest.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge; no actionable new issue remains.Summary
Browser computers now follow the universe clock and send public live-site connections through the egress proxy.
Diagram
%%{init: {'theme': 'neutral'}}%% flowchart LR Gateway[Gateway clock] --> Follower[Browser clock follower] Follower --> Page[Shared clock page] Page --> Chromium[Chromium clock reads] Chromium --> SiteProxy[Site proxy] SiteProxy -->|Public live host| Egress[Egress proxy on real time] Egress --> Live[Live site] SiteProxy -->|Private host| Private[Private site]Reviews (11) · Last reviewed commit: "revert(task_step): sync_env_clock doesn'..." · Reviewed by Greptile