explaingit

lynote-ai/humanize-text-zh

12PythonAudience · developerComplexity · 4/5ActiveLicenseSetup · hard

TLDR

Python toolkit that rewrites AI-generated text to read as human-written using four methods: translation chains, multi-round LLM rewrites, detector-guided loops, and ensemble translation.

Mindmap

mindmap
  root((humanize-text-zh))
    Inputs
      AI generated text
      Chinese or English source
      Detector models
    Outputs
      Rewritten text
      Detector scores
      HTTP API responses
    Use Cases
      Translation chain rewriting
      Multi-round LLM rewriting
      Detector-guided refinement
      Ensemble neural rewriting
    Tech Stack
      Python
      DeepSeek API
      Google Translate
      Docker Compose
      GPU

Things people build with this

USE CASE 1

Rewrite AI-generated Chinese essays into a more human style using a translation chain

USE CASE 2

Run a closed-loop rewriter that scores against four AI text detectors and rewrites paragraphs that fail

USE CASE 3

Self-host the HTTP API on port 8000 via Docker Compose and call it from another app

USE CASE 4

Study how each of the four humanization methods works as a building block

Tech stack

PythonDeepSeekDockerPyTorchGPU

Getting it running

Difficulty · hard Time to first run · 1h+

The detector-guided method needs local detection models and a GPU, plus a DeepSeek API key for the LLM rewriting method.

MIT license, you can use, copy, modify, and redistribute the code commercially as long as you keep the copyright notice.

In plain English

humanize-text-zh is an open source Python toolkit, written mostly in Chinese, that rewrites AI generated text so it reads as if a person wrote it. The README presents it as a research and learning project for people who want to see how AI humanization techniques actually work, and it ships four separate methods rather than a single hidden pipeline. The same authors also run a paid web product called Lynote.ai, and the README is upfront that the open source code is the building blocks while the hosted service mixes them together for end users. The first method is a chain of machine translations through distant languages, for example English to Chinese to Japanese to Finnish and back to English. The structural differences between those languages tend to reshape sentences. The README lists Google Translate, Niutrans, MyMemory and Apertium as the engines it can call, and notes that very long academic text can lose technical terms when too many translation hops are used. The second method is multi round rewriting with a large language model. It uses the DeepSeek API at a high temperature (1.1 to 1.3) and a burst oriented prompt to vary sentence length and word choice over two or three passes. The README warns that each extra pass can drift further from the original meaning. The third method is a closed loop where the text is rewritten, then scored by four AI text detectors at once (Binoculars on GPT-2, a RoBERTa classifier, statistical features, and diversity metrics), and any paragraph that still trips a detector is rewritten again. Document level rewriting feeds into sentence level rewriting and then into rule based cleanup, including replacing about thirty common AI English words and eleven common Chinese AI phrases. The README says this method needs local detection models and a GPU. The fourth method blends outputs from several neural translation engines in a single pass to avoid any single model's fingerprint. The project ships under the MIT license with a pip install path and a docker compose path that exposes an HTTP API on port 8000.

Copy-paste prompts

Prompt 1
Run humanize-text-zh in Docker Compose and call the port 8000 API with a sample Chinese paragraph
Prompt 2
Configure humanize-text-zh to use the DeepSeek API at temperature 1.2 for the multi-round rewriting method
Prompt 3
Help me set up the local detector models in humanize-text-zh for the closed-loop method on a single GPU
Prompt 4
Compare the translation-chain method and the ensemble neural method in humanize-text-zh for English academic text
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.