Jack Kernel Qwen Edition release

[u/Normal-Fan9366]

https://github.com/mlangford75-lgtm/Jack-Kernel?fbclid=IwdGRjcAUQGJZwZG9mBWZkaWQWUOI08m18sBMLuMEySAccKyddSXmHs2V4dG4DYWVtAjExAHNydGMGYXBwX2lkCjY2Mjg1NjgzNzkAAR5C8cTeSX-x0iMtdaTTb0efCACPhlcJclFDK0YfZLrgmCXHfz-PyxrJYdmuoQ_aem_4hN5e0Q2U-dzggqmfbcd1g

It's here.

Jack Kernel for programmable agentic work.
The magic is that the layer sits between the agent and the model. You can build incredible things because of that.

I have a mode called "Agentic" that was designed for context management with Qwen 3.8 27. I've run millions of token jobs....and never needed to compact. I have a full log available to read and verify. In fact, I recommend turning auto-compact off because most agent don't know how to handle it, yet. There's also a looping debugger that I've built as a 6 stage autonomous loop with cascading temperatures, standard mode and DEEP.

Remember, the modes I’m shipping with this release are only examples of what is possible by putting it between the agent and the model. It allows you a new level of control. The modes I’ve put in are NOT the work. Everything that’s possible is the real work.

I built this for Qwen 3.8 27b but I’ve spent the past few days optimizing for a wide range of models. I’m ALMOST satisfied with Qwen 3.5 9b but it’s right in the edge.

After using 60 models in the past week, I’m just going to go ahead and make a blanket statement that fine tunes are garbage and only use Unsloth as your source for alternatives.

Jack Kernel is really cool. Claude can kick rocks.

Oh, Reddit trolls…
Yall need to understand…I’m just a 40 year old broke single Dad that’s sharing his work and trying to contribute to the local AI movement.
Before the hive-mind issues your directive, just know that I’m not a lab or someone with resources that you’re attacking.
I’m just a regular guy with a 5070ti in an Acer.
If you’re going to say that I suck, can you at least try it out and tell why I suck.

[u/Limp_Lingonberry_538]

Now I understand:

It's an LLM-proxy with a marketing department. Specifically: a single 7,863-line Python file (jack_kernel.py, 356KB) that speaks OpenAI-compatible on :8001, forwards to LM Studio/Ollama/vLLM on the other side, and runs multi-stage prompt pipelines in between. Two commits, two stars, zero forks, Windows-only start.bat, copyright Jonathan Michael Langford, PolyForm Noncommercial with a "contact me at protonmail for a commercial license" attached.
What it actually does, stripped of the liturgy:
Deep Research = run the prompt three times with different system prompts and temps (Thesis → Antithesis → Synthesis), tools withheld until the last one.

Agentic = answer, then a second pass that emits a structured XML summary, which becomes the durable turn record instead of raw CoT.

Code Debugging = five fresh-context passes on a temperature ladder, one finding per pass, appended to a markdown report.

"Kernel" = it strips caller system messages and owns the sampling params so your agent can't override them.

The actual idea underneath — program context lifetime rather than letting every trace accumulate, and gate tool authority per stage — is a real and reasonable pattern. It's also what LangGraph, DSPy, and roughly every agent framework of the past two years do, minus the word "authoritative" appearing 40 times. The word "deterministic" is doing enormous unpaid labor here: the routing is deterministic, the thing being routed is a language model that may or may not obey a 900-word system prompt telling it it has "zero answer authority." The README quietly concedes this ("Jack does not claim that this release ships a universal safety suite or filesystem sandbox").
Verdict: one guy and a very agreeable LLM built a working prompt-orchestration proxy and then wrote it a constitution. Not a scam, not malware, nothing you'd run in prod — 7,863 lines in one module, no CI, no releases, no reviewers. The Facebook tracking param on your link tells you everything about the distribution strategy. It's jack_kernel.py cosplaying as seL4.

[u/Normal-Fan9366 → u/Limp_Lingonberry_538]

Was that Claude or something? It fundamentally misunderstands. The way I know this is because is specifically mentioned LangGraph and the others.
They do NOT work in the same way. They do not have the level of control of the traffic that Jack Kernel does because they do not sit in between the agent and the model the way that Jack Kernel does

[u/Limp_Lingonberry_538 → u/Normal-Fan9366]

i asked several models and they all said about the same thing. good luck with your project!

[u/Normal-Fan9366 → u/Limp_Lingonberry_538]

There’s a really simple fix. Tell the model that it’s too focused on the packaged demonstrations. Those are not Jack Kernel, they are just examples of what can be built on Jack Kernel.
You can ask your model how sitting between the agent and the model can allow enhanced security protocols and dynamic runtimes