Claude 4.6 Sonnet vs Gemini 3.1 Pro

It is crazy that Qwen3.6 27B now matches Sonnet 4.6 on AA's Agentic Index, overtaking Gemini 3.1 Pro Preview, GPT 5.2 and 5.3 as well as MiniMax 2.7. It made gains across all three indices but the way the Coding Index works, I don't think the gains are as apparent as they should be. The Coding Index only uses Terminal Bench Hard and SciCode which are both strange choices. Cleary the training on the 3.6 models out now has focused on agentic use for OpenClaw/Hermes but it's interesting how close to frontier models such a small model can get. Qwen3.6 122B might be epic. . .

**Deepseek V4** will probably release this week. Since I've already posted quite a lot about it here and I'm very hyped about V4, **I've summarized all the leaks. Everything is just leaked, unconfirmed**! Of course, everything could be different. If you have any new information or updates, please post them here! If you have different views or a different opinion, write them down too.

# DeepSeek V4 - Release

The release was originally expected for mid-February, alongside Gemini 3.1 Pro. However, DeepSeek has been delayed – this is not unusual and has happened multiple times before. The new release strongly points to **March 3rd** (Lantern Festival / 元宵节), but it could also be later in the week. The Financial Times reported on February 28th that V4 is coming "next week," timed to coincide with China's "Two Sessions" (两会) starting March 4th. DeepSeek's release pattern shows that new models often drop on **Tuesdays**. A short technical report is expected to be published simultaneously, with a full engineering report following about a month later.

# DeepSeek Delay History

DeepSeek delays regularly. Here's the pattern:

|Model|Originally Expected|Actual Release|Delay|
|:-|:-|:-|:-|
|DeepSeek-R1|Lite Preview Nov 2024, Full Version Dec 2024|January 20, 2025|\~4-8 weeks|
|DeepSeek-R2|May 2025 (according to reports)|Never released – replaced by R1-0528 update|Cancelled|
|DeepSeek-V3.1|Early Summer 2025 (expected)|August 21, 2025|Several months|
|DeepSeek-V3.2|Fall 2025 (expected)|December 1, 2025 (V3.2-Exp: Sep 29)|Weeks|
|DeepSeek-V4|\~February 17, 2026|\~March 3, 2026?|\~2 weeks|

# Architecture & Specifications – What Can We Expect?

**All unconfirmed! Much of this has been leaked but could turn out differently!**

# V4 Flagship – Main Model

|Specification|DeepSeek V3/V3.2|DeepSeek V4 (Leaks)|
|:-|:-|:-|
|Total Parameters|671B–685B MoE|\~1 Trillion (1T) MoE|
|Active Parameters/Token|\~37B|\~32B (fewer despite a larger model!)|
|Context Window|128K (since Feb '26: 1M)|1 Million Tokens (native)|
|Architecture|MoE + MLA|MoE + MLA + Engram Memory + mHC + DSA Lightning|
|Multimodal|No (text only)|Yes – Text, Image, Video, Audio (native)|
|Expert Routing|Top-2/Top-4 from 256 experts|16 experts active per token (from hundreds)|
|Hardware Optimization|Nvidia H800/H20 (CUDA)|Huawei Ascend + Cambricon (Nvidia secondary!)|
|Training|14.8T Tokens, H800 GPUs|Trained on Nvidia, inference optimized for Huawei|
|License|\-|\-|
|Input Modalities|Text|Text, Image, Video, Audio|
|Output Modalities|Text|Text (Image/Video generation unclear)|
|Estimated Input Price|$0.28/M Tokens|\~$0.14/M Tokens|
|Estimated Output Price|$0.42/M Tokens|\~$0.28/M Tokens|

# New Architecture Features (all backed by papers)

* **Engram Conditional Memory** (Paper: arXiv:2601.07372, Jan 13, 2026): O(1) hash lookup for static knowledge directly in DRAM. Saves GPU computation. 75% dynamic reasoning / 25% static lookups. Needle-in-a-Haystack: 97% vs. 84.2% with standard architectures
* **Manifold-Constrained Hyper-Connections (mHC)**: Solves training stability at 1T+ parameters. Separate paper published in January 2026
* **DSA Lightning Indexer**: Builds on V3.2-Exp's DeepSeek Sparse Attention. Fast preprocessing for 1M-token contexts, \~50% less compute

# DeepSeek V4 Lite (Codename: "sealion-lite")

A lighter variant has leaked alongside the flagship. At least one inference provider is testing the model under strict NDA.

|Specification|V4 Lite (Leak)|
|:-|:-|
|Parameters|\~200 Billion|
|Context Window|1M Tokens (native)|
|Multimodal|Yes (native)|
|Engram Memory|No (according to 36kr, not integrated)|
|vs. V3.2|"Significantly better" than current Web/App|
|Non-Thinking vs. V3.2 Thinking|Non-Thinking mode surpasses V3.2 Thinking mode|
|Status|NDA testing at inference providers|

# SVG Code Leak Examples

* **Xbox Controller**: 54 lines of SVG – highly detailed and efficient
* **Pelican on a Bicycle**: 42 lines of SVG – multi-element scene

According to internal evaluations: V4 Lite outperforms DeepSeek V3.2, Claude Opus 4.6 AND Gemini 3.1 in code optimization and visual accuracy.

# Leaked Benchmarks (NOT verified!)

**⚠️ IMPORTANT: All benchmark numbers come from internal leaks. The "83.7% SWE-bench" graphic circulating on X has been confirmed as FAKE (denied by the Epoch AI/FrontierMath team). The numbers below are the more conservative, more frequently cited leaks.**

|Benchmark|V4 (Leak)|V3.2|V3.2-Exp|Claude Opus 4.6|GPT-5.3 Codex|Qwen 3.5|
|:-|:-|:-|:-|:-|:-|:-|
|HumanEval (Code Gen)|\~90%|–|–|\~88%|**\~93%**|–|
|SWE-bench Verified|**>80%**|\~73.1%|67.8%|80.8%|80.0%|76.4%|
|Needle-in-a-Haystack|97% (Engram)|–|–|–|–|–|
|MMLU-Pro|TBD|85.0|–|85.8|–|–|
|GPQA Diamond|TBD|82.4|–|91.3|–|–|
|AIME 2025|TBD|93.1|–|87.2|–|–|
|Codeforces Rating|TBD|2386|–|2100|–|–|
|BrowseComp|TBD|51.4-67.6|40.1|84.0|–|–|

# Huawei & Hardware – The Geopolitical Dimension

* **Reuters (Feb 25)**: DeepSeek deliberately denied Nvidia and AMD access to the V4 model
* **Huawei Ascend + Cambricon** have early access for inference optimization
* Training was done on Nvidia hardware (H800), but **inference** is optimized for Chinese chips
* For the open-source community on Nvidia GPUs: performance could be **suboptimal** at launch
* This is an unprecedented hardware bet for a frontier model

# Price Comparison (estimated)

|Model|Input/1M Tokens|Output/1M Tokens|
|:-|:-|:-|
|DeepSeek V4 (estimated)|**\~$0.14**|**\~$0.28**|
|DeepSeek V3.2|$0.28|$0.42|
|Kimi K2.5|$0.60|$3.00|
|Gemini 3.1 Pro|$2.00|$12.00|
|Claude Opus 4.6|$5.00|$25.00|

If correct: V4 would be **36x cheaper** than Claude Opus 4.6 on input and **89x cheaper** on output.

# Open Questions

* Does V4 actually generate images/videos or just understand them?
* Will Nvidia GPU users get an optimized version?
* When will the open-source weights be released?

**Sources**: Financial Times, Reuters, CNBC, awesomeagents.ai, nxcode.io, FlashMLA GitHub, r/LocalLLaMA, Geeky Gadgets, 36kr

**Edit 03.03.2026**

The chance that the model will be released this week is relatively high, but not today. It is assumed that Deepseek will be released between March 3 and 5 if it is not published within the next 5 hours today. It will come in the next few days, as it then deviates from the release pattern (in terms of time).

**Edit 03.03.2026 Part 2**

The situation is becoming increasingly heated and tense, with an extremely large number of leaks and sources currently emerging. Collecting them all and verifying their credibility would take a very long time. However, a release is expected this week, with Wednesday or Thursday being the most likely dates.

**Edit 03.03.2026 Part 3 – Evening Update**

March 3rd (Lantern Festival) has passed without a release. However, in Beijing it is currently the early morning of March 4th, meaning the Chinese workday hasn't even started yet. A release on March 4th is still very much possible, especially since China's "Two Sessions" (两会) begin today.

What happened today:

1. **V4 Lite is being silently updated in production.** AIBase reported today that DeepSeek quietly pushed a new V4 Lite version tagged "0302". Community testers report a massive quality jump in logic, code generation, and aesthetics – now reportedly on par with Claude Sonnet 4.6. This strongly suggests DeepSeek is actively fine-tuning V4 models right before the official launch. (Source: AIBase)
2. **36kr published a new article** titled "The Entire Village Anticipates DeepSeek to Join for Dinner" – confirming the entire Chinese tech industry is waiting for V4. (Source: 36kr)

**Edit 04.03.2026 – Why not today, why Thursday is THE day**

March 4 passed without a release – and that makes strategic sense.

**Why not today:**

* CPPCC opening day = all Chinese media focused on politics, V4 would've been buried
* Shanghai Composite dropped 0.98% to 4,082 (4-week low) – bad sentiment to release into
* Beijing evening release window (8-10 PM BJT) has passed

**Why Thursday March 5 is the perfect storm:**

* **NPC opens tomorrow morning** – Premier Li Qiang delivers Government Work Report with AI & tech as centerpiece of the new Five-Year Plan. Morning: politics declares AI a national priority → Evening: DeepSeek delivers the proof
* **BYD "disruptive technology" event same day** – DiPilot 5.0, Blade 2.0, DM 6.0 reveal. Global headline: "China showcases two AI breakthroughs in one day"
* **Market timing** – Shanghai closes 3 PM BJT, evening release gives markets overnight to digest, Friday opens with V4 hype
* **Developer weekend** – Thursday drop = Fri + Sat + Sun to test & benchmark

**Expected release window:**

|Release|Beijing Time|UTC|
|:-|:-|:-|
|R1 (Jan 2025)|\~10-11 PM|\~2-3 PM|
|V3.2 (Nov 2025)|\~12 AM|\~4 PM|
|**V4 (expected)**|**8-11 PM**|**12-3 PM**|

**If Thursday doesn't happen?**

* Friday = bad release day (weekend kills momentum, DeepSeek has never released on a Friday)
* Next window: Monday/Tuesday March 9-10
* But: silent V4 Lite "0302" production update + 36kr's "The Entire Village Anticipates DeepSeek" article suggest we're in final hours, not days

**Edit 05.03.2026**

It has to happen today. Deepseek Web was down for 40 minutes, but it hasn't been down for the last 30 days, and it was the same before the big launch of V3 and R1. In addition, today is the BYD event Deepseek Partner. It will happen in the next few hours, and if not, then Deepseek has missed the best window of opportunity they could ever have had.

**Edit 05.03.2026 Part 2**

**The model will not be released this week or probably next week. Although DeepSee v4 has been ready for a long time and there were really only a few minor issues left, the model would have been released last week or this week. Is there a major delay due to the government, because at the last minute they said that deepseek is not allowed to release the model as long as it does not run on Chinese hardware, but the model was trained on Nvidia, so such a restructuring naturally takes time, because the new technology in V4 was completely for Nvidia and not for Huawei, and I think we still know what happened with R2...**

**Edit 07.03.2026**

When will Deepseek be released? After all the leaks, news, and crisis status, Deepseek V4 will and must come and cannot end like R2. The Chinese government has gone too far with its AI and told the US that it no longer needs it, whereupon Trump, in order not to appear weak, wants to impose a ban that will allow him to control all chip trade (meaning no more chips to China).

However, BYD and China have praised Deepseek too much in recent days. If V4 ended up like R2 and didn't come out at all, China would look extremely foolish, which the government would never allow.

That's why I suspect that Deepseek will receive help from the Chinese government (in recent years, Deepseek's CEO has been in frequent talks with the government and has received support from it) and will no longer adhere to any release pattern, as Deepseek has already missed three good release windows. My guess is that they will release it when it is least expected, which could be this weekend. (V3.2 was released on Sunday) In order to weaken and expose Nvidia and the entire US market with new AI technology.

Deepseek waiting until Claude or other providers are ready is incorrect and highly unlikely. Deepseek has problems and needs to fix them before release. V4 is already 90% complete (Lite has been corrected several times and is said to be just as intelligent as Sonnet 4.6). We also know that Deepseek's CEO is a perfectionist and would never release a half-finished product or leave it unfinished, as was the case with the GLM-5 release

**🚨 UPDATE 11.03.2026 – 22:00 CET – V4 WEIGHTS SPOTTED**

Major development: Chinese quantization expert u/bdsqlsz (青龍聖者) on X was spotted uploading **DeepSeek-V4-INT8** model shards to HuggingFace with the caption "it is coming." The upload shows multiple `model-0...` shards, a `.gitattributes`, and a [`README.md`](http://README.md) — indicating a full model repo creation.

**Why this is significant:**

* u/bdsqlsz is a verified, well-known quantization specialist — not a random account
* INT8 quantization requires access to the **full original weights** first
* Historically, community quants appear **within hours** of official weight releases (V3: same day, R1: same day, V3.2: within 24h)
* This means the official FP8/BF16 weights either already exist on HuggingFace (possibly private/unlisted) or u/bdsqlsz has NDA access

**Full leaked specs now confirmed:**

* \~1 Trillion parameters (MoE), \~32B active per token
* 1M native context window
* Multimodal: text + vision + audio
* Huawei Ascend 910C optimized
* MIT License

**Previous delays explained:** Huawei Ascend inference optimization (only 80% Nvidia efficiency), Blackwell chip fingerprint removal, and CEO Liang Wenfeng's perfectionism. The 40-min web outage on March 5 was likely a deployment test.

**My prediction: Official release within 24-72 hours.** The weights exist. The upload is happening. Keep your monitors running.

⚠️ UPDATE 11.03 – Unverified leak: u/bdsqlsz posted V4-INT8 weight uploads on X. r/LocalLLaMA is split – top comment (193 upvotes) questions authenticity. The file structure looks technically correct and INT8 aligns with Huawei optimization rumors, but previous V4 benchmark leaks in February were confirmed fake. Treat with caution until official deepseek-ai repo appears on HuggingFace."

Will update when it drops. 🚀

https://preview.redd.it/vfmxgtb46vxg1.png?width=1915&format=png&auto=webp&s=9b7cedec52f05eefaf604699dca8246a259cf713

So my last post blew up, turns out a lot of people hit the same Claude blind-spots problem. Going deeper this time.

Quick recap. Been on the 20x Claude plan running Opus 4.6 / 4.7 exclusively for a while. Last week I tried Codex 5.5 and was shocked by how much Opus had been missing. Pairing them felt like the piece I'd been waiting for.

A week later I'm way past two agents. Current setup, all in tmux:

* 3x Codex CLI, each on a separate ChatGPT Plus account so reset windows don't collide
* Gemini 3.1 Pro Preview
* Kimi K2.6 + DeepSeek V4 Pro, both via OpenCode Go (way cheaper than API keys, and 3x limits on Kimi)

Built a `/work` command in Claude that handles four shapes: plan, implement, major bug, minor bug. For each one it builds a context pack, sends it to 3 reviewers in parallel, waits for consensus.

The thing that actually matters here is *lineage diversity*. Reviewers are picked as 1 Codex + 1 Gemini + 1 OpenCode. Same-family models share blind spots, three Codex sessions reviewing the same code is mostly an echo chamber. Need all three lineages to agree before the gate opens. If they don't, Claude revises and runs it again.

Before any merge, Claude fills out a 4 question checklist (coding principles, architecture drift, tests pass, reviewer consensus) and I pick merge / fix first / override with reason. Catches a lot of *"I think it's done"* moments.

Cost so far is basically $0 on top of the subscriptions I already had.

The thing I keep noticing: Opus by itself is great until it isn't, and the failures are silent. Code looks reasonable, tests pass, but there's a subtle bug or design drift that only shows up later. Having a different model family read the same code fresh catches a startling amount of it.

Happy to share the `/work` prompt and orchestrator if anyone wants to make it their own, let me know.

Edit: Check out [Chorus.codes](http://Chorus.codes) for the latest version of this repo.

Hey everyone, Kazuma here.

V7 is out. Go grab it: **GitHub:** [https://github.com/Arif-salah/Megumin-Suite](https://github.com/Arif-salah/Megumin-Suite)

Before I get into the fun stuff, I need to be real with you guys for a second.

# Real Talk First

I really don't like having to do this. I really don't. But Megumin Suite is a free project, it always has been, and it always will be, and it has been taking up a *huge* chunk of my time. Like, huge. I've got LTC address at the bottom of every post and every readme, and after all this time... basically nobody has ever donated. I am absolutely not guilt-tripping anybody, I promise. I get it. But I thought it was worth being at least a little bit upfront about the situation rather than just pretending it didn't matter.

Even if you genuinely can't afford to contribute financially, and that is absolutely okay, there is one thing that would help me out immensely: **an API key.** Running tests against multiple models is probably one of the biggest roadblocks that I currently face. Right now, I only have complete access to the Gemini 3.1. I can't test against Claude, I can't test against GPT, and sometimes I can't even test against DeepSeek because the server is swamped. If you have a key that you're not fully using and you'd be willing to let me use it that would genuinely help more than you know. DM me on Discord if you're open to it.

Okay. That's out of the way. Let's talk about the actual big update.

EDIT: sorry paypal hate me so no ko-fi link 😞. its ok just hear me rant about it.

**Crypto (LTC):** `LSjf1DczHxs3GEbkoMmi1UWH2GikmXDtis`

# The V7 Engine It Doesn't Feel Like AI Anymore

V7 is a ground-up rewrite. Not a tweak, not a patch. The entire ruleset was rebuilt with one goal: **make the AI stop acting like an assistant.**

If you've used any RP preset before including my older ones you've felt that invisible hand. The AI being too helpful. NPCs agreeing too fast. Conflicts resolving themselves in one turn because the model's base training say "be useful, wrap things up, make the user happy." V7 was designed to remove that instinct.

Here's what it actually does:

**Anti-Assistant Bias** The whole engine is built around the premise that the world does not give a fuck about you. NPCs fight back. They misinterpret you. They hold grudges. They get tired of you halfway through the conversation and just... leave. A good deed does not reset the relationship. An apology does not wipe out What you did. Forgiveness is a process which requires scenes, not words.

**The Knowledge Firewall.** This one is big. All NPCs are in information quarantine. They can only react to physical things they *see* and *hear*, not your internal narration and italicized thoughts. The PC's internal landscape is completely closed. If you write *"I feel pathetic"* as the narration but do not show it externally, nobody notices. The output will always depend on your model Less smart mean more errors.

**Cultural Anchoring.** The AI uses actual culture actual artists' names, actual brands, actual platforms, actual news headlines, actual memes. No more "the popular social media app" or "a famous pop song." In case of setting in 2025, the story should have a real headline on a TV in the background and some character hums a real song. It appears in the text like seasonings – here and there without being forced, not as a list of references but as a texture of a real world. *I used AI for the last sentence sue me*

**Narrative Drive.** The AI does not stop and wait for you. It will always try to derive the story if it start to feel DRY.

**Moral Complexity.** There are no archetypes. There is no good or bad People are grey.

This engine was designed with **DeepSeek V4** in mind, but it runs beautifully on Gemini 3.1 Pro/3 Flash and should work great on Claude and similar high-capability models. There are three variants:

* **V7 Core** The sweet spot in between. Cinematic, grounded, patient.
* **V7 Reality** Complete realism. No plot protection. The consequences have teeth. I personally like this one.
* **V7 Gentle** More subdued, more emotional. For stories that deserve their space.

# Memory Core Save 75% of Your Tokens

This is probably the most practically useful function of all. And honestly, it's insanely easy to use.

The issue here is that you're 400 messages deep in an RP, your context window is overloaded, and the AI starts hallucinating because it's drowning in old text that it can barely make sense of. Or you're throwing away money by sending 120k tokens per message to Claude because you don't want to lose continuity.

Well, Memory Core solves both of those problems. It is a 3-level system for managing your context:

* **Level 1 (Working Memory):** Recent messages. Standard stuff.
* **Level 2 (Short-term):** Old messages are automatically grouped together in 10 Messages chunks and AI-generated summaries of them are created in the background. No work done on your part.
* **Level 3 (Long-term Vault):** The oldest messages are moved to a Vector Database. When it comes time to bring them back, like mentioning a place you Visited 250 messages ago, it does so quietly.

The magical component: **Prompt Interceptor**. This physically deletes the old message from the prompt payload through SillyTavern's native mechanism. Old messages become grayed out in your chat interface You can still visit them and read them but it *won’t be sent to the API*. You aren’t paying for those messages. Your AI won’t have anything confusing to process. But data is preserved: it’s stored in the vault, waiting to be retrieved if necessary.

There's also a built-in **Regex Cleaner** that automatically strips useless tokens from the chat before they even hit the summary pipeline, so you're not wasting storage or context on formatting garbage, HTML artifacts, or other noise. One less thing to worry about.

Two types of search engines: **TF-IDF Keyword Matching**, which is fast and easy to set up, or **Semantic Embeddings** that leverage SillyTavern's native LanceDB integration.

The interface couldn’t be simpler. Head to Tab 10, turn on the switch, and hit "Apply & Extract Pending". That's all there is to it. Even a dummy could do it. And I mean that in the most affectionate way possible.

# NPC Bank Your Characters Have Faces Now

This one's just cool.

The NPC Bank automatically recognizes when the AI introduces a new significant character. It generate their description including name, age, appearance, backstory, personality, secret motivations, their close circle, etc., and stores a comprehensive dossier of them in a persistent database.

From then on, each time that NPC becomes relevant to your story, the system will seamlessly inject their dossier into the prompt. No need to keep track of who's who. The AI will simply *remember* the character because the system provides it with the right information at the right time.

And before you ask: no, it won't spam dossiers just because an NPC's name shows up in the World State block. There's a **Regex filter** specifically designed to prevent false positives, so the system only injects a dossier when the NPC is *actually relevant to the active scene*, not just because their name got mentioned in a status tracker somewhere.

And here's the best part: **AI Portrait.** With just one click, ComfyUI creates a portrait of that NPC entirely based on the AI's physical description of them. Your characters have faces now. And the whole process is fully automated you don't have to do anything. Also, if you use a multimodal model, the system can send the portrait back to the AI as a visual reference.

# Gemini Thinking Stop the Bleed

The Gemini Thinking toggle injects triple `<think>` tags that bypass Google's strict reasoning refusal filters. Clean separation the thinking stays in the thinking block, the prose stays in the prose.

>⚠️ **Important:** If you enable this, go to **AI Response Formatting → Reasoning**, activate **Auto-Parse**, and set the Prefix to `<think>` and Suffix to `</think>`. Otherwise SillyTavern won't know where the thinking ends.

# World State Tracker The Infoblock, But Better

Remember the old `info_block`? It's been completely rebuilt into a proper status dashboard. It now tracks:

* Current date, time, and weather
* PC's physical state (energy, injuries, mood indicators)
* NPC agendas and secrets
* Off-screen activity (what NPCs are doing when you're not looking)
* Unresolved narrative threads
* Current scene phase

It outputs as a collapsible HTML block at the end of each response. Which brings me to...

# NPC Inner Chatter The Spoiler Block

New block. Following every response, the AI generates an additional block that contains the *unfiltered thoughts* of all NPCs involved in the scene. Their true feelings behind the dialogue. The information they're hiding from you. The observations they made but didn't mention.

**My advice: don't look into it.** Both World State Tracker and the Inner Chatter blocks were designed to be read by the AI only, not you. These blocks may contain spoilers, NPC secrets, future story seeds. Once you take a look at them, you will know what's going to happen next and it will spoil the experience for you. Keep them collapsed and let the AI do its job.

However, if you want to I can't stop you.

# Other Cool Features

* **V7 Chain of Thought:** A hardcore 5-step reasoning audit from Ground Truth to Plot Engine, Scene Design, Active Draft, and Correction Loop. The AI needs to justify its actions before even beginning to write anything down. There's also a Lite mode that uses less tokens.
* **Engine Behavior Toggle:** Disable particular V7 behaviors one-by-one (OOC Protocol, Cultural Anchoring, Scene Choreography, and more) while retaining the overall logical consistency.
* **Dynamic Ban List:** Simply click "Analyze Chat" button and the AI will automatically detect sloppy phrases used by itself in the previous 50 messages and ban them for future generations.
* **Story Planner:** Automatically generates at least 10 plot milestones and inserts them into context for the AI to work towards achieving rather than simply responding to your latest message.
* **Prompt Preview:** View the exact text being sent to the API for debugging or just to know how your prompt payload actually looks like.

# Get It

Installation and everything else is on the GitHub. Watch the install video if you need it.

**GitHub:** [https://github.com/Arif-salah/Megumin-Suite](https://github.com/Arif-salah/Megumin-Suite)

**Install Video:** [https://www.youtube.com/watch?v=Q-iaz9mBFrA](https://www.youtube.com/watch?v=Q-iaz9mBFrA)

**Discord:** [https://discord.gg/HkxgN8r3jx](https://discord.gg/HkxgN8r3jx) DM: kazumaoniisan

If you're coming from V6, your profiles should migrate. If something breaks, hit me up on the Discord.

But seriously, if this tool helped you save some time, improved your rp sessions, or even impressed you at least a little bit, please consider donating even just one dollar to the Ko-fi. Or donate an API key. Or just star the repository and share the link somewhere. All of it helps. I will keep working on this project regardless, but it would be nice to know that I am not shouting into the void.

**Crypto (LTC):** `LSjf1DczHxs3GEbkoMmi1UWH2GikmXDtis`

Now if you'll excuse me, I'm going to sleep for approximately 47 hours.