thClaws/thClaws: README-based editorial guide

thClaws/thClaws describes itself in the README as "Open-source AI agent harness in native Rust , GUI, CLI, headless, and webapp from one binary. Multi-provider, MCP, skills, plugins, agent teams.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "thClaws 🦞", the README says: The open-source agent harness, in your terminal and on your desktop.. That establishes the project's stated boundary, not a production test.

The README's "Four surfaces, one engine" section gives a useful starting point for deciding whether the project fits: CLI REPL (thclaws --cli) , interactive terminal prompt for SSH, headless servers, or zero-GUI workflows.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Desktop GUI (thclaws) , native window with Terminal, Chat, Files, and optional Team tabs.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "See it work". The source evidence includes: Three tabs, one binary , captured from a live thClaws session looking at its own source.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: git clone https://github.com/thClaws/thClaws.git cd thClaws # One-shot: build frontend, then cargo build --features gui ./scripts/build.sh # macOS / Linux ./scripts/build.ps1 # Windows PowerShell # Verification suite (cargo fmt --check, clippy, tsc, cargo test) ./scripts/build.sh --check # Run cargo run --features gui # GUI cargo run -- --cli # CLI REPL cargo run -- -p "explain crates/core" # one-shot When the README contains no runnable command, this article does not invent one. Open its "See it work" section and confirm system dependencies, default ports, and first-run initialization before using a public server.