Archify has the agent write a typed JSON IR and lets a deterministic compiler turn it into a self-contained HTML artifact. I read the repository end to end and built four diagrams with it, watching what the validator refuses, why deliver, visual-check, and human review are kept apart, and what changes when this blog’s own mermaid is ported over.
I booted DeepSeek Harness with a single npx command and no API key, dumped its 145-row boot tree with --dump-config, and edited the patch layer by hand. The web profile ships with every model-facing tool switched off, and the reason turns out to be interesting. I also walked straight into the trap where patching a row config silently kills a CLI flag.
WebMCP is a W3C Community Group proposal in which a web page registers JavaScript functions and HTML forms as "tools" on document.modelContext, and the browser mediates those tools to the user's agent. This article lays out the imperative and declarative APIs and the boundaries the browser guarantees, straight from the spec, then calls real tools with Chrome 152 and agent-browser 0.36 to see how it differs from accessibility-tree automation.
What CO₂e means, how much CO₂ has built up in the air, how much of the 1.5 °C budget is left, and how big a tonne really is, shown in four 3D visuals instead of paragraphs.
DeepSeek Harness (dsh) turns the model adapter, the tool registry, the session log, and even the agent loop into Cordis plugins, then assembles the product by stacking patch layers on top of an empty tree. Two weeks after release it passed 200k GitHub stars. This is a source-level analysis of its kernel (Cordis), profile and bundle composition, the rule that the session log is the source of truth, capability seams, self-modification tools, and the way it runs Claude Code and Codex as subagents.