The direct links below always point to the latest local build:

Windows

macOS

Linux (Ubuntu/Debian)

Let me start with something that actually happened.

In early 2025, I added a feature to an internal system: export to Excel. Small requirement — I didn’t even write it up, just typed “add an export button to the list page” into the chat box.

The AI delivered in ten minutes. Frontend changes, new endpoint, SQL — all in one pass. I was pleased when I opened the PR, right up until review revealed: the export columns didn’t match the list page, a hundred thousand rows would hang the service outright, there was no permission check, and the tests only covered the happy path.

Attachment download: Agent Interview Questions.pdf — handy for printing or offline reading

Why Would You Need Multiple Agents

An opening question to separate people who have “read the articles” from people who have “actually built one”.

The bad answer: “Multi-agent enables parallel processing, which improves system throughput and robustness.”

Every word of that is correct, but if you follow up with “so after splitting into two agents, did throughput actually double?”, they stall. The reality: inter-agent communication has overhead, coordination has complexity, and after the split total throughput may well drop. Adding agents is not like adding CPU cores.

The most annoying thing about coding with AI isn’t that it writes bugs — it’s that it writes them differently every time. Same requirement, three conversations, three implementations. The standards live in your head; the AI doesn’t know them.

Trellis tries to solve this. It’s not yet another AI coding assistant — it’s a framework for injecting project standards into AI: the AI reads your standards before writing code, gets checked automatically after writing, and once the check is done, anything newly learned gets distilled back into the standards. The more you use it, the better the AI knows your project.

It runs a complete expert workflow — requirement research, material retrieval, outline planning, layout planning, visual design — where every step allows manual fine-tuning, or the whole thing can run automatically end to end. In terms of output, pages generated with Gemini 3 Flash already reach commercial delivery quality.

You SSH into a server to run a long task, the network drops, and the task is gone. Tmux exists to solve exactly this — it decouples the terminal session from the window, so the process keeps running after you close the terminal.

The Core Problem It Solves

An ordinary terminal window is bound to its processes. Close the window and the processes die. Same story when SSH drops.

We often see URLs like these:

plaintext

]]> https://blog.baifan.site/en/oracle-free-vps-guide/ Tue, 07 Apr 2026 14:00:00 +0800 ByF https://blog.baifan.site/en/oracle-free-vps-guide/

Oracle’s Always Free plan gives you a 4-core, 24 GB ARM server every month — no expiry, no charge. The same specs cost $80–100/month on AWS. This post strings together signup, pitfalls, instance creation, and keep-alive.

What You Get

Oracle’s free tier is called Always Free. Not a trial, not a limited-time promo.

]]> https://blog.baifan.site/en/codex-websocket-reconnect-fix/ Tue, 31 Mar 2026 14:00:00 +0800 ByF https://blog.baifan.site/en/codex-websocket-reconnect-fix/

Codex talks to the ChatGPT backend over WebSocket by default. If your network path involves Clash, a corporate proxy, cross-border transit, or Cloudflare challenge pages, that long-lived WebSocket gets killed easily — and you end up staring at Reconnecting... 1/5 over and over. Turn off WebSocket and switch to plain HTTP streaming requests, and the problem mostly disappears.

Why WebSocket Breaks Behind Proxies

The WebSocket protocol starts with an HTTP Upgrade request; only after the server returns 101 does it switch to the long-lived connection. That long-lived connection is exactly where the problem sits — proxy servers, firewalls, and CDN nodes all run timeout policies on idle connections, and Cloudflare’s challenge mechanism can inject an interstitial page mid-path. Any link in that chain kills the connection, and the Codex client starts Reconnecting.

This post is a curated list. The source is a roundup post by Telegram’s @LCGFX; I’ve reorganized it by platform and added open-source status and risk judgments.