Blog · Analysis

Installer field notes: an orange-book style teardown

August 21, 2026 · dshbase · rewritten field note

Rewritten from Sogou WeChat “全拆解 / 橙皮书” style coverage into installer-facing notes. Not a reprint of any book or WeChat body.

Reference / clue (public orange-book repo; related WeChat coverage via Sogou)

From “it” to “I”

Official docs explain how the harness is built. Field notes ask what happens after you install it: money, disk access, first stuck UI. Both matter; only one matches the panic at 2 a.m.

Dump config before you theorize

dsh --profile web --dump-default-config
dsh --profile web --dump-config

Defaults vs effective config is the fastest way to see which plugins and presets actually loaded.

Append-only session logs

Across modes, the event stream is meant to be reconstructible. If the model saw it, you should be able to replay it from the log. That is the audit story — not screenshots.

Create mode invents tools

Watching an agent add a tool mid-task is exciting. It is also a supply-chain event. Prefer verified plugins from the directory over mystery one-off generators.

PTC is not a free lunch

PTC (programmatic task control) is an orchestration mode, not a coupon code. Community write-ups sometimes show fixed overhead going up. Measure tokens and cache yourself — start with our cost guide and modes guide.

Listed on npm ≠ installed

Packages can exist on npm outside the default install closure. “I saw it on the registry” is not the same as “my profile loaded it.”

Stars vs verification

Popularity is not an install signal. Use audit failure classes and verified badges before you expand the attack surface.

All articles →