https://blog.margrop.net/en/tag/clawd-code/ Recent content in Clawd-Code on Margrop Blog Hugo en-US Tue, 31 Mar 2026 21:30:00 +0800 https://blog.margrop.net/en/post/clawd-code-architecture-quick-read/ Tue, 31 Mar 2026 21:30:00 +0800 https://blog.margrop.net/en/post/clawd-code-architecture-quick-read/ <p>The latest <code>margrop/clawd-code</code> codebase is no longer just a preserved source archive. It is now a very explicit <strong>Python-first porting workspace</strong>: <code>src/</code> is the active implementation surface, <code>tests/</code> is the verification layer, <code>archive/claude_code_ts_snapshot/</code> is an optional local archive, and <code>src/reference_data/</code> is the source of mirrored command and tool inventories.</p> <p>This short post answers one question only: <strong>how is the workspace organized right now?</strong></p> <p><img src="https://blog.margrop.net/post-images/clawd-code-quick-overview.svg" alt=""></p> https://blog.margrop.net/en/post/claude-code-daofa-tishu-source-code-analysis/ Tue, 31 Mar 2026 20:30:00 +0800 https://blog.margrop.net/en/post/claude-code-daofa-tishu-source-code-analysis/ <p>After reading the latest code in <code>margrop/clawd-code</code>, the main change is obvious: this repository is no longer just an archive of the leaked Claude Code tree. It is now a <strong>Python-first porting workspace</strong>. The tracked tree centers on <code>src/</code> as active implementation, <code>tests/</code> as verification, <code>archive/claude_code_ts_snapshot/</code> as an optional local archive, and <code>src/reference_data/</code> as the mirrored data source for commands, tools, and surface coverage.</p> <p>That changes the question. We are no longer asking only “what did the original source look like?” We are asking:</p> <ol> <li>can the old system be reorganized into a maintainable Python workspace?</li> <li>can commands, tools, sessions, permissions, and startup order be modeled explicitly?</li> <li>how much of the original surface is mirrored today?</li> <li>which parts are already runnable, and which parts are still skeletal?</li> </ol> <p>That is why I rewrote this post. The previous version still revolved around the leaked snapshot itself. This version needs to talk about the <strong>new engineering object</strong>: the rewrite workspace.</p> <p><img src="https://blog.margrop.net/post-images/clawd-code-architecture-2026.svg" alt=""></p>