<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Claude Code on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/claude-code/</link><description>Recent content in Claude Code on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 13 Sep 2026 17:45:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/claude-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Obsidian + Claude Code: My Founder OS Dual-Driving Workflow</title><link>https://blog.lynxflow.co/en/posts/obsidian-claude-code-founder-os-workflow/</link><pubDate>Sun, 13 Sep 2026 17:45:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/obsidian-claude-code-founder-os-workflow/</guid><description>&lt;img src="https://blog.lynxflow.co/images/obsidian-claude-code-cover.png" alt="Featured image of post Obsidian + Claude Code: My Founder OS Dual-Driving Workflow" /&gt;The previous post, I Built Myself a Founder OS With Claude Code, covered how to build a knowledge base. This one covers how to use it.
Specifically: how to let human and AI collaborate inside the same knowledge base. I read the dashboard and tweak notes in Obsidian; Claude Code runs batch triage, fills templates, and migrates files in the terminal. Both sides edit the same Markdown files, and Git records everything.</description></item><item><title>I Built Myself a Founder OS With Claude Code: Reclaiming 155 Scattered Files</title><link>https://blog.lynxflow.co/en/posts/lynxos-founder-os-with-claude-code/</link><pubDate>Sun, 13 Sep 2026 17:30:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/lynxos-founder-os-with-claude-code/</guid><description>&lt;img src="https://blog.lynxflow.co/images/lynxos-founder-os-cover.png" alt="Featured image of post I Built Myself a Founder OS With Claude Code: Reclaiming 155 Scattered Files" /&gt;How It Started: What 155 Files Taught Me Start with a number: my WSL home directory contained 155 Markdown files.
Not 155 notes — 155 &amp;ldquo;important but I don&amp;rsquo;t know where to put them&amp;rdquo; files. Among them: 41 industry research reports (ERP selection, VPS migration, LLM rankings), 30 ops postmortems (written at 3 AM when services died), 20 personal documents (my cousin&amp;rsquo;s college application plans, my own resume), and hand-written handoff sheets for a dozen projects.</description></item><item><title>The Complete Technical Routes for Hermes to Control Claude Code: From Terminal Invocation to Agent Interoperability Protocols</title><link>https://blog.lynxflow.co/en/posts/hermes-claude-code-control-routes-2026/</link><pubDate>Sun, 13 Sep 2026 16:15:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/hermes-claude-code-control-routes-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/hermes-cc-control-routes-cover.png" alt="Featured image of post The Complete Technical Routes for Hermes to Control Claude Code: From Terminal Invocation to Agent Interoperability Protocols" /&gt;One-Sentence Summary Hermes (a Telegram bot gateway) controlling Claude Code (Anthropic&amp;rsquo;s CLI coding agent) has 7 technical routes: direct terminal invocation, SDK programmatic API, MCP bidirectional communication, A2A Agent-to-Agent protocol, ACP Agent Communication protocol, Hooks system, and Cloud sessions. Hermes already has codex_app_server and copilot_acp subprocess runtime templates — adding a Claude Code runtime is essentially copying an existing pattern. For Telegram bot scenarios</description></item><item><title>Is My Claude Code Memory System the Most Mature? — DIY Cross-Harness Setup vs. the Open-Source Ecosystem</title><link>https://blog.lynxflow.co/en/posts/claude-code-memory-systems-survey-2026/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/claude-code-memory-systems-survey-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/claude-code-memory-systems-survey-2026.png" alt="Featured image of post Is My Claude Code Memory System the Most Mature? — DIY Cross-Harness Setup vs. the Open-Source Ecosystem" /&gt;The verdict up front No — it is not &amp;ldquo;the most mature on the internet,&amp;rdquo; because there is no absolute most-mature; it depends on which problem you are solving. But placed against the 2026 open-source ecosystem, my system sits firmly in the top tier of self-built setups, with one strength almost no open-source project has: a single-source-of-truth architecture spanning 6 harnesses.
I also have to be honest: the industry is productizing this exact capability. The highest-starred project,</description></item><item><title>What the Server Knows, the Browser Shouldn't Get: Mapping the Frontend Secret-Leakage Surface</title><link>https://blog.lynxflow.co/en/posts/frontend-secret-leakage-ai-era/</link><pubDate>Wed, 02 Sep 2026 01:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/frontend-secret-leakage-ai-era/</guid><description>&lt;img src="https://blog.lynxflow.co/images/frontend-secret-leakage-ai-era.png" alt="Featured image of post What the Server Knows, the Browser Shouldn't Get: Mapping the Frontend Secret-Leakage Surface" /&gt;Let’s start with a scenario. You’re building a SaaS product: the backend is connected to a cloud database, the frontend is Next.js, and iteration is moving fast. Before launch, you ask the security team to run a black-box test. On the third day, the report comes back with two high-severity findings:
C1: On the homepage, “View Source” reveals that the JSON inside __NEXT_DATA__ contains the full backend configuration that should have existed only on the server side—database address, message queue</description></item><item><title>Full Health Check of CPA Model Pool: Which of 80 Models Are Alive, Smart, or Running Naked</title><link>https://blog.lynxflow.co/en/posts/cpa-model-pool-audit-smart-model-ranking/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/cpa-model-pool-audit-smart-model-ranking/</guid><description>&lt;img src="https://blog.lynxflow.co/images/cpa-model-pool-audit-smart-model-ranking.png" alt="Featured image of post Full Health Check of CPA Model Pool: Which of 80 Models Are Alive, Smart, or Running Naked" /&gt;Last month I wrote an article testing six Claude Code models. This time I&amp;rsquo;m broadening the scope: my local CPA (local model gateway) has 80 models connected, and I did two things — first, sent real requests to each one to check liveness, then gave the survivors a puzzle-resistant intelligence test, and finally cross-validated against public leaderboards.
Bottom line up front: listing a model ≠ it works. Of the 80 models, 59 are text models, and only about 30 could actually hold a conversat</description></item><item><title>Solo Multi-Channel Content: How I Built My AI Automation Pipeline LynxPipe</title><link>https://blog.lynxflow.co/en/posts/lynxpipe-ai-content-pipeline-architecture/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/lynxpipe-ai-content-pipeline-architecture/</guid><description>&lt;img src="https://blog.lynxflow.co/images/lynxpipe-ai-content-pipeline-architecture.png" alt="Featured image of post Solo Multi-Channel Content: How I Built My AI Automation Pipeline LynxPipe" /&gt;Running a blog, a Telegram channel, and a WeChat public account all by myself—the real bottleneck isn&amp;rsquo;t running out of ideas, it&amp;rsquo;s keeping up. Every day there&amp;rsquo;s an overwhelming flood of valuable AI news, and manually translating, rewriting, sourcing images, laying out, and distributing it all can eat up half a day before you even start. So I architected it as a pipeline I call LynxPipe: raw inputs go in, polished articles come out, and distribution to the blog, TG, and WeChat h</description></item><item><title>A Comparative Review of Eight IDEs in the AI Era: Memory Usage, Runtime Efficiency, and Bug Signals (Multi-Source Verification, August 2026)</title><link>https://blog.lynxflow.co/en/posts/2026-08-19-ide-comparison-memory-efficiency-bugs/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/2026-08-19-ide-comparison-memory-efficiency-bugs/</guid><description>&lt;img src="https://blog.lynxflow.co/images/2026-08-19-ide-memory-footprint.png" alt="Featured image of post A Comparative Review of Eight IDEs in the AI Era: Memory Usage, Runtime Efficiency, and Bug Signals (Multi-Source Verification, August 2026)" /&gt;Stop taking that optimistic little “lightweight 400MB” number on IDE landing pages at face value—the 2026 generation of AI IDEs has entered the era of “memory inflation.” In a Copilot Chat session stretched across 18 hours, the VS Code extension host can balloon from 500MB to 80GB+, while Zed has even recorded an extreme 185GB case on macOS.
This article offers an in-depth comparison of eight mainstream AI IDEs. Using multi-source online verification plus adversarial review, we cross-check the a</description></item><item><title>ccswitch Edited the Model, Claude Code Didn't Budge: A Three-Layer Override Root-Cause Diagnosis</title><link>https://blog.lynxflow.co/en/posts/ccswitch-model-not-applying-claude-code/</link><pubDate>Tue, 18 Aug 2026 21:36:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/ccswitch-model-not-applying-claude-code/</guid><description>&lt;img src="https://blog.lynxflow.co/images/ccswitch-model-not-applying-claude-code.png?v=090603" alt="Featured image of post ccswitch Edited the Model, Claude Code Didn't Budge: A Three-Layer Override Root-Cause Diagnosis" /&gt;Origin: Three Edits, Zero Effect I opened ccswitch (v3.19.2, the Windows-side Claude Code config switcher), clicked &amp;ldquo;edit provider,&amp;rdquo; changed the Opus-tier model, and saved. Restarted Claude Code — still running the old model. Edited, saved, restarted again — still no change.
&amp;ldquo;Doesn&amp;rsquo;t change&amp;rdquo; problems are the worst kind to guess at. Below is the process of forcing out the root cause with logs and a field-by-field database comparison. The conclusion is more tangled th</description></item><item><title>From Manual Post Review to Semi-Automated Improvement: My Telegram Channel Quality Loop, and the Next Step Toward Full Automation</title><link>https://blog.lynxflow.co/en/posts/tg-channel-auto-audit-loop/</link><pubDate>Sat, 15 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/tg-channel-auto-audit-loop/</guid><description>&lt;img src="https://blog.lynxflow.co/images/tg-channel-auto-audit-loop.png" alt="Featured image of post From Manual Post Review to Semi-Automated Improvement: My Telegram Channel Quality Loop, and the Next Step Toward Full Automation" /&gt;From Manual Review to AI-Driven Loop: How I Automated My Telegram Channel Moderation I run a Telegram channel @Lx_groups focused on free AI resources—free API quotas, limited-time offers, open-source projects, and industry news. The pitch is simple: &amp;ldquo;genuinely free,&amp;rdquo; no gray-market stuff, no ads. Behind the scenes, a Cloudflare Worker pulls from upstream TG channel preview pages, GitHub Atom feeds, and major tech company RSS feeds, deduplicates via KV storage, and pushes curated cont</description></item><item><title>Hands-on Test of Six Claude Code Models: Who’s Fast, Who’s Smart, and Who’s a Lottery</title><link>https://blog.lynxflow.co/en/posts/claude-code-model-benchmark/</link><pubDate>Sat, 15 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/claude-code-model-benchmark/</guid><description>&lt;img src="https://blog.lynxflow.co/images/cc-bench-hero.png?v=090603" alt="Featured image of post Hands-on Test of Six Claude Code Models: Who’s Fast, Who’s Smart, and Who’s a Lottery" /&gt;Claude Code’s model picker currently has six options sitting in it: qwen3.8-max, glm-5.2-fast-preview, glm-5.2, deepseek-v4-pro-0813, qwen3-coder-next, and grok-4.6. All of them are routed through my local CPA, a local model gateway, to their respective upstream providers. In day-to-day use, my impressions were vague: “this one feels faster,” “that one feels smarter.” Gut feel is unreliable, so I spent an evening putting them on the same starting line and benchmarked speed, thinking time, long-i</description></item></channel></rss>