No Stupid Questions

Sure, there are open-weight models and many of them are very usable on quite limited hardware, some can even run on phones which is ridiculous. Don't expect paid-service-level speed or abilities or even free-tier of those same services where it's running on datacenter hardware, but running locally on reasonable consumer hardware it's certainly possible to get close to that, at least sometimes, in some situations. YMMV depending on your configuration and your needs. Most of the good open-weight models are in fact originally released by billionaire asshole companies who have the resources to actually put down these foundations (but a lot of the best open-weight releases are coming from China, which is its own sort of concern), but how and why they get released is not really the important part for us because once they're released, they're released forever and people can take them and adjust them and re-train them for all kinds of different purposes. You just have to be aware of where they came from. On their own, they do not read your disk or phone home (they are not capable of it without an external client enabling and allowing them to use tools at all). They are just text input, and text output (or images/audio input using mmproj techniques, or stable diffusion for image/audio generation, those are totally different cans of worms and outside the scope of this, but it can be done) They're ultimately just text generators, but some of them are trained to general particular formats of text that tell an external software when it should try to use tools.

Personally, I found ollama the easiest way to get started, but I'm sort of a minimalist and started out very casual (and in some ways still am). Another place that looked nice to start out with was the desktop application "Jan". OpenWebUI was relentlessly recommended to me but I found it a bit buggy and unnecessarily resource intensive and ultimately dropped it. I tried Librechat also and it was a little better but ultimately I had pretty similar problems with it. (A lot of stuff in the AI field is vibe-coded slopware, and it really shows sometimes, be warned and be aware) Capek is a very minimal alternative web chat frontend that I've kind of settled on personally. I find minimalism is the best way I can think of to avoid all the feature-bloated insecure AI slop. I don't know if it's actually helping or a good strategy, but it's the strategy I've chosen.

Can I just slow it down and get it to work locally?

Technically yes, but pushed too far it slows down dramatically to the point of not really being useful anymore, unless you're careful about how you do it. Key things to look for:

• File size/download size, and memory usage are pretty much the same number. Everything in the file has to be loaded into preferably VRAM. Most of the time you can go a little bit over and the leftovers will be loaded into system RAM for your CPU to process instead and this can be manageable, but often slows things down dramatically.
• Quantization (most widespread is Q4_K_M) trades a tiny bit of model quality/precision for vastly smaller sizes and Imatrixes (IMAT, IQ_*) have been developed to make even smaller sizes viable, but with somewhat more significant damage to the quality of the model's processing and outputs.
• Uncensoring (common terminology and keywords include abliterated/abliteration, heretic, unchained/unleashed, etc) is often included in unofficial open-weight models and reduces or removes the refusal behaviors of the model (telling you it can't help you with that because blah blah blah) which can be annoying when it's simply misunderstanding the request or false-triggering or if you just don't want the model's training dictating its own morality to you. Done poorly it can make the model stupid and broken, especially on brand-new models or that haven't been heavily experimented with yet, but most of the time the community gets the models uncensored pretty smoothly after some time.
• Some models are trained to try to use external tools when they're told they're available but it's usually not their default mode and they typically won't even try unless you're specifically using client software that specifically tells the models it is designed for and supports tool use (most often called "harnesses") similar to claude code. Opencode is a popular claude-like one, personally I prefer 'pi' (pi-mono) which is very minimal. Many GUI applications also support some kind of tool use but I'm not super familiar with those personally.
• Some models are very highly specialized, and may require very specific configuration, prompts and inputs to work as intended, they may not all be a traditional "chatbot" that you can just write text and converse with, but most of them are, and the popular ones pretty much all are intended for general use like this.
• Parameter count sort of represents the model's knowledge base and breadth of knowledge and kind of also how smart or stupid it is, this is usually measured in billions (for example 9B or 27B) and usually provides a good hint towards the approximate expected file size (A Q4 is usually less but in the same ballpark of GB
• MoE (mixture of experts) is usually noted by "AB" notation (for example, 31B A4B tells you it's a 31 billion parameter model with 4 billion of those parameters active during the processing) MoE models are still big, but MoE is a technique that makes the model run much faster than it's file size would suggest by ranking out only the parameters that "seem" like they will be most relevant for what you're asking about, which can help a lot when you're trying to cram a larger model than you can reasonably run with parts of it in much slower CPU/system memory. It's not a magic bullet, but it is a popular strategy that works pretty well. You still need to have the file loaded into some kind of memory, and if you're using system memory/CPU inference at all it's still not going to be as fast as a model fitting in pure GPU is, but MoE it can make it practical to run much larger models than you would otherwise be able to tolerate. On the other hand, because only, for example, 4B parameters are active (and they may not be all that great at deciding which 4B they should use) they can sometimes be stupid. Generally it's a good thing though depending on your needs. The default models use all parameters all the time. This is the opposite of MoE and is called "dense". There's no right or wrong answer, try both and see what you like. They're all flaky sometimes but in my experience a dense model is more consistent, whereas MoE can have some very good results and some very bad results depending on how the dice roll inside its brainbox.
• Context is important when you're trying to have longer conversations or process a lot of local data at once. Context uses VRAM memory too. If your context is limited the model may have poor "memory" and become forgetful or have to keep compressing its context. You can set context to use Q4 quantization too which lets you fit more context into memory, but there's always a limit, the model itself will have a maximum and the software you're running it with will likely have its own limit. It's not super important for short questions but becomes important for more advanced use, especially coding.

Hope that helps, have fun, be safe!