Fix visual reply previews
Messages and context
Before publishing a page, agents check it with screenshots from a small headless browser that T3 Code keeps for itself. The first preview on a machine downloads this browser once (about 120 MB), so that preview can take a minute.
T3 Code docs: html renders
What it’s for
Understanding slow first previews and failed external resources. Previews can load public resources but block names that resolve to private or reserved addresses, which fake-IP DNS proxies can return.
T3 Code docs: html renders
When to use it
Use this when a preview is slow on a new machine, fails to start on Linux, or loses CDN scripts or other external resources.
T3 Code docs: html renders
How to use it
On the machine running the environment, inline the blocked resource, add its host to fake-ip-filter, or switch that machine's proxy DNS to redir-host.
T3 Code docs: html renders
Use the preview's console messages to find which hostnames were blocked for resolving to private addresses, as Clash or Mihomo fake-IP DNS can cause.
T3 Code docs: html renders
Allow about a minute for the first preview on a machine while T3 Code downloads its own headless browser (about 120 MB) once.
T3 Code docs: html renders
Complete the host setup on Linux hosts where the preview browser will not start; pages still publish without it.
T3 Code docs: html renders
Unofficial notes. Not affiliated with Theo or t3.gg.