About this video
Your local AI is probably better than you think, but only if you stop treating it like a chatbot and start treating it like an engineer. In this video, I dive into the latest DS4 update which brings official DeepSeek 0731 support to the repo. We test the new hybrid quantisation and put my "Big Model Spec" theory to the test. Key Takeaways: - Official DeepSeek 0731 integration in DS4 with hybrid Q2/Q4 quantisation. - Why you must run 'make' after your git pull to avoid configuration errors. - The workflow of using Claude Opus for specs and DeepSeek for implementation. - Real-world performance stats: 23 tokens per second on local hardware. - How to build a functional OCR app with a single prompt.
The Local AI Revolution: DeepSeek 0731 on DS4
Most developers are still wasting money on API tokens for tasks that their own hardware could handle with more precision and zero privacy risks. The latest update to the Dwarf Star (DS4) repository has officially integrated the DeepSeek 0731 quantisations, and the results are frankly staggering for anyone serious about local LLMs.
The Hybrid Advantage
The new implementation is not just a standard shrink. We are looking at a sophisticated hybrid quantisation where the majority of the model runs at Q2, but the final six layers are preserved at Q4. This creates a model that fits within the 90GB to 100GB range while maintaining a level of reasoning that rivals much larger proprietary systems.
The Spec and Implement Strategy
One of the most effective workflows I have discovered is the "Big Spec" approach. I used Claude Opus on high mode to draft a comprehensive technical specification for a document scanning application. Instead of asking the local model to brainstorm and code simultaneously, I fed this high-level blueprint into the local DeepSeek 0731 model.
The result was a fully functional OCR application built from a single prompt. While it took nearly three hours to process the entire instruction set, the local machine averaged 23 tokens per second. This is more than enough for a background development process that does not cost a penny in subscription fees.
Key Technical Lessons
If you are updating your local environment today, remember that a simple git pull is not enough. You must run the make command again to ensure all files are correctly rebundled. Furthermore, if you encounter issues with the model thinking indefinitely, ensure your reasoning mode is set to max in your configuration.
Local AI is no longer a hobby for enthusiasts; it is a legitimate tool for production-grade engineering. The only question left is whether you are brave enough to turn off the cloud and trust your own silicon.
Transcript▾
Yesterday, I showed you how you could get Deep Seek version 0731 running inside of DS4 or Dwarf Star. And those quantisations were produced by the community whilst we waited for the Dwarf Star community to introduce this officially to the repo. And I am happy to say we finally have that result. In the latest commit here, we could scroll down and see that the old Q2 matrix file has been replaced here with the 0731. What we get here is the interesting Q2 and the last six layers being quantised four here as well. So we get the full range basically updated to 0731. And here we have the updated scripts. So let's get that all set up and running. So I am going to change directory into my DS4 folder here. And because I have pulled this down, I am just going to go get pull. And I am probably going to get conflicts here because I played with the actual download file, which we do. So, let's go get diff. You will see that I made these changes in order to update the repo and the Q2 I matrix file. So, realistically, we can get stash that. I don't need that anymore. Get pull. And with that downloaded, you are going to want to make sure you run make again. Not do not make the same mistake I did. Think it is all just going to work just because you have get pulled. You want to make again to make sure all of the files are rebundled up. And I am just going to remove RF GGUF and I am going to remove that quantisation which was kindly provided to us by the community. And I am simply going to go download model and I am going to play around with the interesting quantisation because I believe I have the room for it. And we are literally just going to do that and it is going to download the model for us. Now, I have made a video on how to get this all set up, and I will link that above. You are literally just going to be changing the Q2I matrix command that I use there. You are literally just replacing it with that or depending on the version that you want. Bearing in mind, Q2 is available for 96 to 128 gig RAM machines. Similarly, I think we can squeeze onto there. That is what we are going to check today. If you have the room, if you have a bigger machine, then you can go to the Q4. Or you can get the mixture of experts unquantised lossy format here. If you got 156 gig or if you got a big daddy like a Mac studio, you can go for the pro variant, which you can use this script here. Okay, this is coming in at 90.88 gig, whereas the 2bit quant that we downloaded yesterday was coming at 80.7 and the original 2bit quant 0731 was 86.7. So just to give you an idea of the size, it is a little bit bigger, this hybrid quant they have got going on here. Now, what I have gone and done is actually get Claude to write out a plan because what I said in my last video was it is kind of good to have bigger models, more capable models, spec out a project and then get lesser models, local models to actually implement those. It was a theory. I want to put it to the test. And as I say, I asked Opus on high mode to write a very detailed spec in order to build the same app we built yesterday, which is this document scanning application. Now, it asked me a couple of questions. It is built out this plan here. I am not even going to I am not even going to look at this plan. I am just going to get DeepSeek to actually just implement it from the get-go, and we are going to assess at the end. So, let's get this up and running. So, how we do that is we go DS4 server. We are going to do the whole shebang here, and we are going to increase that context to 100,000. This should pick up on the one and only model that's in there. This looks good. It is loading up right now. I am going to whack on my fan, so excuse this for a sec. And I will put in noise cancelling. Now, I have done instructions on how to set up open code on my previous video. However, there are some reports that it thinks forever and that we should put reasoning mode on max. So, I will leave links down below to the configuration that you should need to give you the ability to set reasoning mode as max. All I am going to say is implement the plan and link to that file and let it rest. So, let's check back in however long this takes and have a look at if it even runs first and foremost and exactly how long it took. Right. And we are finally done. And I say that I have already started running. It is running. I haven't tested it yet, but this has been running for 2 hours and 44 minutes minus a few instances where I didn't notice I needed to approve something or or whatever. It took a while and generally it moved quite fast. I mean, it is again we are talking about two hour two and a half hours of logs here, but tokens per second averaging 23 tokens per second. Not too bad. Compacted itself a few times, but as AI always does, it seems quite confident. Let's just give the damn thing a go. So, we got it here. Let's open this up. And it is slightly more improved the user interface. Like, we have got that typical kind of early Opus 4.5 look. Nothing too crazy, but I am not really after any design, to be honest. Now, let's give it our test lease here. So, if we drop that, this should be connecting to this machine which has an OCR model running on it and it should detect what is going on. Now, you can't see this. However, I should be able to see if we're getting some action on this end and it looks like it is generating. It looks like there is something going on. If you remember rightly, this did not work first time with the previous version of of of deep sea. However, that could be a number of reasons. The fact that I asked Opus to give it a very indepth like spec implementation plan. Anything is possible. Okay, I had to refresh the page to get that. So, there is a bug there, but we open it. It is done it. It is a working app. And I should be able to query what is the date on this lease. I think this is using sonnet 4.5 but let's give it a go on open router reading. There we go. So really good result again a one prompt a single prompt result there with it obviously being given direction from Opus a relatively fast result I think just observing it whilst it is doing its thing given the scale of the app. I have no doubt this would have taken half an hour to an hour with a like a Frontier model. So quite good speed there. Overall, I am impressed. So there you go. I will probably record another video kind of from start to finish as I did with the previous version as the scripts have changed. So look out for that one. Again, let me know what you guys are doing with your local AI stuff, what you will be doing with this Deep Seek model. I love hearing what everyone's doing. I am obviously a coder. I use Open Claw and Hermes and stuff like that, but what are you doing? Like, subscribe if you haven't already. Until next time, keep on vibing.