CluxMate banner
r1c7 r1c7

CluxMate

AI community
SOURCE https://github.com/r1c7/CluxMate

Description

AI coding agent with one Python core and three front-ends — headless CLI, Textual TUI, and an Electron desktop. Works with any OpenAI-compatible API, with risk-tiered permissions, event-sourced replayable sessions, and a fail-closed OS-level sandbox.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

CluxMate

**An AI coding agent — one Python core, three front-ends.**

![Python](https://img.shields.io/badge/python-3.12+-blue.svg) ![License](https://img.shields.io/badge/license-MIT-green.svg) ![Platform](https://img.shields.io/badge/platform-Windows%20%7C%20macOS%20%7C%20Linux-blue.svg)

**English** · [中文文档](README.zh-CN.md)

What is CluxMate?

CluxMate is an AI coding agent that reads your codebase, plans changes, edits files, runs commands, and answers questions. A single Python core powers **three interchangeable front-ends**:

Front-end What you get
Headless CLI One-shot prompts for scripts, CI, and automation (cluxmate -p "...")
Textual TUI A full interactive terminal UI (cluxmate)
Electron desktop A polished GUI that drives the same core over JSON-RPC (stdio)

It speaks the **OpenAI-compatible API**, so it works with DeepSeek, Qwen, GLM, OpenAI, OpenRouter, Ollama, or any self-hosted endpoint using the same protocol — just point it at a `base_url`. No vendor lock-in.

Screenshots

CluxMate Textual TUI CluxMate Desktop

Highlights

  • One core, three front-ends — the headless CLI, the REPL, the Textual TUI, and the Electron desktop all drive the exact same agent loop. The desktop app is a shell around that core; the Python agent remains fully usable on its own.
  • No vendor lock-in — speaks any OpenAI-compatible API: DeepSeek, Qwen, GLM, OpenAI, OpenRouter, or a self-hosted endpoint. Configure multiple models and switch on the fly; provider failures never crash a turn, because timeouts, API errors, and network failures are translated into graceful, user-visible messages.
  • Event-sourced sessions, fully traceable — every session is an append-only event log; the model's message history is derived from it, never stored separate