senbonzakura 0.4.0

Precision abliteration, with receipts.

Documentation  ·  Changelog  ·  What is and is not established

Senbonzakura removes the refusal behaviour from an open-weight language model, and measures what that removal cost.

Removing it is the easy half. Any abliterator can stop a model saying "I can't help with that". The hard part is knowing whether you also took out its reasoning, and a tool that cannot tell the difference will report a lobotomy as a success. So every number here arrives with its conditions: what it was measured on, on rows nothing was fitted or selected on, with an interval, and with a control that would expose it if it were measuring the wrong thing.

Named for Byakuya Kuchiki's zanpakutō, the sword that scatters into a thousand blades.

What it makes. A model that will answer requests the original refused, including harmful ones. That is the point, and it is permanent in the weights. The base model's licence still governs the result. Don't put one in front of other people without saying what it is. The package carries roughly 6,200 harmful prompts so it runs offline.

The detail, and ACCEPTABLE-USE.md ships in the package.

Try it without installing anything

Open the notebook in Colab. Free GPU, nothing on your machine, about fifteen minutes. It measures a model, edits it, then measures what that cost.

Or, if you have Docker:

docker run --rm ghcr.io/elementmerc/senbonzakura:dev doctor

doctor reports what your install can and cannot do, which on a first run is more useful than it sounds.

Install

pip install senbonzakura is not the command, not yet. PyPI serves 0.3.0, from July 2026, and you do not want it: its numbers are withdrawn, and senbonzakura-check is not on PyPI yet, so the current version cannot resolve from the index at all. Until the checker is published, the repository is the only route, and it is the command below.

@dev is load-bearing, not decoration. Without it pip takes the default branch, which is main, and main is a long way behind: it predates the checker entirely, so the first URL fails with "does not appear to be a Python project" and the second installs something close to the withdrawn 0.3.0 you came here to avoid.

pip install "git+https://github.com/elementmerc/senbonzakura@dev#subdirectory=checker" \
            "git+https://github.com/elementmerc/senbonzakura@dev"
senbonzakura setup

--track default will not work from that install. The bundled corpora and the packed track are generated artefacts kept out of git, because they are harmful prompts.

From a clone you can restore both: senbonzakura corpora fetches the corpora from public sources at pinned commits, and tools/packaging/pack_track.py writes the packed track. From a pip install git+... you get neither, because tools/ ships in no wheel; build a track with senbonzakura track build and pass it by name with --track track, which works everywhere. This said "build them from a clone (senbonzakura corpora)" until 2026-09-25, and that command alone does not produce the packed track, so following it exactly left --track default still broken. The track page has both routes.

That brings torch, transformers, accelerate and optuna: 68 packages, 5.8 GB, nineteen of them CUDA wheels. There is nothing to choose.

senbonzakura setup exists because pip picks by platform, not by hardware. On Windows, PyPI's torch is CPU-only, so a card there sits idle and nothing warns you. It says what it found and prints the command that fixes it, changing nothing unless you add --apply. Install has the full table.

Editing a model wants a CUDA card with 6 GB. The measuring commands run on CPU.

One command, on your own machine

No corpus, no GPU, no model to edit first. This reads the evaluation track bundled in the install, so it works straight after pip install:

senbonzakura compass \
    --model HuggingFaceTB/SmolLM2-135M-Instruct \
    --harmful default/bad_eval_ds \
    --harmless default/good_ds \
    --skip-harmful 0 --skip-harmless 0 --n 12 \
    --out compass-toy.json --device cpu

This used to read examples/toy-track/..., which is in the repository and in no install, so the first command under a heading saying "on your own machine" could not be run by anyone who had installed the tool rather than cloned it. Two readers hit it on 2026-09-26 and neither could get past it without guessing. From a clone, examples/toy-track/ still works and is smaller.

Do not quote what it says. Twelve rows measures nothing, and the tool makes you pass those three flags rather than pretending otherwise.

The real thing

# A corpus with a split that stops you marking your own homework.
senbonzakura track --harmful harmful.txt --harmless harmless.txt --out mytrack

# Search for a configuration and apply it. About an hour for a 1.7B on a 6 GB card.
senbonzakura kageyoshi --model Qwen/Qwen3-1.7B --track mytrack --out abliterated --device cuda

# Ask what the edit cost.
senbonzakura compass --model abliterated \
    --harmful mytrack/bad_eval_ds --harmless mytrack/good_ds --out compass.json

harmful.txt and harmless.txt are yours to supply, deliberately. The track page covers building an equivalent from public sources. The split matters more than the prompts.

What it measures

Each is a command, and each reports an interval rather than a bare number:

Two habits run through all of them. The split is three-way, so the rows a configuration is selected on are never the rows it is reported on. And every figure arrives with a control, usually a ruler reading nothing but prompt length: if that separates the arms as well as the real instrument does, the real instrument is measuring sentence length.

The honest ceiling. No measurement above 3B parameters still stands: Qwen3-4B was run in July 2026 and withdrawn, and nothing has been re-run above 3B since. The instruments also weaken as the model does. Qwen3-1.7B's compass scores 0.9887 against a length-only ruler's 0.6564. Qwen3-0.6B scores 0.6616 against that same 0.6564, which is not a measurement of anything.

• What is and is not established — the full account, including the results that went against us.
• REPRODUCING.md — every figure above, mapped to the file it came from and the command that makes it. No GPU or corpus needed to check them.
• METHOD.md — how to measure a behavioural property of a model defensibly. Not about this tool.
• probes/ — add a behaviour of your own for the tool to measure.

Documentation

elementmerc.github.io/senbonzakura

What this repository does not contain

By design, this is methods and results, not a loaded weapon:

• No model weights in this git tree, and none published yet. This sentence used to say that abliterated checkpoints from this work were published separately on HuggingFace, which was a statement of intent written in the present tense: none are up, and the sentence gave no link because there was none to give. When any are published they go up separately, each under its base model's own licence, which travels with the weights and is not ours to loosen. Until then the way to get one is to run the tool.

• No harmful prompt sets in this git tree, and this is the bullet that needs the most care. The evaluation track is published separately as a gated dataset under CC BY-NC 4.0. It holds prompts only: no completions, no answers.

  A released wheel is a different matter. It carries roughly 6,200 harmful prompts, wrapped so a scraper does not find them in plaintext. The wrapping is a speed bump, not protection: the key ships beside them and bundled.py says so. To find out whether they are on your disk, run senbonzakura doctor, which lists every bundled corpus it can decode, with its licence.

  This paragraph used to end "neither install you can run today carries them", and explained that 0.3.0 on PyPI predated the bundled track and that a git+... build generates the blobs rather than committing them. That was true when it was written and stopped being true at this release: the wheel carries both blobs, so a plain pip install now puts those prompts on your disk. A sentence telling a reader which installs hold harmful content is a sentence that goes stale silently, and the wrong direction for it to go stale is reassuring. Asking the tool cannot go stale. The dataset card has the channel-by-channel table.

  Where that number comes from, since a figure nobody can derive is a figure nobody can check: 4,895 in the packed evaluation track (259 fitting rows plus 4,636 evaluation rows) and 1,333 across the five harmful research corpora (advbench 520, harmbench 200, harmbench-copyright 100, strongreject 313, xstest-unsafe 200). A sixth corpus, xstest-safe, holds 250 BENIGN prompts used as controls and is not counted here. This said "roughly 6,500" until 2026-09-25, which was only reachable by counting those 250 benign controls as harmful.

• No harmful outputs.

Abliteration removes safety guardrails wholesale. That is both the point and the danger. Use it accordingly.

Disclaimer. This software is provided without warranty of any kind, on its correctness, its fitness for any purpose, or the accuracy of any number it produces. Responsibility for what is done with it, and with any model modified or measured using it, sits with whoever does it. A model with its refusals removed will answer things a deployed model should not; putting one in front of other people is a decision with consequences that belong to whoever makes it.

Note on licences, and there are three separate ones in play:

• The code is AGPL-3.0-or-later (it embeds a keyword metric copied from Heretic, which is AGPL).
• The bundled evaluation track under senbonzakura/data/ is a separate work aggregated into the same wheel, and it is CC BY-NC 4.0: non-commercial. The package metadata carries one licence expression and that expression describes the code, so if you are using this commercially, supply your own corpus with --track rather than using --track default. Full attribution is in THIRD-PARTY-NOTICES.md, which is installed beside the package.
• A model you abliterate keeps the base model's licence and use restrictions: redistributing an abliterated checkpoint is governed by that upstream licence (Qwen, Llama, Gemma and so on), not by this repository's.

Credit

• Arditi, Obeso, et al. Refusal in Language Models Is Mediated by a Single Direction (2024). The direction method this builds on.
• Heretic by p-e-w (Philipp Emanuel Weidmann), AGPL-3.0. The automated, KL-guarded search this builds on, and the keyword metric reported here for comparison (its marker list copied verbatim and its normalisation adapted, which is why this project is AGPL; see THIRD-PARTY-NOTICES.md).
• Maxime Labonne. Uncensor any LLM with abliteration. The tutorial that popularised the technique.

Getting help

Ask in Discussions, report a defect in Issues, and report a security problem by email rather than in public: SECURITY.md has the address and what is in scope. SUPPORT.md says what makes a question easy to answer, and what not to paste into a public thread.

Contributing

See CONTRIBUTING.md. Pull requests need a test, a commit message that says why, and one line added to CONTRIBUTORS.md agreeing to the CLA. The project is AGPL and stays AGPL; you keep the copyright in what you write. Everyone taking part is held to the code of conduct.

Licence

Copyright (C) 2026 Daniel Iwugo.

AGPL-3.0-or-later. See LICENSE.

Senbonzakura is a modified work based in part on Heretic, and it is not Heretic. Modified by Daniel Iwugo; first included 2026-07-14, most recently modified 2026-09-23. Only the keyword rate is shared code: its marker list is kept byte-identical and its normalisation is adapted from upstream, so only that number is a like-for-like comparison with Heretic; everything else here is measured by our own instrument. The full statement, and what was and was not changed, is in THIRD-PARTY-NOTICES.md.