Better Harness Tools, not merely storing the archive of leaked Claw Code
Important
Rust port is now in progress on the dev/rust branch and is expected to be merged into main today. The Rust implementation aims to deliver a faster, memory-safe harness runtime. Stay tuned — this will be the definitive version of the project.
If you find this work useful, consider sponsoring @emmarktech on GitHub to support continued open-source harness engineering research.
The Rust workspace under rust/ is the current systems-language port of the project.
It currently includes:
crates/api-client— API client with provider abstraction, OAuth, and streaming supportcrates/runtime— session state, compaction, MCP orchestration, prompt constructioncrates/tools— tool manifest definitions and execution frameworkcrates/commands— slash commands, skills discovery, and config inspectioncrates/plugins— plugin model, hook pipeline, and bundled pluginscrates/compat-harness— compatibility layer for upstream editor integrationcrates/claw-cli— interactive REPL, markdown rendering, and project bootstrap/init flows
Run the Rust build:
cd rust
cargo build --releaseBeing written
The main source tree is now Python-first.
src/contains the active Python porting workspacetests/verifies the current Python workspace- the exposed snapshot is no longer part of the tracked repository state
The current Python workspace is not yet a complete one-to-one replacement for the original system, but the primary implementation surface is now Python.
I originally studied the exposed codebase to understand its harness, tool wiring, and agent workflow. After spending more time with the legal and ethical questions—and after reading the essay linked below—I did not want the exposed snapshot itself to remain the main tracked source tree.
This repository now focuses on Python porting work instead.
.
├── src/ # Python porting workspace
│ ├── __init__.py
│ ├── commands.py
│ ├── main.py
│ ├── models.py
│ ├── port_manifest.py
│ ├── query_engine.py
│ ├── task.py
│ └── tools.py
├── rust/ # Rust port (claw CLI)
│ ├── crates/api/ # API client + streaming
│ ├── crates/runtime/ # Session, tools, MCP, config
│ ├── crates/claw-cli/ # Interactive CLI binary
│ ├── crates/plugins/ # Plugin system
│ ├── crates/commands/ # Slash commands
│ ├── crates/server/ # HTTP/SSE server (axum)
│ ├── crates/lsp/ # LSP client integration
│ └── crates/tools/ # Tool specs
├── tests/ # Python verification
├── assets/omx/ # OmX workflow screenshots
├── 2026-03-09-is-legal-the-same-as-legitimate-ai-reimplementation-and-the-erosion-of-copyleft.md
└── README.md
The new Python src/ tree currently provides:
port_manifest.py— summarizes the current Python workspace structuremodels.py— dataclasses for subsystems, modules, and backlog statecommands.py— Python-side command port metadatatools.py— Python-side tool port metadataquery_engine.py— renders a Python porting summary from the active workspacemain.py— a CLI entrypoint for manifest and summary output
For questions, discussions, or collaboration:
👉 Telegram: https://t.me/emmarktech
Feel free to reach out if you’re interested in:
- the architecture
- contributions
- ideas and improvements
- general discussions about AI systems
Render the Python porting summary:
python3 -m src.main summaryPrint the current Python workspace manifest:
python3 -m src.main manifestList the current Python modules:
python3 -m src.main subsystems --limit 16Run verification:
python3 -m unittest discover -s tests -vRun the parity audit against the local ignored archive (when present):
python3 -m src.main parity-auditInspect mirrored command/tool inventories:
python3 -m src.main commands --limit 10
python3 -m src.main tools --limit 10The port now mirrors the archived root-entry file surface, top-level subsystem names, and command/tool inventories much more closely than before. However, it is not yet a full runtime-equivalent replacement for the original TypeScript system; the Python tree still contains fewer executable runtime slices than the archived source.
See the chart at the top of this README.
- This repository does not claim ownership of the original Claw Code source material.
- This repository is not affiliated with, endorsed by, or maintained by the original authors.
