Claude-Code on Margrop Blog

Couldn’t Get the GLM Coding Plan? Volcengine’s ¥9.9 Offer Can Drop to About ¥9.4 with an Invitation

Sat, 11 Jul 2026 03:20:00 +0800

Short answer

If the GLM Coding Plan is unavailable when you need it, refreshing the purchase page is not your only option. Volcengine Ark currently advertises the Coding Plan Lite subscription at ¥9.9 per month for the first two months. The same page lists a regular monthly price of ¥40, making the introductory price roughly 25% of the regular price, or “2.5 zhe” in Chinese discount terminology. The plan page also lists GLM-5.2 and says selected popular models receive a temporary four-times quota boost.

Read the fine print before buying: ¥9.9 is not a permanent price, the third month returns to the displayed ¥40 monthly rate, and Coding Plan quota is intended for supported coding tools rather than arbitrary general-purpose API traffic. This article and its screenshots were prepared on July 11, 2026. The official campaign page displayed an end date of August 7, 2026; always trust the live checkout page if the rules change.

Stop Hunting for YOLO Flags: One Launcher for 6 AI Agent Tools

Mon, 06 Jul 2026 09:50:00 +0800

Short version

In AI Agent tools, yolo does not mean “the model is smarter.” It means “ask me fewer questions.” It reduces or skips approval prompts so the Agent can run more like an unattended automation script. The annoying part is that every tool names this differently. Codex exposes a dangerous approval-and-sandbox bypass. Claude Code has a dangerous permission-skip mode and a permission mode. Gemini CLI and Qwen Code use --approval-mode=yolo. OpenCode uses --auto plus permission rules. Aider uses --yes-always.

My recommendation is not to overwrite codex, claude, or gemini with risky aliases. Install an explicit agent-yolo launcher instead. When you really want high autonomy, type agent-yolo codex, agent-yolo claude, or agent-yolo gemini. This article provides Windows 11, Ubuntu 26.04, and macOS 26 scripts. They do not depend on third-party services, do not install missing Agent tools, and do not contain private addresses, full computer names, private domains, tokens, or keys.

The Markdown Throne Falls: When AI Agents Step Out of the Chat Box, HTML Becomes the New Answer

Wed, 10 Jun 2026 10:00:00 +0800

If 2023 was the “chatbox era” of ChatGPT and Markdown, then 2026 is heralding the arrival of a new phase: AI no longer merely “answers” you—it is set to “take over” your interface. As Agents begin directly controlling browsers, operating SaaS, and building interactive application prototypes, Markdown—long the de facto standard for LLM output, that elegant format prized for its simplicity, readability, and token-friendliness—is rapidly revealing its fatal shortcoming as the “last mile.” HTML, not Markdown, is becoming the new answer for next-generation Agentic output.

Claude Code Upgrade Broke Every Model? Before You Rotate Keys, Check the Compatibility Gateway

Fri, 29 May 2026 15:30:00 +0800

The short version

After a Claude Code upgrade, every model call failed with the same error: API Error: 400 invalid params, chat content has invalid message role: system (2013). At first glance this looks like a bad API key, a dead model, an exhausted account, a broken proxy, or a provider-wide outage. The root cause was different: a newer Claude Code request shape crossed an Anthropic-compatible model gateway that had not caught up with the client-side protocol behavior. The gateway, or a downstream chat validation layer behind it, rejected a system role in a place where it did not expect one.

The practical fix was not to randomly reinstall things. I reproduced the failure with the smallest possible prompt, tested adjacent Claude Code versions, and found the last known good version. 2.1.150 returned OK; 2.1.154 and 2.1.156 reproduced the 400. Pinning the global Claude Code installation back to 2.1.150 restored the existing provider path.

This post is a troubleshooting write-up for a local Claude Code environment. The fix itself was small, but the incident is useful because it shows a pattern that is becoming common in AI agent tooling: the CLI, environment settings, model gateway, API compatibility layer, and actual model backend are often separate moving pieces. When one layer changes its request structure, the terminal may only show a vague 400.

All private details have been removed. This article does not include real internal addresses, usernames, tokens, private provider names, local absolute paths, or private service domains. Configuration examples use placeholders such as <PLACEHOLDER>, <MODEL_GATEWAY>, and <MODEL_NAME>. The goal is to document a reusable debugging method, not to expose a specific environment.

Clawd Code Quick Architecture Read: One Page to Understand the Python-First Rewrite Workspace

Tue, 31 Mar 2026 21:30:00 +0800

The latest margrop/clawd-code codebase is no longer just a preserved source archive. It is now a very explicit Python-first porting workspace: src/ is the active implementation surface, tests/ is the verification layer, archive/claude_code_ts_snapshot/ is an optional local archive, and src/reference_data/ is the source of mirrored command and tool inventories.

This short post answers one question only: how is the workspace organized right now?

Clawd Code Latest Code Analysis: How a Python-First Claude Code Rewrite Organizes Commands, Tools, Sessions, and Audit

Tue, 31 Mar 2026 20:30:00 +0800

After reading the latest code in margrop/clawd-code, the main change is obvious: this repository is no longer just an archive of the leaked Claude Code tree. It is now a Python-first porting workspace. The tracked tree centers on src/ as active implementation, tests/ as verification, archive/claude_code_ts_snapshot/ as an optional local archive, and src/reference_data/ as the mirrored data source for commands, tools, and surface coverage.

That changes the question. We are no longer asking only “what did the original source look like?” We are asking:

can the old system be reorganized into a maintainable Python workspace?
can commands, tools, sessions, permissions, and startup order be modeled explicitly?
how much of the original surface is mirrored today?
which parts are already runnable, and which parts are still skeletal?

That is why I rewrote this post. The previous version still revolved around the leaked snapshot itself. This version needs to talk about the new engineering object: the rewrite workspace.