<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>fomoxx</title><link>https://fomoxx.com/en/</link><description>Recent content on fomoxx</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 30 Sep 2026 10:55:00 +0800</lastBuildDate><atom:link href="https://fomoxx.com/en/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I Don’t Treat Investing as an Escape When My Capital Is Small</title><link>https://fomoxx.com/en/posts/dont-rush-investing-with-small-capital/</link><pubDate>Wed, 30 Sep 2026 10:49:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/dont-rush-investing-with-small-capital/</guid><description>&lt;p&gt;There is a sentence I disliked the first time I heard it:&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;If you have less than RMB 100,000 in cash, do not rush into trading and investing.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;It sounds like &amp;ldquo;people with less money should not invest.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;That is not how I interpret it now.&lt;/p&gt;&#10;&lt;p&gt;The more useful point is that when capital is small, the &lt;strong&gt;absolute investment return may be too small to change your life, while the volatility can still be large enough to change your mood and behavior&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>WeChat Official Account Cold Start: Recommendation Traffic, Search, and Monetization</title><link>https://fomoxx.com/en/posts/wechat-official-account-cold-start-guide/</link><pubDate>Wed, 30 Sep 2026 10:48:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/wechat-official-account-cold-start-guide/</guid><description>&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;Scope:&lt;/strong&gt; this article summarizes real conversations among WeChat Official Account operators in &lt;strong&gt;May 2026&lt;/strong&gt;. It is not an official Tencent ranking document and not a guaranteed monetization playbook. Account condition, content category, platform cycles, and luck all matter. Treat the notes below as field observations, not as a formula.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&#10;&lt;h2 id="the-short-version"&gt;The short version&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;The first useful goal in a cold start is not follower count. It is producing enough content for recommendation testing and learning what the system distributes.&lt;/li&gt;&#10;&lt;li&gt;Reads and ad revenue are not linearly related. Posts with similar view counts can earn very different amounts.&lt;/li&gt;&#10;&lt;li&gt;WeChat Search (搜一搜), recommendation traffic, and private sharing are separate distribution paths.&lt;/li&gt;&#10;&lt;li&gt;Artificial engagement, careless originality claims, and repeated deletion/reposting can create noise or risk instead of useful growth.&lt;/li&gt;&#10;&lt;li&gt;The first 7–15 days are better treated as a sequence of content experiments than as a verdict on whether the account will work.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="watch-recommendation-traffic-before-follower-count"&gt;Watch recommendation traffic before follower count&lt;/h2&gt;&#10;&lt;p&gt;New accounts often watch the wrong metric first.&lt;/p&gt;</description></item><item><title>Two AI Frontend Design Experiments: GPT vs Gemini vs Claude vs Kimi vs Grok vs GLM vs MiniMax</title><link>https://fomoxx.com/en/posts/ai-frontend-design-experiments/</link><pubDate>Wed, 30 Sep 2026 10:47:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/ai-frontend-design-experiments/</guid><description>&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;My conclusion after two rounds:&lt;/strong&gt; AI-generated frontends have not converged to one universal aesthetic. Under low-constraint design prompts, different model/harness combinations repeatedly exposed different visual preferences. OpenAI tended to be strong at physical spaces and mature commercial branding; Gemini leaned toward concepts and interactive experiments; Claude Sonnet behaved more like a product/brand designer; Kimi was strong at Chinese typography and editorial direction; Grok leaned cinematic and theatrical. Instead of asking which model has the &amp;ldquo;best taste,&amp;rdquo; I now use those recurring biases as a multi-model design pitch pool.&lt;/p&gt;</description></item><item><title>ChatGPT Plus vs Team/Business: A Real-World Usage Capacity Test</title><link>https://fomoxx.com/en/posts/openai-account-durability-analysis/</link><pubDate>Wed, 30 Sep 2026 10:46:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/openai-account-durability-analysis/</guid><description>&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;Current-status note — September 30, 2026:&lt;/strong&gt; this article is a historical usage test from May 11–12, 2026, not a current official quota table. ChatGPT Business has since introduced Standard and Premium seats. OpenAI&amp;rsquo;s current documentation says Premium includes 5× the usage of Standard and is not subject to the five-hour usage window. The Plus-A / Team-B / Team-C ranking below describes only the three accounts I measured at the time. For current limits, check &lt;a href="https://help.openai.com/en/articles/12003714-chatgpt-business-data" target="_blank" rel="noopener noreferrer"&gt;OpenAI&amp;rsquo;s Business models and limits documentation&lt;/a&gt;&#10;.&lt;/p&gt;</description></item><item><title>Bitget Wallet Card Guide: Fiat24 Setup, Top-Up, Alipay, WeChat Pay, and Google Pay</title><link>https://fomoxx.com/en/posts/bitget-wallet-card-guide/</link><pubDate>Wed, 30 Sep 2026 10:45:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/bitget-wallet-card-guide/</guid><description>&lt;h2 id="what-the-card-is"&gt;What the card is&lt;/h2&gt;&#10;&lt;p&gt;Bitget Wallet and Fiat24 launched a crypto-linked payment card that I originally tested as a virtual &amp;ldquo;U card.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;The things that stood out to me were:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Relatively clear fee structure.&lt;/strong&gt; The current Mainland China fee page lists no issuance fee, no annual fee, and no spending fee, while top-ups and some payment scenarios can still carry fees.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Exchange rates and fees need to be checked in the live app.&lt;/strong&gt; My original test had relatively low FX loss, but that can vary by region, funding currency, and payment method.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Multiple payment platforms.&lt;/strong&gt; The card can be connected to services such as Alipay, WeChat Pay, Google Pay, and Apple Pay where supported.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;GetGas.&lt;/strong&gt; Bitget Wallet can automatically handle gas replenishment after funding, which is convenient.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;It worked in my own payment tests.&lt;/strong&gt; I used it for services including ChatGPT and API-related payments.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;⚠️ &lt;strong&gt;Important:&lt;/strong&gt; Fiat24 is not a bank deposit account with deposit insurance. I treat this as a spending tool: fund it when needed instead of leaving a large balance there.&lt;/p&gt;</description></item><item><title>Tencent Cloud Lighthouse Has No Automatic Snapshots: My Two-Slot Rotation with systemd</title><link>https://fomoxx.com/en/posts/tencent-lighthouse-auto-snapshot/</link><pubDate>Wed, 30 Sep 2026 10:44:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/tencent-lighthouse-auto-snapshot/</guid><description>&lt;p&gt;Tencent Cloud Lighthouse does not provide an automatic snapshot feature for the server workflow I was using, and my instance only has two snapshot slots.&lt;/p&gt;&#10;&lt;p&gt;If I rely on manual snapshots, I either consume the available recovery points quickly or simply forget to create them.&lt;/p&gt;&#10;&lt;p&gt;I ended up running a script &lt;strong&gt;on the Lighthouse server itself&lt;/strong&gt;. The script calls the Tencent Cloud API, deletes the oldest automatic snapshot, creates a new one, and is triggered by a &lt;code&gt;systemd timer&lt;/code&gt; every Sunday at 04:30.&lt;/p&gt;</description></item><item><title>Why I Self-Host Waline on a VPS with SQLite</title><link>https://fomoxx.com/en/posts/waline-vps-sqlite/</link><pubDate>Wed, 30 Sep 2026 10:43:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/waline-vps-sqlite/</guid><description>&lt;p&gt;I recently wanted to add a comment system to my blog.&lt;/p&gt;&#10;&lt;p&gt;Looking at the usual options, I realized how quickly comments can turn into a small infrastructure project: GitHub Issues, Discussions, Vercel, serverless functions, cloud databases, object storage, CAPTCHAs, email notifications, and anti-spam services.&lt;/p&gt;&#10;&lt;p&gt;None of those pieces is especially difficult on its own. Put enough of them together, though, and a comment box starts to look like another system to operate.&lt;/p&gt;</description></item><item><title>Slock Is Now Raft: Installation, Agent Setup, and Common Problems</title><link>https://fomoxx.com/en/posts/slock-guide/</link><pubDate>Wed, 30 Sep 2026 10:42:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/slock-guide/</guid><description>&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;2026 update:&lt;/strong&gt; Slock has been renamed to Raft. This article keeps the real-world experience from the Slock phase and adds the current rename, compatibility, and migration context. Raft is still evolving quickly, so installation commands and UI details should always be checked against the current product page.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&#10;&lt;p&gt;Slock, now renamed to &lt;strong&gt;Raft&lt;/strong&gt;, is a chat-based way to dispatch local agents. You connect command-line tools such as Claude Code, Codex CLI, Gemini CLI, OpenCode, and &lt;a href="https://fomoxx.com/en/posts/opencli-guide/"&gt;OpenCLI&lt;/a&gt;&#10;, then @ them in channels to assign work, review plans, and collect results.&lt;/p&gt;</description></item><item><title>Enterprise AI Agents Don’t Always Need Multi-Agent Architectures</title><link>https://fomoxx.com/en/posts/enterprise-sop-agent-architecture/</link><pubDate>Wed, 30 Sep 2026 10:41:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/enterprise-sop-agent-architecture/</guid><description>&lt;p&gt;A while ago I reviewed a real AI customer-reception system and ran into a point that is easy to miss:&lt;/p&gt;&#10;&lt;p&gt;In many enterprise workflows, the most useful agent architecture is not several agents collaborating with each other. It is &lt;strong&gt;one agent constrained by a stable process&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;The surrounding system should first tell the agent:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;which business stage it is currently in;&lt;/li&gt;&#10;&lt;li&gt;what this stage is supposed to accomplish;&lt;/li&gt;&#10;&lt;li&gt;which tools are available;&lt;/li&gt;&#10;&lt;li&gt;what conditions allow a transition;&lt;/li&gt;&#10;&lt;li&gt;when the workflow must stop and hand over to a human.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;I usually call this an &lt;strong&gt;SOP agent&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Multi-Agent Collaboration Patterns: Chat, Issue-Driven, SOP, and Hybrid Workflows</title><link>https://fomoxx.com/en/posts/ai-agent-collaboration-patterns/</link><pubDate>Wed, 30 Sep 2026 10:40:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/ai-agent-collaboration-patterns/</guid><description>&lt;p&gt;Once you start running several AI agents at the same time, one question shows up quickly: &lt;strong&gt;how should they actually collaborate?&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Spinning up more agents is easy. The hard part is deciding who receives the request, who breaks it down, who executes, who reviews, where state lives, how permissions are controlled, and how the system recovers when something goes wrong.&lt;/p&gt;&#10;&lt;p&gt;Across my work with &lt;a href="https://fomoxx.com/en/posts/slock-guide/"&gt;Slock/Raft&lt;/a&gt;&#10;, &lt;a href="https://fomoxx.com/en/posts/multica-guide/"&gt;Multica&lt;/a&gt;&#10;, and an enterprise SOP-agent system, the biggest difference has not been the model. It has been the &lt;strong&gt;organizational pattern&lt;/strong&gt; around the model.&lt;/p&gt;</description></item><item><title>Multica Guide: Issues, Agent Workflows, and Multi-Agent Collaboration</title><link>https://fomoxx.com/en/posts/multica-guide/</link><pubDate>Sun, 27 Sep 2026 14:26:08 +0800</pubDate><guid>https://fomoxx.com/en/posts/multica-guide/</guid><description>&lt;p&gt;Multica is a multi-agent collaboration platform. You connect CLI agents such as Claude Code, Codex, &lt;a href="https://fomoxx.com/en/posts/opencli-guide/"&gt;OpenCLI&lt;/a&gt;&#10;, and Hermes into it, then organize tasks using workspaces, issues, automations, and CLI tools.&lt;/p&gt;&#10;&lt;p&gt;If &lt;a href="https://fomoxx.com/en/posts/slock-guide/"&gt;Slock / Raft&lt;/a&gt;&#10; feels like a chatroom, Multica is closer to an office. A chatroom works well for calling someone in, quick brainstorming, and immediate course corrections. An office needs tasks, assignees, statuses, handoffs, and verification.&lt;/p&gt;&#10;&lt;p&gt;When you run multiple agents, multiple projects, and multiple terminals at once, Multica provides a shared space where work can retain its state, handoffs, and acceptance criteria.&lt;/p&gt;</description></item><item><title>OpenCLI for AI Agents: Turning Browser Workflows into Reusable CLI Commands</title><link>https://fomoxx.com/en/posts/opencli-guide/</link><pubDate>Thu, 24 Sep 2026 15:30:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/opencli-guide/</guid><description>&lt;p&gt;OpenCLI is easy to describe as “letting an AI click around websites.” That is not wrong, but it is too narrow.&lt;/p&gt;&#10;&lt;p&gt;A better mental model is that OpenCLI can do two things at once: let an agent operate a logged-in browser through Browser Bridge, and turn browser workflows that already work into reusable adapters or CLI commands. A flow can open a page, reuse an authenticated session, click, paginate, download, submit, and return a result. Codex, Claude Code, Slock / Raft, Multica, or another agent can then call the capability again instead of rebuilding the same interaction from scratch.&lt;/p&gt;</description></item><item><title>Does Multica Reduce Work or Add More? Lessons from a Real Squad Workflow</title><link>https://fomoxx.com/en/posts/multica-squad-workflow-review/</link><pubDate>Tue, 22 Sep 2026 10:30:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/multica-squad-workflow-review/</guid><description>&lt;p&gt;I previously wrote a &lt;a href="https://fomoxx.com/en/posts/multica-guide/"&gt;Multica guide&lt;/a&gt;&#10; that focused on the basics: how Issues work, how agents are organized, and how multi-agent collaboration is structured.&lt;/p&gt;&#10;&lt;p&gt;Getting those individual features working is one thing. Putting an actual multi-stage workflow into Multica and letting several agents hand work to each other is another.&lt;/p&gt;&#10;&lt;p&gt;I took a real multi-stage task I was already working on and ran it through a full Squad workflow. It was not a demo invented to test Multica. It was a real workflow that needed several roles to participate in sequence, including upfront analysis, task decomposition, work by different agents, verification of key results, and an independent review step.&lt;/p&gt;</description></item><item><title>I Used 1.05 Billion Tokens in Cursor: What a 93.31% Cache Hit Rate Taught Me</title><link>https://fomoxx.com/en/posts/cursor-1-billion-token-review/</link><pubDate>Tue, 15 Sep 2026 15:10:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/cursor-1-billion-token-review/</guid><description>&lt;p&gt;When Cursor&amp;rsquo;s per-request pricing period was approaching its end, I exported my Usage Events from &lt;strong&gt;March 1 to May 19, 2026&lt;/strong&gt; and added them up.&lt;/p&gt;&#10;&lt;p&gt;The result was larger than I expected: across this Cursor workflow alone, 80 days accounted for &lt;strong&gt;1,051,066,111 tokens&lt;/strong&gt; of total throughput.&lt;/p&gt;&#10;&lt;p&gt;That was not my total AI usage. I was using other tools during the same period; they are not included here. This dataset only covers what I could see in Cursor&amp;rsquo;s Usage Events: requests, uncached input, cache writes, cache reads, and output.&lt;/p&gt;</description></item><item><title>Fix Codex App instructions_required 400 Behind CLIProxyAPI</title><link>https://fomoxx.com/en/posts/codex-desktop-cpa-instructions-required-400/</link><pubDate>Tue, 15 Sep 2026 15:05:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/codex-desktop-cpa-instructions-required-400/</guid><description>&lt;p&gt;When I routed the Codex App through CLIProxyAPI (CPA) to a third-party upstream, requests failed immediately with a 400 error:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;instructions_required · 400&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;The instructions parameter is required and must be a non-empty string.&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The failure was not fixed by upgrading CPA, turning on the built-in Codex instructions option, or trying to remove the field with &lt;code&gt;payload.filter&lt;/code&gt;. The working fix was much smaller: keep the built-in injection disabled and use &lt;code&gt;payload.default&lt;/code&gt; to supply a minimal non-empty compatibility value only when the field is missing.&lt;/p&gt;</description></item><item><title>How to Connect a Local stdio MCP Server to ChatGPT Web with OpenAI Secure MCP Tunnel</title><link>https://fomoxx.com/en/posts/connect-local-mcp-to-chatgpt-web-secure-tunnel/</link><pubDate>Tue, 15 Sep 2026 15:00:00 +0800</pubDate><guid>https://fomoxx.com/en/posts/connect-local-mcp-to-chatgpt-web-secure-tunnel/</guid><description>&lt;p&gt;A local MCP server that communicates over &lt;strong&gt;stdio&lt;/strong&gt; is easy for a desktop client to launch. ChatGPT Web is different: it runs in the cloud and cannot simply cross into your Mac and execute a local process.&lt;/p&gt;&#10;&lt;p&gt;I ran into exactly that boundary while trying to use Google&amp;rsquo;s official &lt;code&gt;google-analytics-mcp&lt;/code&gt; from ChatGPT Web. The path that finally worked was &lt;strong&gt;OpenAI Secure MCP Tunnel&lt;/strong&gt;:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Local MCP server (stdio)&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ↓&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;OpenAI Secure MCP Tunnel (tunnel-client)&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ↓&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ChatGPT Web / Developer Mode / custom MCP app&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This article documents the complete setup I used on macOS, including the parts that actually took time: Google OAuth, isolating failures by layer, local proxy settings, &lt;code&gt;launchd&lt;/code&gt;, and verifying that ChatGPT could execute a real Analytics report.&lt;/p&gt;</description></item><item><title>Privacy Policy</title><link>https://fomoxx.com/en/privacy/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0800</pubDate><guid>https://fomoxx.com/en/privacy/</guid><description>&lt;h1 id="privacy-policy"&gt;Privacy Policy&lt;/h1&gt;&#10;&lt;p&gt;Last updated: September 2026&lt;/p&gt;&#10;&lt;p&gt;Fomoxx is a personal blog.&lt;/p&gt;&#10;&lt;p&gt;This site uses Cloudflare for network and security services, Google Analytics for aggregate traffic measurement, and Waline for comments. These services may process information such as IP addresses, device information, and pages visited as needed to provide their services. If you leave a comment, Waline also processes the nickname, email address, and comment content you choose to submit.&lt;/p&gt;&#10;&lt;p&gt;The site also loads fonts or front-end libraries from Google Fonts and jsDelivr. When your browser requests those resources, the relevant provider may receive ordinary network-request metadata such as your IP address, user agent, and referrer.&lt;/p&gt;</description></item><item><title>About</title><link>https://fomoxx.com/en/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://fomoxx.com/en/about/</guid><description/></item></channel></rss>