CometixCode

What it does

• File-for-file port: a TypeScript component maps to a Rust component, a hook to a hook; deviations are recorded in the source where they happen
• Builds on CometixTUI, an iocraft fork carrying the Ink-parity primitives the port needs: row-level diffing, event propagation, SIGCONT self-healing, IME cursor, bracketed paste, grid layout
• Same ripgrep shape as Claude Code — vendor/ripgrep archive next to the executable, source tree, then PATH; /doctor reports which one is in use and USE_BUILTIN_RIPGREP=0 forces the host binary
• just test runs the suite under cargo-nextest (one process per test) because process-wide state makes plain cargo test an invalid gate; the Windows cross-build statically links four C/asm dependencies (onig_sys, ring, tree-sitter, tree-sitter-bash) so the .exe needs no DLLs

When to use it

Rust developers who want to read a production-grade terminal UI architecture, and anyone curious how the Claude Code interface actually works — the companion ClaudeCodeRev analysis is what this port was derived from. It is also a working (if partial) native client: the interactive loop, tool execution, permissions, MCP and slash commands run today.

Getting started

git clone https://github.com/Haleclipse/CometixCode.git
cd CometixCode
cargo build --release
cargo run --release   # the binary is cometix

# Windows cross-compile (mingw-w64 toolchain on PATH):
rustup target add x86_64-pc-windows-gnu
cargo build --release --target x86_64-pc-windows-gnu

Things to know

Unofficial and not affiliated with Anthropic — “Claude” and “Claude Code” are Anthropic trademarks and nothing here is endorsed or supported by them. Work in progress: large parts of the interactive loop, tool execution, permissions, MCP and slash commands are implemented, other areas are partial, so expect gaps. AGPL-3.0-only.