Model Requests & Suggestions

#1
by IsValorum - opened

Suggest a model for a future handcrafted MiniPlus or NanoPlus release.

Please include:

  • Upstream model link
  • Intended use or strengths
  • Why it would be valuable at a MiniPlus or NanoPlus footprint

I will review requests based on demand, architecture, local-inference practicality, and whether the model would benefit from a custom tensor-by-tensor quantization.

IsValorum pinned discussion

CyberTiel

  1. Link: peculiar-ragdoll/Cyber-Tiel-Coder-35B-A3B-GGUF-MTP (https://huggingface.co/peculiar-ragdoll/Cyber-Tiel-Coder-35B-A3B-GGUF-MTP)
  2. Just like Tiel , agentic coding tasks, but stronger, less thinking(in my opinion) and uncensored
  3. Miniplus like what you did on Tiel

The MiniPlus V2.1 and NanoPlus quantizations are already underway; they will be available within an hour at most—follow me to get notified.

Wow
Thanks for your hard works and very fast reply, really impressive, this is the fastest model request i've seen on hf (or maybe you had already worked on this model from before :))

I will definitely check and test for if the Apex Miniplus CyberTiel work good too

Request for next model.
Reason: I've personally used k2 and it's the closest thing to match or exceed Qwen intelligence:
IFM/K2-Horizon-MoVA-36B-A4B

I personally tried the K2-Horizon, the smaller versions and that MoVA, and they didn't convince me because of the cost of the KV Cache.

I could barely get it to 8K context in Q4_0, not enough to properly test it, is it really any good?

For me, the fact that it had such an absurdly expensive KV cache was enough to completely rule it out. Did you guys test it in real-world use?

You were using Q4_0 KV?
How much VRAM on the rig?
I assume your models were tested on 24gb ram?

@IsValorum feel like working your quant magic on a Gemma4 or a Nemotron MoE?

ThinkingCap-NVIDIA-Nemotron-3.5-Lightning-30B-A3B (or original)

ThinkingCap-gemma-4-26B-A4B-it (or original or og-QAT or QAT abliterated)

My reasons for asking is that Gemma is great at languages (I use E4B to proof OCR output) and chatting, and Nemotron Lightning is (supposedly) a sipper where it comes to context memory use. I doubt either would touch the Tiels though where it comes to actual work, so I won't be surprised if you say nope. 😆

Tomorrow, ThinkingCap-gemma-4-26B-A4B-it will be quantized; Nemotron doesn't excel at anything.

Title: Request: Handcrafted APEX-I-MiniPlus V2.1 for Apex-35B-V1.0 (35B MoE / 3B active)


Hi IsValorum,

I'd like to request a handcrafted APEX-I-MiniPlus V2.1 quantization for Apex-35B-V1.0 by Apex Intelligence.

Full benchmark context

Apex-35B-V1.0 is a 35B MoE with ~3B active parameters, built on Qwen3.6-35B-A3B and further trained via a recursive self-improvement pipeline. The official card publishes a side-by-side table against Qwen3.6-35B-A3B (35B), Recursive Flint (40B), GLM-5.3 (753B), GLM-5.3-Flash (320B), and DeepSeek-V4.1-Flash (552B+196B).

Agentic / tool-use benchmarks:

Benchmark Apex-35B-V1.0 Qwen3.6-35B-A3B Recursive Flint GLM-5.3 (753B)
BrowseComp 69.4 42.1 23.2 80.9
BFCL V4 84.0 75.2 65.4 75.8
WideSearch 69.9 60.9 48.3 78.4
APEX-Agents 64.6 41.7 33.8 68.2
SWE-bench Pro v2 92.4 72.4 85.2 95.8
SWE-Atlas QnA 33.1 12.1 16.1 48.7

Research benchmarks:

Benchmark Apex-35B-V1.0 Qwen3.6-35B-A3B Recursive Flint GLM-5.3 (753B)
FrontierScience 40.0 21.7 5.0 30.7
PaperBench 60.9 45.8 ~29 42.5
SciCode (Main/Sub) 62.6 / 75.6 37.5 / 60.6 26.6 / 46.0 79.2 / 91.3
ASI-Bench 22.5 16.3 17.5 33.1

Sources: official HF model card benchmark table; PaperBench and FrontierScience comparisons also reported in Chinese coverage. GAIA is not reported in the official benchmark table, so it is omitted here rather than inferred.

The pattern is clear: Apex-35B-V1.0 is a 3B-active model that trades blows with 300B–750B class systems on agentic and research tasks—BrowseComp 69.4 against GLM-5.3's 80.9, SWE-bench Pro v2 92.4 against GLM-5.3's 95.8, FrontierScience 40.0 against GLM-5.3's 30.7. That margin is fragile. It lives or dies on routing stability and attention-gate fidelity.

Why this model specifically needs the handcrafted APEX-I treatment

A community GGUF release for Apex-35B-V1.0 already exists (Sangreal ICE), and its author documents a critical property: this base model is unusually sensitive to rounding. Even a plain Q8_0 sits roughly 0.015 KLD away from BF16 on code, which is higher than other 35B-A3B ladders at the same size. The ICE 2.0 12G tier still shows 76.4% same-top-1 on wiki and 86.6–87.9% on code—meaning even at 12 GB, roughly 1 in 5 wiki token distributions diverges from the BF16 master.

That sensitivity is not a reason to skip APEX-I. It is the reason APEX-I is the right treatment. The MiniPlus recipe protects exactly the tensors this model cannot afford to lose:

  • Routers gate_inp / gate_shexp: uncompressed F32 — zero routing drift
  • Output head: Q6_K
  • Attention gates: Q8_0
  • Core experts: IQ3_XXS / IQ3_S or above

Prior handcrafted APEX-I releases on comparable MoE architectures have held ΔPPL ≈ +0.05% to +1.08% while preserving those three failure points. For a model whose BrowseComp and SWE-bench Pro margins are the entire reason to run it locally instead of a generic 3B model, that armor is not optional.

Suggested starting preset

APEX-I-MiniPlus V2.1, following the standard armor above. Given the documented rounding sensitivity of this base model, I would especially value the handcrafted router/attention-gate treatment over any size-optimized generic tier. If the 35B/3B footprint allows, an APEX-I-MiniPlus V2 variant would also be valuable for users prioritizing edge fidelity.

Use case: local agentic coding, tool orchestration, and research-replication workflows—exactly where SWE-bench Pro v2's 92.4 and BrowseComp's 69.4 are the scores that justify the download.

Thanks for considering this request.

Both versions ready

https://huggingface.co/IsValorum/Apex-35B-V1.0-APEX-I-MiniPlus-V2.1-GGUF
https://huggingface.co/IsValorum/Apex-35B-V1.0-APEX-I-NanoPlus-V2.1-GGUF

Would you be open to consider quanting decision-model oriented finetunes of Gemma4 or Qwen3.x 27B/35B-A3B?

@IsValorum feel like working your quant magic on a Gemma4 or a Nemotron MoE?

ThinkingCap-NVIDIA-Nemotron-3.5-Lightning-30B-A3B (or original)

ThinkingCap-gemma-4-26B-A4B-it (or original or og-QAT or QAT abliterated)

My reasons for asking is that Gemma is great at languages (I use E4B to proof OCR output) and chatting, and Nemotron Lightning is (supposedly) a sipper where it comes to context memory use. I doubt either would touch the Tiels though where it comes to actual work, so I won't be surprised if you say nope. 😆

Both ready:

https://huggingface.co/IsValorum/ThinkingCap-Gemma-4-26B-A4B-it-APEX-I-MiniPlus-V2.1-GGUF
https://huggingface.co/IsValorum/ThinkingCap-Gemma-4-26B-A4B-it-APEX-I-NanoPlus-V2.1-GGUF

SmallAICreator/GRAFT-50B-A3B-GGUF

SmallAICreator/GRAFT-50B-A3B-GGUF

It's a generation prior to Qwen3.5, it's Qwen3 and it performs worse than Qwen3 30B A3B despite having more parameters (40B), pruning more than 40B of parameters from the original 80B left it lobotomized.

Furthermore, there are no BF16s or safetensors anywhere; only a Q4_K_M was uploaded.

DavidAU/Qwen3.8-40B-Ultimate-Heretic-Uncensored

ItachiSan/LiquidCode-2.5-24B-A2B
based on LiquidAI/LFM2.5-24B-A2B, i already use your LFM2.5-24B-A2B-APEX-I-MiniPlus-V2.1, which is great, and the fastest model on my pc, a coding variant would be awesome .

Sign up or log in to comment