{"lang":"en","count":12,"issues":[{"title":"270. Qiao Cun","link":"https://weekly.tw93.fun/en/posts/270/","pubDate":"Mon, 15 Jun 2026 00:00:00 GMT","description":"\n

The cover photo was taken over the weekend when I went to Qiao Cun for a meal, just a casual snap. Their food is great, the avocado and salmon are really tasty. Whenever a friend visits Hangzhou, I usually take them here or to Zhang’s Mansion.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

New Recommendation

\n

If a friend of yours needs to update their resume soon, you have to recommend Kami to them
\nhttps://github.com/tw93/Kami
\nIf a friend of yours needs to update their resume soon, you have to recommend Kami to them. I tuned a dedicated version carefully, so Kami alone makes writing a resume genuinely handy, good-looking, and clear. Have them get their raw source material ready in Markdown, then tell the AI /kami help me produce a resume, tweak it once or twice, and it’s pretty much done. It’s not just layout, it also helps optimize and organize your resume content, looking at the talent profile from the perspective of a technical final-round interviewer.
\n

\n

Product Releases

\n

Mole’s desktop client 1.7.2 is here
\nhttps://mole.fit/
\nThis release updates a ton of things, including support for users with accessibility needs. Status and the menu bar are faster and more stable, Software, uninstall, and updates are more complete, Clean is more thorough while still keeping review-first, the privacy check is more accurate, quieter, and smarter, Analyze, Doctor, and Clean Screen are more stable too, and there are quite a few optimizations for fan control on Apple silicon.

\n

It’s been exactly one month since Mole’s Mac version launched, written in my spare time, and the numbers are kind of fun. In total I wrote 110,000 lines of Swift, including 36,000 lines of test code and 1,983 unit tests, shipped 8 releases, added 145 new features, and supported 9 languages. It’s the last day of the early-bird price and MOLEWEEKLY still works, so anyone interested is welcome to give it a try. More surprises to come.

\n

\n

Kaku has finally updated to version 0.12 as well
\nKaku even has its own little official site now https://kaku.fun/, go take a look. This update brings quite a few things: it now restores session history after you reopen a window, supports AI features you can use directly once logged in with the Codex backend, opens PDFs, images, audio and video, archives, and Office documents with the system default app, and when all panels are sitting at the shell prompt, Cmd+Q quits directly, plus other fun features. Go check out the Release.
\n

\n

Some fun recent updates to Pake
\nhttp://github.com/tw93/Pake
\nPake packages a web page into a lightweight desktop app with one command, supporting macOS, Windows, and Linux. Recently it added cmd+f content search, right-click download support, dots in desktop app names, clearer error messages when AppImage builds fail on Linux, a pnpm 11 compatibility fix, and more.
\n

\n

Just Chatting

\n

I’m not an influencer, not a content creator, not a KOL, so what am I
\n
\nMy Twitter earnings are only a bit over 100 dollars each time, probably far less than most blue checkmarks, even lower than that friend who got burned twice by Tauri, which is kind of funny. Why so little? Haha, I should reflect on it, and along the way share my failure experience with everyone.

\n

First off, I’m not an influencer, not a content creator, not a KOL, nothing really, just an ordinary engineer who writes a bit of hobby code. Twitter, to me, is a way to sync the changelogs of my open-source products to everyone, and to share daily life posts about where I went, what I ate, what I watched. There’s no traffic pressure at all, and no pressure to turn traffic into money, so if the earnings are small, so be it. That actually happens to make this an account I like more and more.

\n

Content creators usually make money by taking ads, and AI companies tend to pay quite well, sharing lots of altruistic products to get more people to follow, earning their due while being helpful, which is honestly pretty nice too. But there’s usually traffic pressure: you have to keep chasing hot topics and obsessing over headlines, and the longer you do it the better you get. I just feel that’s too exhausting, and I can’t pull it off.

\n

I actually took some ads before, but I haven’t for a long time now. I remember an agency once contacted me and said advertisers don’t like an account like mine, they prefer the kind that constantly posts AI hot takes. When I heard that, I was actually happy, haha. My account hasn’t turned into the high-quality traffic account they see it as, so I guess I’m keeping things pretty well.

\n

I kept wondering, if I had to describe my account in one word, what would it be? I thought about it for a long time, and finally figured it out today, which is why this casual article exists: my account should be a continuously iterated “Tw93 Engineer Magazine”.

\n

This magazine has roughly these few columns: Product Notes, recording the updates and interesting ideas behind products like Pake, Mole, and Kaku; a Tech Column, where I write about technical thoughts, thoughts on AI, and learning topics in new tech areas; Good Stuff, all tools I actually use myself, none of the paid-promotion kind; and a Just Looking Around module where you can see my daily life, what I eat, play, and watch.

\n

Every engineer can flip through it casually, find something they’re interested in, and dive in to play with it. Friends who want to learn can also read through my long articles one by one, then head to my blog and the trending weekly to find more interesting past content.

\n

This magazine has almost no ads, and won’t say things against my conscience just to promote my own products. Updates are pretty casual too, usually at most two posts a day, just one when I’m too busy, posting whatever comes to mind. At the same time this magazine is a continuously iterating product: through it you can see how I change year by year, like a tech friend who keeps you company, and you can also reach the magazine’s editor via DM.

\n

The magazine is slowly growing its own side business, Mole. It sells not because the product is so great, but more because of people’s trust in the magazine itself. This made me realize that low-traffic content doesn’t mean it has no value. Not many people read it, but the trust runs deep, and that can actually bring some unexpected conversions, which is pretty magical. It’s just run rather casually, but fairly consistently.

\n

So what am I really running? It should just be this magazine called Tw93. Whatever kind of person I am, I write that kind of content, and naturally I’ll meet that kind of reader, with no need to worry about what to write. In the end, what I most want to do is let the engineers reading this magazine and me learn from and grow with each other, but without the anxiety.

\n

\n Buy me a coke 🥤\n

"},{"title":"269. Tianmu Scenery","link":"https://weekly.tw93.fun/en/posts/269/","pubDate":"Sun, 07 Jun 2026 00:00:00 GMT","description":"\n

The cover photo was taken at Tianmu Scenery on Mount Tianmu in Lin’an, where I went the weekend before last. A really nice place, super cool in summer with plenty of fresh air. The Liuchun House up the mountain is delicious, highly recommend a visit, way fewer people than Jiuxi Yanshu.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

New Article

\n

You Don’t Know Embodied AI: From a Tiny Robot Dog to Optimus
\nhttps://tw93.fun/en/2026-06-07/robot.html
\nNew article is here. Back in April I assembled a little robot dog. I posted a few things about the build on Twitter, you’ve probably seen them. Then I wrote on and off for almost 2 months and finally finished it, the longest article I’ve ever written. Give it a read.
\n

\n

Product Releases

\n

Mole’s desktop client 1.6.2 is here
\nhttps://mole.fit/
\nI’m working to round out Mole desktop’s nice features as fast as I can. Just shipped 1.6.2, go update. If you haven’t bought it yet and are interested, you’re welcome to grab it. The price is expected to return to normal after June 15.

\n
    \n
  1. Keep Screen On (new): keep your Mac awake from the menu bar, with selectable durations. Restoring on launch now completes quietly, no more sudden admin-permission prompts.
    2. \n
  2. Privacy Check (new): the menu bar popover shows camera or microphone usage status and sends a local notification, so you can see it without opening the main window.
    3. \n
  3. Clean Screen (new): switch the screen to a solid color to make wiping the screen and keyboard easier. Press Escape to exit, and you can enable input lock too.
    4. \n
  4. Software updates cover more apps: Software now checks the Mac App Store, Sparkle, Electron, Homebrew cask/formula, Homebrew catalog, and GitHub Releases, with clearer progress.
    5. \n
  5. Uninstall finds more leftovers: leftover detection now covers receipts, Launch Items, Group Containers, Darwin temp caches, and more App Support traces.
    6. \n
  6. Clean is more useful while staying careful: Mole finds large directories like build, dist, target, and node_modules in your projects, but leaves them for you to review by default.
    7. \n
  7. Analyze scans faster: disk analysis adds concurrent computation, cache reuse, and subdirectory prewarming, so large directories open faster.
    8. \n
\n\n

Kami, where good content deserves good layout, has shipped a bunch of updates
\nhttp://kami.tw93.fun

\n
    \n
  1. Added a landing-page module. The Mole site and Kami’s own site you’ve seen are actually generated by Kami bootstrapping itself. It’s great for your product intro page, and it even thinks through Geo, Sitemap, and Vercel deployment for you, so you can build a site worry-free.
    2. \n
  2. Finally supports Marp slide mode, back to the days of writing slides in Markdown. One md file exports to HTML, PDF, or PPTX via marp-cli. The theme ships with Kami’s colors and fonts, works out of the box, and stays lightweight.
    3. \n
  3. Turns out there are quite a few Korean users, so on top of Simplified Chinese, Traditional Chinese, English, and Japanese, Kami now has fine-grained Korean support and multi-template designs. If you’re a friend from Korea, you’re very welcome to try it and send me feedback.
    4. \n
  4. The one-pager module, portfolio, and slides now all support importing your brand logo and other brand cues, so Kami blends right into your brand style.
    5. \n
  5. Since we’re engineers, Kami also does automatic syntax highlighting for code, coloring it for you at build time with no external CSS needed.
    6. \n
  6. One more fun thing: although Kami is also a Skill, it’s actually 70% code rather than Markdown. If you want to learn how to write a Skill that’s obedient and useful by default, you’re welcome to read the code, it might help https://github.com/tw93/Kami
    7. \n
\n

\n

Made a nice website for Kaku
\nhttp://kaku.fun
\nFinally done, built using the Kami skill, with a lot of docs filled in, and it supports both Chinese and English. Little Kaku finally has its own website, go take a look. Also, Kaku 0.12 is out, remember to update~
\n

\n

Just Looking Around

\n

Come check out my latest desk setup
\nReally happy, it arrived over the weekend. Before, I had a thick book plus a slab of mahjong tiles under my monitor, and the height was just right, but my OCD wanted a clean, unobtrusive 30×20×10 block to put underneath. I looked at lots of dedicated monitor risers, all too big, and looked at acrylic boards too, a bit rough, no solution.
\nHere’s the kicker: somehow while browsing PDD I stumbled onto these Buddha-statue bases. A perfect fit, ten times cheaper, and they work great!

\n\n \n \n \n \n \n
\n \n \n \n \n \n
\n

Can’t believe I only just watched “A Love Letter to Grandma”, highly recommend
\nOver the weekend I went to see the film “A Love Letter to Grandma”. It’s about to leave theaters, really good and really moving, the best film I’ve seen in a cinema in the past couple of years. The young actors were cast really well. If you haven’t seen it, definitely go when you have time!
\n

\n

Just Saying Thanks

\n

Some trade-offs I’ve made building products
\nMore than 20 days after Mole Mac launched, sales hit a small milestone. I want to share some of the trade-offs I made along the way, and why early on I handled every bit of user communication, Q&A, and refunds entirely by hand. Hopefully it gives some input to folks building their own indie products.

\n

First, why do I handle user Q&A, feedback, email replies, refunds, activation-code resets, price-difference refunds, and so on completely by hand, even though they’re less than 1% of users and I could honestly spend half an hour writing an Agent to handle them? This is a common trap for engineers building products, something that looks efficient but isn’t actually great. There are two considerations here. Only by genuinely handling users’ after-sales issues can you feel what users really need, why they want a refund, why something feels hard to use, their real suggestions and feedback. You can even exchange emails to surface more of their real needs, and through this process you get fluent at knowing the best replies and solutions for every kind of problem. That way, once the product gradually grows, bringing in an Agent for efficiency works much better than doing it from the start.

\n

Second, why I don’t recommend building a so-called after-sales system from day one. This is an important technical-judgment call for a product engineer: prioritize getting the main product features right, rather than standing up all your peripheral support systems up front. AI is fast, but it still pulls your precious time away from improving the product itself. It looks like it costs no time, but it actually costs you a lot. Spending that time improving the product and meeting users’ real needs is far better.

\n

Next, I want to talk about some common pitfalls when engineers transition to indie product development. First, what’s the difference between a good product and an average one? A good product is better at deciding what not to build, at which stage each feature is best for the product and users, and which features, even if good, don’t belong on the product’s main line and shouldn’t be added, otherwise it easily turns into a mishmash that’s hard to maintain. Another trait of a good product is that you actually hold the next six months of its development in your head, clearly knowing which features each version should add, which are false needs, and which features should sit right where users naturally reach for them. A product that ordinary beginners don’t need a manual for is a good product. That’s also why, when some friends suggested adding nice Mac features to Mole, I apologetically declined, staying restrained and firmly believing in the product view of “don’t add entities unless necessary”.

\n

Mole’s positioning is the quiet guardian of Mac system optimization, cleanup, and maintenance. Keep that positioning, refine it, and make it the best Mac maintenance software in the world. If 1 in every 100 Mac users worldwide used Mole, then Mole would truly be good, and that’s what I chase as a product maker: letting more non-technical folks enjoy the fun of an engineer’s product. Recently some visually impaired users have been using Mole and ran into a few accessibility issues, which I’m rushing to fix. I’m really looking forward to how it works and feels for them.

\n

Maybe in the AI era a lot of things have indeed gotten much more convenient, but communicating with people can’t be replaced by AI, otherwise it loses its meaning. AI can boost efficiency, but it can hardly deepen the feeling and trust between people. This might be a good way for products built with AI Coding to keep a human touch going forward.

\n

Since this is my first paid product, there may be things I haven’t thought through, and I welcome experienced friends to point them out and offer suggestions.

\n

\n Buy me a coke 🥤\n

"},{"title":"268. Xiaohe Park","link":"https://weekly.tw93.fun/en/posts/268/","pubDate":"Mon, 25 May 2026 00:00:00 GMT","description":"\n

The cover photo is of a textured building I shot last weekend at Xiaohe Park. The sunlight happened to be perfect, paired with the green trees, it looked really nice.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

Product Releases

\n

The Mole desktop client is here
\nhttps://mole.fit/
\nFinally, finally, Mole’s Mac desktop version is out. The CLI will keep being free and open source forever. The desktop client is for folks who enjoy a more interactive product feel. We recently shipped 1.5, which adds various sprite animations in the menu bar, login-item management, software update management, and the most fun part, fan control, plus more. Head over to the official site for the full rundown. Weekly readers get 20% off with code MOLEWEEKLY. Early-bird price is currently $9.

\n

If you’ve contributed code to Mole or sponsored me on GitHub, DM me and I’ll send a 100% discount code.

\n

\n

Mole CLI updated to 1.39
\nhttps://github.com/tw93/Mole

\n
    \n
  1. mo clean major hardening: GUI app dotdirs and Gradle DSL caches are no longer wiped by mistake; dry-run now matches actual cleanup so no more false reports; simctl probing retries to fix the first-error-after-restart issue; Trash cleanup no longer triggers blocking macOS warning dialogs; TMPDIR cleanup is roughly an order of magnitude faster; added cache coverage for UTM/Lima/Arc/QQ Browser/Codex CLI/Antigravity/Gemini; VS Code family now cleans leftover extensions by the .obsolete marker.
    2. \n
  2. mo uninstall: bundle ID matching upgraded to boundary checks so it won’t hit by mistake; leftover login items are now called out with their cleanup paths in the summary. mo purge: hardened with timeout protection and trap handling, any exit path restores the cursor and clears temp files.
    3. \n
  3. mo analyze: hardlinks are now deduped by inode, so FCP and other managed media no longer report tens of times inflated. mo status: available-memory math now aligns with Activity Monitor.
    4. \n
  4. mo touchid: PAM writes switched to atomic operations to preserve read-only permissions. mo optimize: removed Bluetooth reset to avoid accidentally kicking devices.
    5. \n
  5. Global NO_COLOR=1 support. When Trash isn’t available, it now fails closed to prevent silent permanent deletion.\n\n
    6. \n
\n

Kami now builds product landing pages
\nhttps://github.com/tw93/Kami
\nKami has shipped a bunch of updates lately. Beyond the original PDF generation, you can now tell it you want a landing page for product XX, and it’ll build something in the same quiet style as the Mole site.
\n

\n

Waza has had a bunch of updates lately
\nhttps://github.com/tw93/Waza
\nWaza (技, わざ), the engineer’s skill collection, has had a bunch of updates recently. Posting a tweet to keep everyone in the loop. If you’re using it, remember to update. I’ve folded in nearly a month of dev best practices, especially a lot of lessons from the recent Mole client work.

\n

First, Waza finally supports codex end-to-end. One command and you’re done, every capability is supported, because codex has felt really good to use lately.

\n

The biggest one: the original health skill was just for checking whether Claude config and usage matched best practices, but now it’s evolved into a full Agent Health check. There’s a fun phenomenon with people writing code with AI now, it feels amazing at first, but after a while it becomes unmaintainable and hard to extend. In that case try /health, it’ll check your code, including whether the various capabilities still look ok, whether it’s maintainable, whether things should be split apart, whether dead files should be deleted. Think of it as a scavenger for the bad code AI generates.

\n

Then /think (Thinking Mode) also has many updates. You can discuss with it whether a feature should be built, and it’ll give you a Kill / Keep / Pivot judgment across multiple dimensions. Honestly, a lot of the time a product is defined by what you choose not to add, not by what else you could add.

\n

I’ve always felt that adding rules to AI calls for restraint. Every rule you add becomes a ceiling for it. When the model gets stronger, your rules start dragging it down. That’s why I don’t like Superpowers or so-called Spec programming, too verbose, too many rules. That’s also why I wrote Waza, it’s like installing my code-writing avatar onto your computer.

\n

Trending Tools

\n

Lightpanda: a headless browser written from scratch in Zig
\nhttps://github.com/lightpanda-io/browser
\nA headless browser written from scratch in Zig, designed for agents and automation. The pitch is -9x memory and +11x speed vs Chrome, compatible with the CDP protocol (Playwright/Puppeteer). Worth a look as browser infrastructure for the agent era.
\n

\n

Mise: Dev tools, env vars, and tasks in one CLI
\nhttps://github.com/jdx/mise
\nA single tool that unifies runtime versions (nvm/asdf) + env vars (direnv) + tasks (make), all managed by a single mise.toml. Lightweight Rust binary. Worth a try if you’re interested.
\n

\n

Just Looking Around

\n

Recommending this lemon-flavored sparkling water
\nYou have to chill it first, then it’s really good. Don’t drink the plain one, this lemon one is the best!

\n\n \n \n \n \n
\n \n \n \n
\n

This eye drop I’ve been using is pretty good
\nIf you often lose yourself in AICoding, grab a bottle of Hai-Lu eye drops, and have your watch remind you to stand up and walk around.
\n

\n

Bought a few nice wooden things
\nFirst is a shoehorn, no more bending over to put on shoes. Second is a laptop riser, very useful, with anti-slip. Third is a small holder for aroma bottles. Fourth is the little brush I use to sweep up coffee grounds when I make coffee.

\n\n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n
\n

Some thoughts on the Mole desktop release
\nOn the back of the recent Mole Mac release, I want to share the magic moments I’ve had over the past couple days. Thanks to this little toy project I started by the Sanya pool last year, I’ve met many interesting overseas developers from all kinds of countries.

\n

The Mac client took two weekends to build. Plenty of overseas users had brought it up before, saying their parents and siblings don’t use a CLI but really want this feature, asking if I could put out a simple, easy-to-use desktop version. Back then there was the time issue, plus I didn’t think the Mole CLI was mature enough yet, so it kept getting pushed back until now.

\n

It’s only been half a year since Mole launched, and somehow it’s over 50K stars, 500 user-submitted cleanup-suggestion issues, 300 high-quality feature PRs, and contributions from 100 developers around the world, delivering cleanup capabilities arguably stronger than tools like CleanMyMac. I even racked up 60T of traffic in one week from just 2 images I hosted on Vercel for the README, which left me owing Vercel $80, that’s when I realized how many people are actually using it, so the desktop version was worth doing.

\n

A lot of the small clever touches in the Mole desktop client only came to me once I started building. Like using planets to represent each feature, which traces back to my childhood love of watching planets move, plus 10 years ago when I picked up frontend, the very first thing I wanted to learn was WebGL. I started using WebGL to render the planets, and each planet’s character lined up nicely with what Mole does, so I worked that theme in:

\n

Clean uses Earth, “Rain washes the old soil, dust drifts with the tide”
\nUninstall uses Mars, “Red dust covers the old, travel light to journey on”
\nOptimize uses Mercury, “Swift along the near orbit, small fixes ring out”
\nAnalyze uses Jupiter, “From afar it becomes a map, the smallest details visible”
\nStatus uses the Sun, “Light that doesn’t strike the eye, a heartbeat that stays bright”

\n

Like the little mole’s digging and exploration moving from a small patch to the wide world, but still quiet, not getting in your way.

\n

Another design touch: I swapped each planet’s texture map more than 10 times, downloading and picking through many from NASA’s site to find the best fit. The rotation direction and axis, the speed, the post-completion flight characteristics of each planet, all reference how the actual planets move. That part was one of the more enjoyable bits of AI Coding. These details might feel only loosely connected to Mole-the-mole, and I could have just built a simple click-to-clean menu bar app, but I didn’t want to. There’s already too much cyber junk being generated by AI. I needed to make something that feels a bit more pleasant, so that my tokens aren’t wasted, and so I’m not polluting your timeline.

\n

I released it around 10pm that night. So grateful for the many friends who shared it on their own, and especially thankful to all the users who bought it, some folks even bought it purely because of the value the CLI had given them. Lots of European and American users, with French, German, all kinds of currencies coming in, really magical. There’s still a lot to round out on the Mac desktop, and I appreciate everyone’s patience, prepaying $9 for a pretty little toy. I’ll keep working on the features.

\n

I really like things that come together naturally, I don’t like chasing short-term results. This kind of long-term iteration, continuously meeting new friends, getting so much input and discussion, is the most precious treasure. Really fun.

\n

\n Buy me a coke 🥤\n

"},{"title":"267. Westlake Stone Characters","link":"https://weekly.tw93.fun/en/posts/267/","pubDate":"Mon, 11 May 2026 00:00:00 GMT","description":"\n

The cover photo was taken last weekend. To get a feel for the strokes for my type design project Luo, I went looking for these kinds of stone-carved characters along the road by West Lake and snapped this shot.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

Just Writing

\n

You Didn’t Know GEO: AI Visibility Principles, Practices, and Trade-offs
\nhttps://tw93.fun/en/2026-05-01/ai-visibility.html
\nA bunch of friends have @-ed me lately saying my open source tools are getting recommended unprompted when they ask AI questions. I hadn’t done anything special, so I figured why not spend an hour structuring the content properly. After doing it I fired off a quick tweet, but the structure was messy. People seemed genuinely interested, so I decided to write it up as a proper article for reference and lookup.
\n

\n

Trending Tools

\n

Kami, the typesetting system that gives good content the layout it deserves, has been upgraded
\nhttps://github.com/tw93/Kami
\nKami has had several upgrades recently, including fixing Chinese garbled text in PPT, speeding up the engineering, expanding doc analogues to 8 categories, polishing many layout details, updating the built-in chart capabilities, and more. Welcome to update and try it out.
\n

\n

Waza, the engineer’s 8 skill trees, has been updated
\nhttps://github.com/tw93/Waza

\n
    \n
  1. Durable Context: six skills (think, check, hunt, design, write, health) can consume optional memory/preview context. Safety contract: current state always wins, raw conversation reads disabled by default, hardcoded machine paths not allowed.
    2. \n
  2. Plan Execution Mode: /check executes approved implementation plans step by step, defaults to review-then-ship continuation, document review routes to /write.
    3. \n
  3. Evaluation Mode: /think now outputs Kill/Keep/Pivot, deciding whether something should be done or kept.
    4. \n
  4. Validation guardrails: trigger word overlap detection, routing drift checks, attribution leak interception, preventing silent skill conflicts and accidental personal info leaks.
    5. \n
  5. Design and Write references: added typography traps, design tokens, aesthetic quality, Chinese-English mixed typesetting standards, release-note style guide.\n\n
    6. \n
\n

Kaku finally updated to V0.10
\nhttps://github.com/tw93/kaku
\n🥷 Long wait, everyone. Kaku finally hits V0.10. I held this version back through several minor releases while I kept tuning a really handy in-app Agent assistant. The vibe is a clean, no-nonsense tech buddy. You can summon it with Cmd + L without disturbing any of your existing content, but it’s smart enough to read your context, and I’ve equipped it with a curated set of solid tools. You configure its brain through kaku ai. I highly recommend setting up search capabilities, and pipellm is a nice option.

\n

AI features are something I’ve always wanted to build but didn’t want to disturb users with. If you’re more of a pure terminal user, I’ve also added plenty of features worth catching up on.

\n

First, there’s a fun smart window-close intercept. When you haven’t configured whether to intercept window closing in kaku config, if you’re in the middle of AI work it’ll dynamically intercept and ask whether you really want to close, so you don’t accidentally kill it.

\n

It also finally supports window snapshot. Kaku auto-saves multi-tab and multi-pane layouts. When needed, hit Cmd+Option+Shift+T or use Shell → Restore Previous Window to recover. This nicely solves the pain of accidentally closing a window and wanting to start back up.

\n

Some folks suggested that the light mode looks great but the dark mode contrast is a bit too strong. Got it. I’ve now tuned a much softer dark mode, dropping the saturation of highlight colors and slightly dimming foreground text, so staring at the screen for a long time is easier on the eyes.

\n

I’m also obsessive about startup speed, especially cold start. I want to build the fastest terminal. Through Lua bytecode caching, lazy initialization of fonts and config, shell user variable caching, and similar tricks, your Kaku now opens almost instantly. Still a tiny bit behind Alacritty, but I’m working on it.

\n

Lastly, fixed full-screen crashes and freezes, multi-monitor race conditions, resize gaps, cursor reflow, links, selection, light theme readability, TUI copy, and many other detail issues.

\n

If this is your first time hearing about Kaku, welcome to give it a try. Still not mature, actively being polished. Any suggestions or bugs, please file an issue and I’ll handle them.
\n

\n

Just Looking Around

\n

M5 Pro in black finally arrived. Stunning. Very excited
\n16-inch M5 Pro / 48GB / 1TB black with standard glass. I think this config is a great fit for anyone considering a new machine.
\n

\n

Picked up an iPhone SE3 to play with
\nHow can such a small phone feel this refined? Just lovely to hold.

\n\n \n \n \n \n \n
\n \n \n \n \n \n
\n

A neat UI bug debugging trick of mine
\nSharing a really useful UI bug debugging approach. Back in my old-school coding days I often used screen-recording with slow-motion playback. AI struggles with this kind of thing, but humans get it instantly. Find the frame with the problem, and you basically know where the issue is. Then hand the screenshot to AI. Way better than logging or guessing.
\n

\n

Somehow it’s been 4 years on Twitter, posted a little reflection
\nJoined X 4 years ago already. The journey has been really fun, and it’s also been a great outlet for my urge to share tech and product stuff.

\n

I was just chatting with a new friend about how I ended up here. Back then it was still called Twitter. MiaoYan had just been written, and I was looking for somewhere to sync update logs. Yes, that simple. So I signed up with Google login and posted MiaoYan’s intro. Magically, it turned out MiaoYan was already being recommended by lots of folks with big followings as a simple and handy markdown-native notes app. Coming over felt like, oh, there are so many friends here. We finally meet. The Twitter environment back then was great. Not so many ads or money-grabbing. More sharing, conversation, pure tech discussion. Sad to say, many of those friends whose output quality was way higher than mine slowly stopped posting much.

\n

Later I gradually started sharing some good open source products I’d come across each morning, or the latest releases of my own products, and bits of my own thinking. Slowly I met many like-minded friends, and they put a lot of energy into contributing to my open source projects. Friends from Taiwan, Japan, Turkey, Europe, the US, and especially many friends who helped with Pake. That was a kind of pure code-writing era from before AICoding existed.

\n

When ChatGPT first came out, I immediately registered an account and started playing with 3.5. It really was a magic moment. Back then we shared funny prompts, very fun, but it now reads like ancient literature. I even wrote an article on 2022-12-04 titled “How Ordinary People Avoid Being Replaced by OpenAI.” Haha, you can see how shallow I was. The first deep question I asked was even “give me some online docs to learn Rust.” How AI has developed since then is beyond comparison.

\n

That was about when I felt all in on AI. At the company, I handed off all my main business support tech to my direct reports, and went looking for a bigger ceiling for my team in AI. I even paid out of pocket with my international credit card to buy official OpenAI API for the team to use, so we could understand the latest stuff. I solved a lot of business problems that had been giving managers headaches with AI. Meanwhile, since I’m good at sketching solutions and product flows, I also pushed AI application R&D platforms, B-side digital employee solutions, and the deep integration of business efficiency tools with AI. Three years on, much of it is now well-productized and efficiency has improved dramatically.

\n

Because the results in practice were so clear, in early 2023 I moved all my Chinese ADRs and company-allocated stock all in on AI direction. I sold them very cheaply, but bought what now look like treasures. Like Tesla I love at around 130, NVIDIA at around 90, SMH at around 160, etc. Around then I started intentionally learning to invest, analyzing companies and their underlying value, and read many books to sharpen my thinking. The books didn’t help much operationally, since most were written decades before AI, but the mindset is useful. Investing in AI also can’t follow the old playbook. It gave me an interest outside of programming, which is fun. Maybe one day I’ll build an investing-related AI product.

\n

Then, as you all know, came Mole, written last National Day during a Sanya pool vacation between swims and rests. Mole introduced me to many overseas developers. My overseas follower count grew sharply because developers from all over the world have been actively spreading the word almost daily. So grateful! Then came Kaku written during this year’s Spring Festival, plus the recently efficiency-boosting Waza and Kami, and now that the new machine is here I’m planning a font called Luo. The journey has been wonderful, and I’m really looking forward to what’s next. New friends are very welcome.

\n

\n Buy me a coke 🥤\n

"},{"title":"266. Masked Sculpture","link":"https://weekly.tw93.fun/en/posts/266/","pubDate":"Mon, 27 Apr 2026 00:00:00 GMT","description":"\n

The cover photo is a sculpture of a child wearing a mask, taken on the weekend while running errands over in Gongshu. In a flash, the pandemic already feels like a long time ago, and yet it also feels like just yesterday. Those years are still worth remembering.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

Introducing the Tw93 Open Source Family

\n

https://github.com/tw93
\n

\n

After finishing Kami, I suddenly realized that Kaku, Waza, and Kami feel a lot like a small family. Then I kept thinking, and actually Pake, MiaoYan, and Mole have always been quietly part of this family too. Some of them were even out doing real work before AI showed up. Today let me introduce you to this warm and happy little family.

\n

Kaku is the dad. He mainly handles writing code, the terminal, and builds. Very reliable and capable in the AI era, he holds the family together well.

\n

Pake is the mom. She has been quietly packaging, organizing, and delivering apps all along. Gentle and efficient. She is the kids’ favorite in the family.

\n

MiaoYan is the older brother. Sensible and steady, he likes writing, Markdown, and reflective thinking. A quiet young man who thinks for himself, has his own opinions, shares his views, and never chases trends or follows the crowd.

\n

Waza is the older sister. Her personality is similar to mom’s, very sharp and capable. As a kid she even practiced taekwondo. She loves learning, and through endless practice and reflection she sharpens her skills until they become instinct.

\n

Kami is the younger sister. The youngest little sweetheart in the family, generated based on my daughter’s photo. Bright and cheerful, always smiling, very sunny. She has a kind of order-keeping presence at home, loves tidiness, and loves drawing pretty pictures. Small, but very warm.

\n

Mole is the family’s little pet mole. Brought home one year while swimming by a pool in Sanya. A round little mole with a tiny headlamp and a small shovel. He loves rummaging through corners, finding things you no longer need and helping you throw them away. He loves cleanliness. The moment he spots trash, before you can react, it is already gone. Always there, keeping us company.

\n

So, which member of the Tw93 Open Source Family did you meet first? Let me introduce the rest of the family to you, hoping they bring a little something good into your life. And of course, feel free to introduce them to your friends too.

\n

Product Releases

\n

Kami: A Comfortable Typesetting and Design System for the AI Era
\nhttps://github.com/tw93/kami
\nThe weekend before last I started working on a new Skill called Kami (紙, かみ). You can think of him as the younger sister of Waza (技, わざ) and the daughter of Kaku (書く), focused on Paper typesetting scenarios. Last Monday I finished the open source release. Welcome to give it a try.

\n

For example, when you need to produce a one-page report, write a white paper, generate a polished slide deck, or build a portfolio PDF to send to someone. Any printing or typesetting scenario works. It auto-generates beautiful PDFs, and even has the ability to draw clear charts automatically.

\n

Plenty of updates lately. The most fun one: I added support for 12 inline SVG charts, things like stock investment charts and architecture diagrams, all with colors that match Kami. While generating your layout, it automatically decides whether chart capabilities are needed, helping you explain things more clearly.

\n

I also spent some time supporting English and Japanese scenarios, carefully picking fonts, letter spacing, line heights, and font sizes that I think work well for typesetting. If you have English or Japanese use cases, give it a try.

\n

The output also supports image and slide deck export, including HTML display. The best output for typesetting is still PDF in my opinion, since it reads very comfortably for others.

\n\n

Mole has updates, plus good news: progress on the desktop client
\nhttps://github.com/tw93/Mole

\n
    \n
  1. mo uninstall: cleans up leftover LaunchAgent/LaunchDaemon plists after uninstall; recognizes pkg-installed apps under non-standard paths like /usr/local and /opt; nested helper apps no longer block login item cleanup; sudo is dropped before calling brew, avoiding cask uninstall failures from “running as root”; Homebrew bottles now run correctly under prefixes that contain spaces (such as Applite).
    2. \n
  2. mo clean: Service Worker ScriptCache is no longer cleaned while Chrome / Arc / Brave / Vivaldi / VS Code / Cursor are running, so MV3 extensions stay intact; TCC-protected Group Containers are skipped to avoid repeated privacy prompts.
    3. \n
  3. Cloud & Office segments now have timeout and SIGINT handling, no more freezing; Microsoft Office helpers and research software bundles are no longer flagged as orphans (compatible with macOS’s built-in bash 3.2); added Yarn v1 global cache cleanup.
    4. \n
  4. mo clean: legacy AI coding assistant cleanup adds GitHub Copilot CLI (~/.copilot/pkg/universal//), handled alongside Claude Code and Cursor Agent.
    5. \n
  5. mo analyze: worker pool cap lowered again to prevent system thread exhaustion in Steam-like fan-out scenarios; uses incremental cache invalidation when deleting files, no full rescan needed; bundle parsing falls back to the filesystem after mdfind timeouts.
    6. \n
  6. mo optimize: gracefully skips periodic maintenance on macOS 26+ where the underlying tool no longer exists; adds mo optimise alias and completion.
    7. \n
\n

Just Writing

\n

The AI Coding You Don’t Know: Onboarding, Scenarios, and Practice for Non-Technical Folks
\nhttps://tw93.fun/en/2026-04-26/ai-coding.html
\nLast month I gave a session at work for product and business folks on how to get started with AI Coding. Recently I also posted about it on Twitter, and a lot of people brought up that subscription costs prevent them from accessing the top-tier AI Coding tools. The methods and habits can actually be learned for free first, so I decided to write up the onboarding part. To make it easier to grasp, the article includes plenty of simple illustrations, which should make it more direct.
\n

\n

Video version of “The Agent You Don’t Know: Principles, Architecture, and Engineering Practice”
\nhttps://www.youtube.com/watch?v=Z5If1L3eFtw
\nFinally uploaded to YouTube. If you read the article and did not fully follow it, or want a deeper look, the video version is up. New to YouTube here, so please like, subscribe, and share. From now on I will try to record more sessions and share them here.

\n\n

The slides are also fun. They are the predecessor of Kami. Kami started as a small investment report generator I was tinkering with inside CC. Around the same time I had a session about agents to give, and writing such a long deck felt tedious, so I just used the existing capability to generate and tweak versions until I was satisfied. That is how Kami was born. Welcome to read.

\n

Moments of Happiness
\nA lazy Sunday afternoon coding in the study
\nNothing else to deal with
\nEndless Claude Code
\nCode that works on the first try
\nLook up and see the sunset coming through the window
\nA very simple kind of happiness
\n

\n

Some thoughts after sharing, and they have shifted again
\nRecently I interviewed a number of 985 university interns for campus recruiting. One strong impression: AI tools are rapidly widening the resource gap between students.

\n

From what I have seen, the gap can really reach 5x. The students clearly ahead, without exception, all got into Claude Code, Codex, and other top AI Coding tools relatively early, and were willing to pay for subscriptions themselves. They do not just use the tools, they have made them part of their daily learning and development. Talking models, engineering, agents, and code practice, the conversation flows naturally for an hour. In many places they understand things more deeply than I do.

\n

But there are also quite a few students with great grades and solid CS fundamentals who, because of family conditions or budget limits, can only use domestic relays or cheaper local model packages. That gap is very real. The best domestic models and top international ones still have about half a year of difference in overall capability. Before AI, the resource gap mostly meant slightly different efficiency. Now it directly affects vision, depth of practice, and confidence.

\n

I have been thinking about this a lot. For students with real potential, missing out on so much just because of a few dozen dollars a month feels like a real shame. It reminds me of when I was in college, also pretty broke most of the time. Lucky for me, in my second year I met some senior developers who pulled me into commercial projects and got me on my feet. I am very grateful to all the friends who patiently taught me technical things back then.

\n

So I want to try a small experiment: take part of the X posting revenue and sponsor a few students who do well academically, love computer science, but come from less wealthy families. Give them a few months of Claude Code or a similar AI Coding subscription, so they actually experience what good models and dev workflows feel like.

\n

But I am also pretty busy on my end and cannot personally handle applications, screening, verification, and long-term follow-up alone. So I want to invite some friends with similar interests to do it together. University teachers, student leads, open source community members, or friends already working in education, public welfare, or developer communities. Together we can come up with a more reliable mechanism.

\n

I do not want to make this big or complex for now. Start small, maybe 5 to 6 students per round, 3 to 4 months each, perhaps with short weekly video chats with me. Prioritize recommendations, work portfolios, learning records, and real usage feedback, to avoid turning this into pure cash handouts or a contest of who writes the best application. Of course, college students who are on X probably do not lack this money, so we still need better channels.

\n

If you have reliable channels, or want to help with rule design, recommendations, vetting, or follow-up, please DM me. If we can make this trustworthy, maybe we really can help a few students with real potential.

\n

Update Reply:

\n

After the message went out, I received plenty of suggestions and reminders from friends. I read them all carefully.

\n

This really cannot be pushed forward on enthusiasm alone. On one side there are tool usage boundaries and compliance risks. On the other, the real needs of the student community, the screening method, and the follow-up feedback all need a more solid mechanism. Some friends mentioned getting badly burned doing similar things in the past, even bitten back in the end. I find that reminder very valuable.

\n

So the plan now is to first gather more on the actual situation, like the real pain points college students face when using AI Coding tools, budget limits, learning scenarios, and real needs. Then put together a clearer proposal.

\n

Going forward, I will prioritize working with domestic large model vendors, developer communities, and university teachers to see if there is a more formal and sustainable way to push this small step forward.

\n

\n Buy me a coke 🥤\n

"},{"title":"265. Xixi Window View","link":"https://weekly.tw93.fun/en/posts/265/","pubDate":"Mon, 20 Apr 2026 00:00:00 GMT","description":"\n

The cover photo is from lunch at Yueya in Xixi Wetland one noon this week. I had not been there in a long time. The place still feels great. The sun was out, short sleeves felt just right, and I took this shot outside the window. Spring moves fast.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

Talking About Waza’s Design Ideas

\n

I want to write a few pieces introducing the implementation references behind some interesting skills in Waza. Last week I wrote one every morning, so I am collecting them here for everyone.
\nhttps://github.com/tw93/waza

\n\n

Introducing the /design Skill

\n

I really dislike those AI-generated websites that all look the same, often with emoji and blue-purple gradients. They look ugly to me. Usable, sure, but that is about it.

\n

So I asked Claude Code to study my tuning notes from all the UI websites I have built recently. It produced a basic set of what I consider best practices and anti-patterns. That became the initial shape. Then I learned the useful parts from the Claude frontend design skill, and a pattern basically came together.

\n

For concrete rules, I learned quite a bit from pbakaus/impeccable. It contributed many specific rules for me, including banned font lists, color systems, theme styles, forbidden CSS patterns, animation standards, and more. These help give AI some aesthetic knowledge.

\n

Then I took a capability from getdesign: a nine-part scaffold structure originally from Google Stitch. I simplified it and folded it into /design. At that point, the skill had a proper knowledge system.

\n

Finally, when I ask you to use this skill, it first asks a few questions: who will use it, what aesthetic direction to choose, what you want users to remember from the page, what you dislike most, and what kind of signature micro-interaction the page should have. With this important context plus /design, Claude Code often gets much better results.

\n

How I Designed the /check Code Review Skill

\n

First, we need to understand that when a model says it is done, it may not actually be done. It may have left behind nonexistent things or problematic details, and issues often stay hidden. In Agent design, my engineering experience is to give the model a checklist to verify whether the work is truly complete. This tends to work far better than simply asking it to check the result.

\n

From the beginning, /check was not designed as one big all-in-one reviewer. It is an orchestration and division-of-labor system. SKILL.md is the lead reviewer, responsible for review levels and process control. Under agents/, there are independent security and architecture reviewers. Each handles its own area without interfering with the others. Which reviewer gets pulled in, and when, is decided by activation rules rather than the keyword matching people usually use.

\n

The level logic is also interesting. Code changes under 100 lines get a fast review. Changes between 100 and 500 lines bring in experts as needed. Changes above 500 lines bring in the full set, followed by a round of adversarial testing. The adversarial testing looks for problems from four angles: violated assumptions, possible issues under combined failures, errors across parent-child chains, abuse scenarios, and so on.

\n

The issues found are handled in four levels. Things that can be safely fixed are fixed directly. Things that are probably right but need confirmation are packaged up for you to approve manually. Things that require judgment are asked about. Reference-only items are also reported, but it will not ask you about every tiny issue, and it will not overstep by changing behavior logic for you.

\n

There is also a hard requirement: if verification has not finished, the task is not complete. It includes a detection script that can identify project types such as Cargo, TypeScript, and Python, then run the relevant tests. If it cannot detect the project type, it reports an error directly instead of pretending everything passed.

\n

This makes it feel more like an experienced technical expert applying review judgment to different situations. I happened to distill that experience into Waza’s /check skill in a very simple way.

\n

How I Designed the /think Skill

\n

This is already the third part of the Waza skill design notes. Today I want to share how I designed /think, the skill used for planning before writing code.

\n

I have two very interesting settings when using Claude Code. The first is /model opusplan, which means planning uses the strongest Opus model by default, while execution uses the regular Sonnet model. This helps save my Max quota for places where it matters more.

\n

The second is that I usually run Claude Code with the alias c=\"claude --dangerously-skip-permissions\". I do not recommend this for technical beginners. I use it because I know what it is doing, and mainly because I am lazy.

\n

Back to the main topic: how does /think help the strongest model perform better? It starts with the model itself. Models do not like taking a position, but I prefer engineers who can take a position and recommend the best plan. So the first thing I did was require the model to state its position at the beginning, explain what evidence could overturn that position, and explicitly ban correct but useless filler like “There are many ways to think about this”. Giving 2 or 3 options is fine, but there must be a clear recommendation, and it must include a minimal option.

\n

A plan is not done just because it has been thought up. The second step asks it to argue against itself: under what conditions would this plan fail? If the issue can be fixed, it adds the fix back into the plan and presents it again. If the issue breaks the plan outright, it directly explains when and why the plan does not work. At least the plan you receive is one you understand clearly.

\n

It also checks assumptions carefully. First, confirm whether the target directory and code location are correct. I have actually seen it produce a plan against the wrong path. Then it checks old technical design documents to avoid reinventing things. Then it searches GitHub to see whether others have handled similar problems. Only after these three steps does it start thinking about solutions, so the plan is not built on a wrong premise from the start.

\n

There is also complexity grading. If more than 8 files are involved or a new service is added, it clearly states the scale. If more than 3 components exchange data, it draws an ASCII diagram to look for cycles. All API keys and third-party dependencies are listed during the planning stage, preventing wasted work and unreliable plans.

\n

Finally, there is a hard rule: the plan cannot contain TBD, TODO, “leave it for later”, or “similar to step N”. This goes back to AI’s behavior. If you leave these openings, execution can easily miss things or improvise too much. Do not give AI any escape route that can lead to poor results.

\n

The output format is also defined: what to do, what not to do, which option was chosen and why, 3 to 5 decision points, and explicit unknowns. /think never writes code. It waits for user approval before execution.

\n

When I designed the Think skill, I was also using my idea of how a good technical expert writes a technical plan: detailed analysis and research, a decisive best plan, no loose ends, and immediate plan refinement when challenged.

\n

Talking About the /hunt Skill for Engineers

\n

This is finally part 4 of the Waza skill design notes. After this, it is almost complete, because the other two, /read and /learn, were already briefly covered before. This time I will continue with the engineering skills and talk about /hunt, which is the skill for debugging and investigating problems.

\n

One major difference between superficial AI coding and serious AI coding is visible in how users use AI to investigate problems that have stayed unsolved for a long time. The troubleshooting process shows a clear gap. This is also why experienced engineers can use AI to solve much more complex problems than people who understand less about technology.

\n

I often ran into this before: Claude Code hits a problem and fixes it with a patch. You say it is wrong, so it gives you another patch. After 4 or 5 rounds, new problems appear. It is easy to keep patching without diagnosing the actual issue, much like junior developers did before AI.

\n

The core rule of /hunt is interesting: before AI can state the root cause in one sentence, it is not allowed to touch the code. That sentence also has a precision requirement. It needs to clearly explain the cause.

\n

Then I designed a self-deception checklist to prevent the model from falling into several common patterns of self-justifying thinking. Each pattern has matching rules, and the gotchas include real cases. I summarize and abstract this again based on issues I ran into while debugging over the past month.

\n

The hypothesis verification stage also has concrete work requirements. For example, add a fresh observation method, teach AI to add logs, add assertions, or run a minimal failing test case. If there are still problems after the fix, it should immediately switch plans. It organizes what it checked, which directions it investigated, and what remains unknown into a handoff for the user to decide how to continue, instead of trying endlessly.

\n

The output also guides AI to include the root cause at file:line, what changed at file:line, what evidence confirms the fix, and which tests passed. The final state has three options: resolved, resolved with caveats, or blocked.

\n

You can see that /hunt behaves like an experienced technical expert. When it hits a problem, it does not guess. It slows down, looks for where the problem is, diagnoses the cause clearly, and then fixes it in one pass. This often saves a lot of time.

\n

Things to Browse

\n

MiaoYan released version 3.2.0, Nargacuga
\nhttp://github.com/tw93/MiaoYan

\n
    \n
  1. Faster preview: two-stage rendering shows text immediately, while local images lazy-load in the background. This noticeably reduces the wait for the first preview screen.
    2. \n
  2. Terminal shortcut: added Cmd+J as a global shortcut to open the terminal for the current folder anytime. The folder right-click menu also has the same entry.
    3. \n
  3. Copy path: right-click any note to copy its full file path directly.
    4. \n
  4. Spanish localization: complete Spanish translation coverage for menus, settings pages, and system strings.
    5. \n
  5. Mermaid upgraded to v11.14.0, fixing subgraph edge rendering issues and adding new chart features.
    6. \n
  6. Real-time reload fix: notes modified by other tools now correctly trigger reloads, including files inside symlinked directories (closes #502).
    7. \n
  7. Startup and window fixes: opening .md files directly from Finder no longer shows a blank screen. In single-column mode, notes are no longer lost during startup or exit.
    8. \n
  8. Export and mode switching: fixed blank previews when switching notes, timing issues when exiting PPT presentation mode, export timeout handling errors, and more.
    9. \n
  9. Concurrency safety: fixed ExportCache data races, security-scoped URL leaks, and note state confusion after async rendering.\n\n
    10. \n
\n

Kaku has an interesting feature coming soon. It should ship in a few days
\nhttps://github.com/tw93/Kaku
\nKaku has been developing an interesting feature recently: a real Agent assistant that can move smoothly inside the terminal. It gradually realizes the quiet Kaku AI idea I mentioned during Chinese New Year, and it also helps me move 100% of my coding work fully into Kaku.

\n

A very convenient context environment, useful CLI tools, models, and a restrained personality make Kaku feel different. It is not cold, and it is not the over-the-top “I have got you” style of GPT either. Kaku AI is positioned as a technically strong, friendly, and concise engineer friend. Once I test it for a few days without bugs, I will release Kaku 0.10 for everyone to try.
\n

\n

My Claude Code Max usage suggestions
\nFirst, I add an alias in .zshrc, so every time I press c, it starts dangerous unrestricted mode directly. If you are a beginner, I do not recommend starting this way. Auto mode is enough. Another big suggestion is to set the automatic context window compaction to 400k. Together, the alias below goes into the file, which means the 1m context window starts compacting at 40%. The result feels much better.

\n
alias c='CLAUDE_CODE_AUTO_COMPACT_WINDOW=400000 claude --dangerously-skip-permissions'
\n

Then I set /model to opusplan. You can run the hidden command /model opusplan directly inside Claude Code to enable it. If you want it faster, you can turn on /fast, which nicely makes up for the token savings above.

\n

Finally, someone gave me a really good suggestion: when using opusplan, make sure to set showClearContextOnPlanAccept to true in the Claude config file ~/.claude/settings.json. Otherwise, Sonnet can run into serious cache miss issues. Once this is configured, the experience feels much smoother.

\n

\n Buy me a coke 🥤\n

"},{"title":"264. Finally Done","link":"https://weekly.tw93.fun/en/posts/264/","pubDate":"Mon, 06 Apr 2026 00:00:00 GMT","description":"\n

The cover photo is a shot of my hardware toy finally finished. It was a fun ride, and I wanted to document the whole process in this week’s issue. Hope you enjoy reading it.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

New Article

\n

How I Deep-Dive into a New Technical Domain in the AI Era
\nhttps://tw93.fun/2026-04-06/learn.html
\nA follow-up to the learning writeup from last time, combined with the /learn skill inside Waza, walking through how I actually wrote that previous large model article. Hope it is useful to you.
\n

\n

Building a Little Robot Dog

\n

April 4: Back to hardware basics. I want to build something that combines software and hardware.
\nAll the parts and tools had finally arrived, a whole table full of them. Saving it all for the Qingming holiday to dig in properly.
\n

\n

April 4, 9:45 PM: v0.1.0-beta
\nThe first sign of life. I was so happy I couldn’t describe it.
\n

\n

April 5, 12:07 AM: v0.1.0-beta1
\nGot the WiFi module, AI module, microcontroller module, and quad-leg module all running together. Tomorrow I’ll attach the legs and tune the screen. Going to sleep right now!
\n

\n

April 5, 1:45 PM: v0.1.0-beta2
\nMechanical leg control is working. It can crouch, sleep, and walk. Still rough around the edges, but one of the leg motors from the order looks like it has a problem. Waiting on a replacement part.
\n

\n

April 6, 10:33 AM: v0.1.0-beta3
\nAll four legs are fully under control now. But I burned the screen during debugging. Waiting on shipping. Can’t wait to release.
\n

\n

April 8, 11:37 PM: v0.1.0-beta4
\nThe replacement screen arrived after work. Got it running, then tuned the temperature, CO2, infrared, and lighting sensors all in one go. Still working on WiFi provisioning. It’s basically taking shape now, just need to seal and secure everything.
\n

\n

April 11, 11:30 AM: v0.1.0 finally ships 🎉
\nSealed up the battery pack and tied a few straps around it to keep things from falling apart. Got the WiFi and AI conversation module working too. Using DeepSeek makes it noticeably faster, response speed is decent. Next up: something with more advanced hardware.
\n

\n

A few photos from different angles to mark the moment

\n\n \n \n \n \n \n \n \n \n
\n \n \n \n
\n \n \n \n
\n

Trending Tools

\n

App Store Price: Look up app prices across different countries and regions
\nhttps://app.vbr.me
\nA handy little tool. You can check what an app costs in any App Store region, like figuring out which country has the cheapest Claude subscription. I’ll probably find a use for this soon.
\n

\n

Random Thoughts

\n

Let me share what I think makes for a genuinely good product experience.

\n

There’s a followup to my lost drone story. The signal cut out mid-flight, I searched for a long time, couldn’t find it. I uploaded the flight logs and DJI couldn’t find a clear cause either. Even without being sure it was actually lost, they asked for very minimal proof and, under their Care Refresh service, just shipped me a brand new one. They even threw in a 128GB card in case it would be more convenient. Not once did anyone ask me to explain how it got lost or whether I had gone looking for it.

\n

That experience made me a real fan of DJI. Their customer service and technical support engineers were professional and clear throughout the whole process. I want to use that story to share what I think makes a good product experience.

\n

Good product experience is not just what people usually say: great interaction design, beautiful UI, easy to use, no bugs. Those matter, but what matters even more is this: when a user is in a tough spot, you give them something far better than they expected. Something so good that they get excited and tell their friends about it. That is what I consider truly good product experience, the kind that is good for business too. The only thing I worry about is that this culture of trust and simplicity gets taken advantage of by people trying to game the system. It’s something we all have to protect together.

\n

Two other experiences that stood out to me involved Ctrip.

\n

The first was three years ago during the Spring Festival. Tickets home were nearly impossible to get. They suggested I buy tickets for a few extra stops to guarantee I could board, and I was already grateful for that because nothing else had worked. But then, even better: I was at the movies that afternoon, feeling like everything was handled, when I got a call from an unknown number that I declined. Right after, a text came in saying they had found me a direct option that didn’t require the extra stops, and could I please go to the app to confirm. You could tell a real person had made that call and sent that message. It wasn’t the few dollars saved. It was the feeling that someone was genuinely working hard for me and delivering better than I had hoped. That is good experience.

\n

The second happened recently, during National Day. I had gotten two first-class seats but they weren’t together, pretty far apart. I had noted I was traveling with an 18-month-old. Then, the day before departure, Ctrip quietly swapped our seats. Just a simple notification: we found an open seat in your carriage and moved you both together. Another moment where someone gave me more than I expected.

\n

So if you are building a product, think about giving your users something far beyond what they expect in the moments when they really need it, rather than chasing clicks with tricks. When you do that, people will genuinely love your product and become your most loyal fans.

\n
\n

\n Buy me a coke 🥤\n

"},{"title":"263. Hardware Beauty","link":"https://weekly.tw93.fun/en/posts/263/","pubDate":"Mon, 06 Apr 2026 00:00:00 GMT","description":"\n

The cover photo is from a hardware toy I spent three days playing with at home during the holiday. I was soldering, applying glue, and debugging through a pile of components. I was almost at the final step when I burned the screen during testing. Now I am waiting for the replacement to arrive so I can keep going. Lots of fun.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

New Article

\n

What You Don’t Know About LLM Training: Principles, Paths, and New Practices
\nhttps://tw93.fun/2026-04-03/llm.html
\nThis is the longest article I have ever written. The good news is I finally got a handle on the basics of large model training. The gap between what I assumed I knew before and what I actually found was massive. I highly recommend this to anyone working in AI applications or anyone curious about AI. It should give you a clear picture without leaving you lost.
\n

\n

Product Releases

\n

Waza, My Engineer-Alter-Ego Skill Set
\nhttps://github.com/tw93/waza
\nI packaged my personal skills into something new called Waza. In Japanese, 技（わざ）means technique or skill, often used in martial arts. This is the first time I have released an open-source project with zero code, just markdown files. In the pre-AI era, for a programmer, that would have been embarrassing.

\n

When Superpowers came out, I installed it once and deleted it right away. Too heavy, not my thing. A lot of people kept telling me “You don’t know Superpowers? If you’re not using it you’re not with the times, it’s amazing.” Then I found gstack, which was better, but still felt like too much. I still wasn’t used to it. I wanted something simple and useful where I could clearly see what it was doing.

\n

So I built Waza the way I like it. For me, this set is enough. No need to mess with other skills. Not too many, not too few, just right. New iterations can be added over time.

\n

The 8 skills correspond to 8 abilities I think a good engineer in the AI era should have:

\n
    \n
  1. \n

    Think clearly. AI writes code fast, but if the direction is wrong, the faster you go the further off course you get. A good engineer questions the problem itself before touching any code, stress-tests the plan, and has a clear mental architecture before asking AI to execute. /think locks this habit in.

    \n
    2. \n
  2. \n

    Design well. Building a product is not just about making features work. AI-generated things tend to look the same. Good engineers have an aesthetic standard for what they deliver and a clear design direction. /design handles this.

    \n
    3. \n
  3. \n

    Debug systematically. AI fixing bugs most easily falls into a “try this, try that” loop. A good engineer diagnoses problems systematically, confirms the root cause before touching the code, and gets it right in one shot. I turned this habit into /hunt.

    \n
    4. \n
  4. \n

    Review before merging. AI-generated code needs human oversight even more. Check the diff before merging, auto-fix what can be auto-fixed, group the judgment calls together, and verify with evidence rather than gut feeling. That is /check.

    \n
    5. \n
  5. \n

    Read primary sources. Good engineers read original material, not second-hand summaries. Converting URLs or PDFs into clean Markdown and pulling it directly into the workflow is what /read does.

    \n
    6. \n
  6. \n

    Write clearly. No matter how technically strong you are, if you can’t explain it clearly, others won’t receive it. A good engineer can convey what they have learned and what they want to express to the right audience. /write helps you nail this step.

    \n
    7. \n
  7. \n

    Learn actively. Tech moves faster in the AI era. Entering an unfamiliar domain is not just skimming a few articles. It is collecting, digesting, outlining, drafting, refining, and publishing. Output drives learning. That entire flow is /learn.

    \n
    8. \n
  8. \n

    Maintain the toolchain. A good engineer does not only care about business code. The toolchain itself needs regular checkups. When something feels off with CLAUDE.md, rules, hooks, or MCP configs, run /health and find out what is wrong.

    \n\n
    9. \n
\n

Product Updates

\n

Kaku 0.9 is out and it is really good
\nhttps://github.com/tw93/kaku
\nA few fun features shipped in this version that should be genuinely helpful.

\n
    \n
  1. Natural language command generation: Type # <description> and press Enter, and the auto-generated command is injected back into the prompt.
    2. \n
  2. Option+Click to move the cursor: Click anywhere on the current line to move the cursor there.
    3. \n
  3. Window pinning: Pin the window to the front via the Window menu, and toggle it on or off anytime.
    4. \n
\n

\n

Trending Tools

\n

Claude HUD helps you track your Claude usage
\nhttps://github.com/jarrodwatts/claude-hud
\nIt is a little feature-heavy, but after some simple configuration it works well. Worth trying if you are curious. The code feels a bit complex, and when I have time I will probably simplify it myself. Minimalism is the goal.
\n

\n

A super minimal, AI-friendly Markdown doc generator
\nhttps://docmd.io
\nStumbled on docmd. It is a zero-config documentation generator built for developers. It converts Markdown into fast, clean static docs with automatic routing, built-in search, and context that AI can easily use.
\n

\n

Picked up a 140W charger and it is great
\nGot a 140W charger. Good size, finally free from my old 45W. Four ports, which makes it way more convenient on the go. The display showing real-time power output is a nice touch.

\n\n \n \n \n \n \n
\n \n \n \n \n \n
\n

Random Thoughts

\n

Let me share how I dive deep into a new technical domain in the AI era.

\n

Before AI, I mostly read books and went through every blog post from notable people in the field, both domestic and international, writing notes by hand. It was slow but genuinely fun. Learning WebGL back then felt like that. Getting a solid understanding of something might take half a year of free time. Slow, but happy.

\n

Now that AI is here, I still can’t stand those “summarize a hundred-year-old novel in 3 minutes” things online. I also dislike short-episode dramas and watching shows at 2x speed. I mostly still choose good things and take time with them.

\n

But recently while writing the “You Don’t Know Claude Code” and Agent series, outside of the parts I already understood, there were huge areas I wasn’t clear on. Luckily I had saved a lot of articles, and this was the perfect chance to clear the backlog, fully digest everything, and write it all out. I have always believed that what matters is not how much you read, how much you hear, or how much you take in. Most of that doesn’t really stick. What matters is how much you output. That is what becomes truly yours.

\n

A couple of weeks ago I started a deep challenge: studying the training pipeline of large language models and making sure even non-specialists could understand it. I explored for two weeks, and the experience is now ready to share. The article is basically done and should be coming out soon.

\n

I organize this learning process like writing code. Step one: collect high-quality material. Recent top papers in the field, blog posts from major model providers about their key releases, threads from model leads on X, recent courses from Stanford and similar schools, and classic “build an LLM from scratch” repos. These are my sources. I use tools to automate downloading everything, converting to Markdown, cleaning, and organizing it all into a structured repo for this research.

\n

For content I understand, I read it all through, delete the bad parts, and keep the good ones. For content I don’t understand, I use Claude to help me get it. The more complex parts I translate into Chinese and read that way. For code that can run locally, I run it. For code that can’t, I read the structure. Either way, I end up with a rough understanding of the technical principles. This phase usually cuts the original material by half.

\n

At this point you have a general picture of the field, so you can start writing an outline and figuring out which source material belongs with each section. All of it works well in Markdown. What do you want to say, or more accurately, what do you want your reader to know? Always remember: an article is written for its readers. You need to know your audience’s level. It is a lot like giving a presentation.

\n

Then comes the grind, which is also a review of everything you have covered. It feels a lot like cramming before an exam in college. You fill in each section completely, and what you end up with is a very long and somewhat rambling article.

\n

This is where AI really helps. You can ask it to remove the redundant parts and smooth out the disconnected bits, without changing your original meaning or your voice. You can also ask it to flag gaps and help fill them in. That process teaches you even more things you had missed.

\n

Once that is done, read through it yourself one more time, not AI. AI is just a tool here. Do not let it replace your brain, that defeats the whole point. Reading through yourself, you can keep adjusting and polishing. It feels a lot like testing your own code: fix issues, fix more issues. After reading it twice and feeling good about it, you can publish it for everyone to see.

\n

Some folks worry that nobody will read what they write, so they hold back or just don’t write at all. Honestly, if your content has real value, readers will come. Worry about quality, not the audience.

\n

That took 10 minutes to write. Done. Happy to hear how you learn new fields. The video below is a recording of the learning repo for the LLM training article I mentioned, the one coming out soon. It shows my “industrial-scale” way of learning. Kind of fun to look at.

\n

\n

\n Buy me a coke 🥤\n

"},{"title":"262. Lost My Drone","link":"https://weekly.tw93.fun/en/posts/262/","pubDate":"Mon, 30 Mar 2026 00:00:00 GMT","description":"\n

The cover photo is here in memory of my drone, which I finally lost. This was the last shot it ever took. Thankfully I have DJI Care Refresh, so I should be able to get a replacement for free.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

Product Updates

\n

Kaku released version 0.8
\nhttps://github.com/tw93/Kaku
\nThis release is called Fish 🐟. Most of the work in this round went into shell compatibility, tab behavior, and overall stability.
\nIt now has full fish shell bootstrap support, including Starship, Yazi, theme sync, and config handling. Tab management was also improved, with remembered last directories, isolated tabs for update and doctor, and a new option to show directory names only in tab titles.
\nOn top of that, it fixes a batch of issues around fast output and Claude Code viewport jumping, plus window hiding, link clicking, paste behavior, emoji width, SSH aliases, Cmd+Q crashes, and transparent rounded-corner rendering. Worth updating.
\n

\n

Mole released version 1.32
\nhttps://github.com/tw93/mole
\nThis version is called Rorqual 🐋, and there are quite a few updates again.
\nmo clean now fixes the long-skipped wallpaper proxy and Messages preview caches, and adds cache and log cleanup for PCSX2 and RPCS3. It also improves Python bytecode cache output, the Brave cleanup guard, Spotify playback detection, and the error handling around Service Worker cache cleanup.
\nBesides that, mo uninstall now filters out invisible background helper apps, the main menu shows more accurate Touch ID detection and a version shortcut, and the install flow now grabs sudo permission up front so you do not have to keep entering your password over and over.

\n

Pake released version 3.11
\nhttp://github.com/tw93/Pake
\nThis release is called Evolve 👻. It had been a while since the last update, and this one is mostly focused on bug fixes plus a few new features.
\nOn macOS, --install now supports one-command installation into /Applications. The new --new-window flag keeps popup and OAuth windows inside the app instead of constantly bouncing out to the system browser. It also adds --camera, --microphone, and --identifier for on-demand media permissions and custom Bundle IDs, which helps reduce conflicts between apps.
\nThere are also plenty of cross-platform fixes in this release, including Gemini download failures, parts of the ChatGPT UI disappearing after zooming, Windows icon copy errors, and crashes when clicking external links in macOS new-window mode. Overall it feels more stable.

\n

Trending Tools

\n

The 4 Claude MCPs I use the most
\nhttps://tinyfish.ai
\nThe first one is TinyFish MCP. I like it a lot because it lets Claude browse the web directly, fetch pages, do research, and return structured results instead of just a static answer. Lately I have been using it to collect AI news for this weekly, like pulling the most popular Hacker News items from the past few hours and turning them into a clean summary list. It saves a lot of time.
\nThe second is GitHub MCP. It makes everyday things like reading commits, tracing changes, and understanding a repository much smoother, without constantly switching between tools.
\nThe third is Figma MCP. You can inspect design files, check layout and spacing, and pull UI details directly into the conversation, which is very handy when you are aligning implementation with design.
\nThe fourth is Excalidraw MCP. This one is better for thinking through things, especially flows and system structure. When words are not enough, drawing it out is much faster.
\nThe last three are probably already familiar to many people. I also recorded a short video showing how TinyFish works in a real workflow.
\n

\n

I have really been enjoying the gstack skill lately
\nhttps://github.com/garrytan/gstack
\nI highly recommend trying it. It feels like having a solid team of specialists around you, covering roles like CEO, tech lead, design, QA, and security, all helping you reason through the code development process.
\n

\n

Random Looks

\n

Chinese Painting from the Yuan to the Qing is an excellent book
\nhttps://book.douban.com/subject/37156716/
\nThis book is really good. It is dense in the best way, and Wu Hung’s scholarship is seriously impressive. If you want an art history book to get started with, this is a good one.
\n

\n

A drone clip from the Yangjiapai hike
\nThis is exactly where I lost my drone, for your amusement. “Dear DJI customer, we are very sorry to hear that your aircraft has gone missing. Please rest assured that DJI will do its best to assist you. Your flyaway report has been successfully accepted. You may first refer to the Find My Drone guide and try to locate the aircraft.”
\n

\n

Random Thoughts

\n

Kill the Manual Programmer

\n

\"\"

\n

The title is adapted from a song I loved 12 years ago, “Kill That Shijiazhuang Man” by Omnipotent Youth Society. The scene they wrote about feels a little similar to what we are looking at now.

\n

I have not taken a bus in years. Last time I went to Prince Bay, the scenic area had traffic restrictions, so I had to park outside and take the free shuttle in.

\n

In the seat ahead of me, a little girl kept swiping through those AI-generated short videos. The visuals were rough, the content felt fake, and when she moved to the next one, it was somehow more of the same. She was completely absorbed. The strangest part was that every video had a huge number of likes. Watching that made me a little sad. I kept thinking, when my own kid grows up, will they also be surrounded by this kind of low-grade AI-made content from the start, to the point that it becomes hard to even find something genuinely beautiful?

\n

Once AI showed up, producing things suddenly became much easier. Making content got easier, and making software got easier too. In the past, if you wanted to build something, you had to spend real time on it, go back and forth, solve actual problems, and only then dare to ship it. Now a lot of those steps have been flattened. Writing something is easy, building a product is easy, you buy some tokens, ask AI, stitch together a workflow, throw on an interface, and pretty quickly you have something that runs.

\n

Today I also saw someone say they could recreate a Claude Code in two days. I both believe that and do not. In voice AI alone, dozens of products have appeared all at once, and a lot of them are actually pretty decent. Even Doubao is competing in that space now. I have also seen quite a few Claude Code wrapper clients lately, and honestly some of them are very usable.

\n

For programmers, a lot of things that used to require professional skill, a learning curve, and years of accumulation are quickly turning into abundant supply. In the future, the least scarce thing may be products that look like products. They work, they run, they look fine. You can only try to do them a bit faster, a bit better, or wrap one more layer around them and maybe there is still some value there. But that value will get matched by AI more and more easily.

\n

Not long ago I was having dinner with a colleague and we got onto an interesting topic. I told him that over the past year I have really enjoyed listening to cassette tapes, and that every song somehow feels more durable and more beautiful. Why did cassettes, CDs, TV shows, and even many old books often feel higher quality overall? The reason is actually simple: production and distribution used to be heavy. If you wanted to release an album, you first had to make the work good enough, and only then would it make sense to produce tens of thousands of tapes. Otherwise they would not sell, and the company probably would not back your next release. Publishing a book was similar. You could not just finish it casually and push it in front of a huge audience right away. Back then, the act of making something was already a filter.

\n

Now you can upload a song to a platform and that is it. You can post an article to a public account and that is it. Software is becoming similar after AI, and in some cases AI will even upload the code to GitHub for you, a place many people used to find intimidating, and even generate the CI that publishes the release for you. A lot of thresholds that once required long-term accumulation to cross have been filled in by tools, and so the world slowly gets flooded with things that are all kind of the same and kind of usable.

\n

The trouble is not just that quality drops. Over time, people’s sense of quality drops with it. The more rough things there are, and the wider they spread, plus the pressure to make money, the more our judgment gets pulled off course. Eventually what people get used to is fast stimulation, fast feedback, and fast satisfaction.

\n

When I think back to that little girl watching videos, that is the part that feels uncomfortable. She was not just watching a few rough clips. She may be growing up inside a world filled with lower-cost, higher-frequency, emptier things.

\n

Code is clearly entering the same phase now. In the future, ordinary beginners will be able to use AI to build products that satisfy their own needs. Product managers will be able to make things that used to require engineers working alongside them. So what exactly is left for real engineers to do? That is something we need to think about seriously.

\n

I have also heard that a lot of bosses at big internet companies are now staying up day and night vibe coding. In a single afternoon they can build a demo they personally consider usable, and some of them are deeply hooked on it. This could have a major effect on people doing frontline work. Once the boss gets a few flows working in code, the natural conclusion becomes: writing software is not that big a deal after all. Things that used to take six months, can they now be done in one? Things that used to need 100 people, can they now be done with 10? It is hard not to think about where that leads.

\n

There is still room for engineers to keep building products that are more usable and more efficient. But if we stop at that layer, the field will only get more crowded. More people can enter, and more people can ship something that looks convincing. The competition will get brutal.

\n

I suspect the real way forward is something closer to how singers and actors responded. Yes, they still release albums, but they also make concerts, stage productions, and live performances. Those are not things you can casually replace by putting a wrapper around something. They require organization, density of detail, and a sense of wholeness that only comes after long polishing, and they face the world directly.

\n

Looking ahead, software may move in that direction too. Everyone will be able to vibe code a product. Everyone will be able to make something that is more or less usable. What will really open up the gap later is still system capability, engineering depth, understanding of real scenarios, and all the things people do not notice at first glance but that ultimately determine whether a product has real weight.

\n

The faster the outside world moves, the less we can afford to lower our own standards for software along with it. Low-level supply will definitely keep increasing, but that does not mean we also have to become rough. The things that survive are usually the ones that feel smooth, comfortable, restrained, almost bug-free, the kind where you can tell the maker treated the work seriously.

\n

I am also thinking through my own next step. I still want to keep building open-source software that is useful, approachable, language-independent, and can earn tens of thousands of stars. I also want to keep playing with low-level rendering, terminals, editors, Rust, and related directions. Before AI, all of that felt very rewarding. After AI, though, once you have an idea, so much suddenly becomes easy that the meaning of it can start to feel less obvious.

\n

Maybe the next thing for me lives in a different dimension, a hardware-software product, or the kind of platform product that used to require thousands of people at a big company, or maybe something that breaks out of the current frame entirely. What exactly it is still needs more thought.

\n

Some of my products and content have already been slowly moving toward English, toward a bigger world. When everything here starts to feel more similar and more crowded, going outward may be one answer. A bigger market, more varied users, and higher expectations make it impossible to stay at the level of wrappers, speed, and timing alone. That pressure forces you to build something more solid, and it also forces you to think again about what you actually want to make.

\n

AI has made many things easier. But precisely because things are easier now, it has become harder to figure out what is truly worth doing and worth trading years of your life for. What to build may matter more than how quickly you can build something.

\n

\n Buy me a coke 🥤\n

"},{"title":"261. miss spring","link":"https://weekly.tw93.fun/en/posts/261/","pubDate":"Mon, 23 Mar 2026 00:00:00 GMT","description":"\n

The cover photo was taken looking up at the spring sky. Spring in Hangzhou is truly beautiful. I kind of hope summer doesn’t come too quickly—weather like this is incredibly comfortable.

\n
\n

Recording down-to-earth trending tech seen every week, published here after filtering. If you find it useful, feel free to subscribe to this weekly newsletter for update notifications.

\n
\n

Wrote a Long Article

\n

The Agent You Don’t Know: Principles, Architecture, and Engineering Practices
\nhttps://tw93.fun/en/2026-03-21/agent.html
\nAfter writing “The Claude Code You Don’t Know: Architecture, Governance, and Engineering Practices,” I realized my understanding of the underlying Agent mechanics wasn’t deep enough. Plus, our team has accumulated quite a bit of business implementation experience in the Agent direction, yet we’ve always lacked a systematic summary. So, I went through the materials, open-source implementations, and the code I wrote myself again, ultimately organizing it all into this article.
\n

\n

Product Updates

\n

Mole Released Version 1.31
\nhttps://github.com/tw93/mole
\nMole released version v1.31.0 over the weekend, codenamed Makima. It features faster performance and more accurate system status reporting. Huge thanks to all the contributors! I also made a video so everyone can feel the power of open source.
\n

\n

Trending Tools

\n

Get Inspired by These Projects Built with Claude
\nhttps://claude.com/resources/use-cases
\nDefinitely worth a look. It covers various use cases in daily work, from research, writing, programming, to analysis. The content is much more in-depth than I expected.
\n

\n

Highly Recommend This Service from Jina in the Agent Era
\nhttps://r.jina.ai
\nSometimes you need an AI to read the content of a live website, but often it can’t fetch it due to various reasons. You can try this service: just append the URL you need to fetch after it, and it will convert it into nicely formatted markdown for you, making it super convenient for AI to use.
\n

\n

Pi, This Minimalist Agent Framework, is Worth Getting to Know
\nhttps://github.com/badlogic/pi-mono
\nIt’s very small. The openclaw project was previously implemented based on this framework. It serves as a great entry point for understanding Agents.
\n

\n

Random Thoughts

\n

Try Buying Pre-made Ice Cubes This Summer
\nI had been debating whether to buy an ice maker, but since I’m the only one at home who likes drinking ice water, I felt the usage rate would be low and it would just take up space. Freezing ice cubes myself was also inconvenient—I’d usually realize I forgot to make them right when I wanted a drink. I found a great solution: just buy some pre-made ice cubes and keep them in the freezer. When you need them, just take them out. You can even use them directly to make Americanos in the summer. The cost-effectiveness is super high.
\n

\n

Got a Singapore HSBC Card
\nIf you already have HSBC accounts in mainland China and Hong Kong, you can ask your relationship manager to help you apply for a Singapore one. Although it kind of feels like a supermarket loyalty card. The registered mail didn’t arrive for three months; after a phone call, they remade it and it arrived via express delivery in a week.
\n

\n

\n Buy me a coke 🥤\n

"},{"title":"260. Prince Bay","link":"https://weekly.tw93.fun/en/posts/260/","pubDate":"Mon, 16 Mar 2026 00:00:00 GMT","description":"\n

Cover photo taken on Saturday when I took the kid to Prince Bay Park at West Lake. Originally wanted to see the tulips, but there were way too many people. I wouldn’t recommend going to join the crowds.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

Wrote a Long Article

\n

The Claude Code You Don’t Know: Architecture, Governance, and Engineering Practices
\nhttps://tw93.fun/en/2026-03-12/claude.html
\nRevolves around Context Management, Skills, Hooks, Subagents, Prompt Caching, and CLAUDE.md design. It focuses on how to make the collaboration process more stable and controllable, sharing best practices from an engineer’s technical perspective. Welcome to exchange ideas.
\n

\n

Product Updates

\n

Mole has released version 1.30
\nhttps://github.com/tw93/mole
\nI started writing Mole last November, and surprisingly, 30 versions have been released up to today. This update includes:

\n
    \n
  1. Strengthened orphan app data cleanup strategy. General orphan cleanup now uses a 30-day resting window.
    2. \n
  2. Optimized Application Support and project cache scanning logic in large directory scenarios, reducing the risk of stuttering, and converging the scanning scope to a safer root path.
    3. \n
  3. Strengthened LaunchServices refresh fallback logic, stabilized Homebrew uninstall and update paths, and reduced unnecessary sudo behaviors.\n\n
    4. \n
\n

Kaku released version 0.7
\nhttps://github.com/tw93/Kaku
\nI really like the transparent frosted effect in this release, you can give it a try. Updates are as follows:

\n
    \n
  1. Kaku will now automatically switch between dark and light modes along with macOS, and has optimized transparency rendering and Yazi theme synchronization experience.
    2. \n
  2. Added closing confirmation for tabs and panes, reworked the close overlay style, and added custom rounded scrollbars. Try kaku config.
    3. \n
  3. kaku ai now supports Antigravity model configuration, quota tracking, and background loading.\n\n
    4. \n
\n

Trending Tools

\n

Learning the principles of Claude Code-like systems
\nhttps://learn.shareai.run/en/
\nIt will guide you step-by-step from scratch to build a minimalist Agent similar to Claude Code, and explain each mechanism in detail. Worth a look.
\n

\n

RentAHuman: AI hiring humans to work
\nhttp://RentAHuman.ai
\nWhen an AI Agent encounters a task that cannot be completed online, it can post the job online and hire a real human to complete the task. Haha, quite interesting.
\n

\n

A fantastic interactive MicroGPT demo
\nhttps://growingswe.com/blog/microgpt
\nThis is a learning website based on Andrej Karpathy’s GPT implemented in about 200 lines of Python code, explaining how language models work in a visual way. Worth checking out.
\n

\n

A public OpenClaw exposure monitoring site
\nhttps://openclaw.allegro.earth
\nLists OpenClaw instances accessible over the network. In many cases, you can click into these instances and directly view what is running inside. Actually, a lot of people who don’t understand the technology are installing OpenClaw. Many things are very dangerous, and surprisingly, many belong to Alibaba, which is scary.
\n

\n

Random Looks

\n

My CodeX configuration, for your reference
\nModel: Fast GPT-5.4 High
\nPersonality: Pragmatic.
\nCustom Instructions:
\nAct like a high-performing senior engineer. Be concise, direct, and execution-focused.
\nPrefer simple, maintainable, production-friendly solutions. Write low-complexity code that is easy to read, debug, and modify.
\nDo not overengineer or add heavy abstractions, extra layers, or large dependencies for small features.
\nKeep APIs small, behavior explicit, and naming clear. Avoid cleverness unless it clearly improves the result.
\n

\n

Cooked 4 dishes on Sunday

\n\n \n \n \n \n \n \n \n \n
\n \n \n \n
\n \n \n \n
\n

\n Buy me a coke 🥤\n

"},{"title":"259. Jingshan from Above","link":"https://weekly.tw93.fun/en/posts/259/","pubDate":"Mon, 09 Mar 2026 00:00:00 GMT","description":"\n

Cover photo taken during a weekend trip to Jingshan Flower Sea with my drone. Currently only rapeseed flowers are blooming - the other flowers haven’t really opened yet. Flew the drone to maximum altitude for some photos and spotted quite a few nice views.

\n
\n

Recording down-to-earth trending tech I see every week, filtered and published here. Follow this weekly newsletter to get update notifications

\n
\n

Trending Tools

\n

MiaoYan recently got updated with CLI support
\nhttps://github.com/tw93/miaoyan

\n
    \n
  1. CLI support via miao command - list all notes, search, create new ones, and cat content from the terminal. Very practical for AI workflows.
    2. \n
  2. Apple notarization complete: No more “App is damaged” warnings or having to click “Open Anyway” in System Settings!
    3. \n
  3. Preview stability upgrade: Fixed occasional blank preview issues and enhanced recovery capabilities after WebContent process crashes.
    4. \n
  4. Editing experience optimization: Fixed input method issues in split-column mode, resolved system shortcut conflicts, and eliminated highlight flickering when switching notes.\n\n
    5. \n
\n

Pake released version 3.10
\nhttps://github.com/tw93/Pake

\n
    \n
  1. Multi-window support: New --multi-window parameter allows opening multiple windows in the same App instance. When enabled, macOS File menu (Cmd+N) and system tray menu will both show “New Window” entry. Restarting the App opens new windows instead of focusing existing ones.
    2. \n
  2. Internal link regex control: New --internal-url-regex parameter supports precise control over which URLs are treated as internal links via regex, as an alternative to the default same-domain judgment. Falls back to default logic on invalid regex.
    3. \n
  3. Windows ICO icon fix: Reordered multi-resolution ICO files to prioritize 256px icons, improving App icon display quality on Windows.
    4. \n
  4. DMG background image fix: Restored Retina metadata for macOS DMG background images and adjusted dimensions, fixing background display issues in CI builds.\n\n
    5. \n
\n

nanobot: A lighter OpenClaw form factor perfect for personal computers
\nhttps://github.com/HKUDS/nanobot
\nI currently have two nanobots running locally - one focused on code that helps me review issues, organize thoughts, and push technical solutions forward; another for life stuff handling daily tasks. Basically replaced my ChatBot habit from six months ago. Plus a cron job that keeps watching - if the service goes down it automatically restarts, and I use Amphetamine to keep my home computer always online. After running for a while, it becomes a stable part of your environment that doesn’t require you to consciously open, maintain, or fuss with it.

\n

Often when you’re halfway through coding or when you’re out and can’t conveniently open your computer, you can casually toss tasks to it to work on first. When you come back later, some of the prep work is already done. This experience is very practical and feels natural for engineers who prefer lightweight, simple, self-controllable solutions. If you don’t want to tinker, I’d actually recommend using the installer version - works out of the box. For those who want to add custom features like me, you can clone it locally and have nanobot optimize its own code and iterate on itself. Recently added quite a few fun features.
\n

\n

Amphetamine keeps your Mac awake
\nhttps://apps.apple.com/us/app/amphetamine/id937984704
\nWhen running things like OpenClaw or nanobot, you really don’t want the screen to sleep or even want it to keep running with the lid closed. Found this software - free and works great. Perfect for when you’re using a home Mac but want it to stay on with the screen off.
\n

\n

Maple browser bookmark tool latest update
\nhttps://github.com/tw93/Maple

\n
    \n
  1. New tab opening setting: Added “Open in new tab” option in settings, with hover tooltips disabled by default for a cleaner interface.
    2. \n
  2. Multi-language support: Optimized settings page styling and added multi-language support for better accessibility.
    3. \n
  3. File protocol support: Fixed issues with opening file protocol bookmarks (file://).
    4. \n
  4. Bug fixes: Fixed Bing date issues, sorting problems, and various UX improvements.\n\n
    5. \n
\n

Discovered a very modern VSCode theme: Islands Dark
\nhttps://github.com/bwya77/vscode-dark-islands
\nHas that new Apple system feel with glass arc effects, rounded corners - very modern looking, though you might not get used to it.
\n

\n

Readout: Visualize your Claude Code projects
\nhttps://readout.org
\nVisualizes your Claude Code environment in real-time. Shows AI, sessions, repos, costs, MCPs, ports, and more. Provides instant global search and complete session replay with timeline scrubbing. Runs locally, no account needed. Looking forward to its future development.
\n

\n

Random Finds

\n

Gaidihu floor drain core is excellent, worth trying
\nAfter buying the Gaidihu floor drain core that topped my “best purchases of the year” list and testing one, I bought another and replaced all the bathroom floor drains in my house. Very smooth drainage without clogging, easy to install. Highly recommended.
\n

\n

Haven’t eaten coconut meat in years, quite interesting
\nLearned how to open a coconut without a knife: First peel off the top, then you’ll see 3 faces. Gently press to find the spot that’s noticeably softer, then look for the hole there.

\n

As for cracking the shell open - use another coconut. Hold one in each hand and smash the three raised ridges against each other. Hit hard a few times and one will crack, then break it open. The coconut meat is very refreshing!

\n\n \n \n \n \n
\n \n \n \n
\n

Random Thoughts

\n

\"\"

\n

Last Friday I saw Tencent Tower installing OpenClaw company-wide. Quite thought-provoking - felt a bit like “The Great OpenClaw Leap Forward”.

\n

Recently many big tech companies have been frantically pushing frontline non-technical employees to install OpenClaw. There’s even a real 500 RMB on-site installation service online. Everyone’s desperately searching for use cases, demanding implementation, trying to prove this thing is too important to miss. The whole process gives me a strong sense of cyber-tech folding.

\n

Saw an interesting quote: “People who can’t even install OpenClaw, how would they use it?” Taking it a step further - if you haven’t even established basic usage, yet you’re expected to first create complete scenarios, deliver results, and prove value - that’s even harder.

\n

There are two things叠加 (stacked) behind this. One is illusion: many bosses have watched too many WeChat video clips, been repeatedly bombarded by exaggerated narratives and universal case studies, and really start hallucinating that this thing can do anything, connect anywhere, everyone should install it, and installing it should immediately produce output. The other is anxiety: everyone fears missing this wave, so they start using administrative actions to push adoption, using collective anxiety to replace real demand.

\n

So you see a strong contrast. On one side, slogans are huge - as if everyone must enter the AI-native era. On the other side, many people can’t even clearly articulate what things are worth handing over to it. This contrast will only grow stronger and increasingly absurd.

\n

Because tools never generate value through installation. Tools only generate value through task density, clear processes, and visible results. Without continuous tasks, without SOPs, without conditions for online completion, without clear inputs and outputs - even the strongest thing sitting there is just an icon. It won’t automatically grow scenarios just because it’s installed.

\n

So I’ve always felt OpenClaw isn’t for everyone.

\n

It suits commanders, solo entrepreneurs, and people who constantly have things they want to push forward, can break work into steps, and can complete many things online. Especially if you’ve used skills and tools, understand AI’s capability boundaries, can string processes together, build scenarios, and complete things step by step - then it’s very suitable.

\n

For me, this scenario comes naturally. Especially when there’s lots to push forward but I’m not home or at the office - out with just my phone or can’t conveniently open my computer - I’ll have my two nanobots check my open source product issues, produce technical solutions, then have another review and submit. All in one go. Lets me elegantly get things done during my morning commute. Really convenient.

\n

But for someone who normally has no work to complete outside, or who doesn’t even want to open their computer when they get home - how could you force scenarios to exist? Eating well and having fun is comfortable enough. No scenario means no scenario, really no need for anxiety.

\n

I think what’s most easily amplified in this wave isn’t capability gap - it’s scenario gap. People with scenarios will use it more smoothly, run faster, eventually feeling like they have multiple selves. People without scenarios will easily spin around in concepts, tutorials, case studies, and videos, ending up with nothing changed except having installed more software.

\n

Many people’s biggest problem today isn’t not having installed OpenClaw - it’s treating having installed a tool as having entered the AI era. The real watershed has always been in task understanding, process design, and result judgment. Do you actually have continuous problems to solve? Can you break problems down and hand them to the system? Can you judge whether results are correct? These determine whether you can truly extract value from AI.

\n

So no need for anxiety. Installing OpenClaw when you have no real use case doesn’t mean much.

\n

If you really want to experience where this generation of AI is strong, better spend $20 on Claude Code, or more interestingly get a ChatGPT subscription, use GPT 5.4 to handle something you truly find difficult - produce a solution, push execution forward, experience this simple, efficient, problem-solving process once. That’s way better than installing OpenClaw.

\n

OpenClaw suits people with scenarios, suits commanders, suits solo entrepreneurs, suits those who can SOP-ize, online-ize, and complete processes step by step. It’s certainly powerful, but it proves its power through completing work for you, not through being installed.

\n

What many people are installing today is OpenClaw. What’s more important to figure out first: What problem do I actually have that’s worth solving with AI?

\n

That question may be more important than installing anything.

\n

\n Buy me a coke 🥤\n

"}]}