Following up on the previous post [From Fydetab Duo to HP Chromebook X11], I have been using the HP Chromebook X11 for a while. The overall experience is quite good, but I encountered two annoying bugs. Here I record the solutions.

It’s been barely a month since I wrote [The Perplexity of Modern Laptop and Tablet Choices], and here I am again.

That’s right — the same person who confidently declared “I’ll stick with the Fydetab Duo for now” at the end of that article is now sitting in front of an HP Chromebook X11 typing these words.

The essence of human nature is “it smells so good” (after swearing off something). My essence is tinkering.

Good news — the new company also provides laptops, and I got a Lenovo Xiaoxin 14 Pro with 32GB of RAM, the best-spec work computer I’ve had in 8 years.

The bad news is it has a glossy screen, and the office lights are so bright that the glare hurts my eyes. Luckily I also got a monitor, so I just use the external display (too bad the OLED has better colors…).

I maintain a package channel on prefix.dev to distribute some self-built packages. Since I’ve been busy with work recently, I haven’t looked after it for a while. Today I checked and noticed that the Actions had mysteriously stopped running… So I looked into the reason and decided to document a few other issues as well.

Today I came across an article from Qubit reporting that Anthropic just released Claude Managed Agents and already got an “open-source alternative” — this project is called Multica. I started using this project last week, so I did some digging.

Lately I’ve been deeply conflicted in my device selection, and after considering many devices, I have some thoughts I need to get off my chest.

Opencode has significantly improved my efficiency in development and bug fixing. However, in real work, I often need to maintain multiple projects simultaneously or handle development across several different directions. This means one person needs to manage and work on multiple branches at once. In such cases, manually switching branches, launching Opencode, confirming changes, testing, merging, and testing again can be quite tedious…

That’s why I’ve been looking for a task board tool where I can assign and track tasks through issues, letting Agents handle initial work while I focus on testing and reviewing code. Today I’m introducing Multica (https://multica.ai/), an open-source AI-native task management platform that aims to turn coding agents into real team members. Simply put, it allows you to collaborate with AI Agents the same way you would collaborate with human engineers.

With the global hype around OpenClaw, I’ve once again pondered a bit: is the current agent frenzy really because AGI has arrived? I naturally don’t think so.

New tools are always like this: the good parts are amazing, but the unfinished parts can be a headache. Recently, I tried to set up an automated build system using pixi and rattler‑build to regularly package and upload opencode to prefix.dev. The whole process took about 6 hours, during which I encountered quite a few unexpected issues.

Last time I successfully packaged my own program, so I wanted to try something else. Recently opencode has been extremely popular, and I’ve been using it too. Since it’s not yet available on conda, I decided to package it.