If something is missing or awkward, this is the place. Most useful framing is what you were trying to do and where it got stuck — that tends to lead somewhere better than a specific solution would, because the underlying problem is often fixable in a way nobody had thought of. Bugs are welcome here too. Include: What you did What you expected What happened instead, with the exact message Recent changes that came from exactly this kind of report: models that were too big for a card used to silently thrash instead of saying so, and a model that failed to shut down cleanly could block every later run with no way out but restarting. Both are fixed.

One of the more interesting things about running locally: once a model is downloaded, the internet is optional. If you're using Lizard somewhere without a network — a plane, a locked-down site, a lab machine — a few notes worth sharing: The model needs downloading once, on a connected machine or by copying the file across. Generation, the chat app and the local API all work with no connection. Update checks simply fail quietly. Nothing breaks. If you've set this up in an environment with real restrictions, how did you move the model files across, and did anything get in the way?

A place for what you're actually doing with a local model — working, half-finished or abandoned, all interesting. Some things people use this kind of setup for: Drafting and rewriting without documents leaving the building Summarising long files that shouldn't go to a cloud service Coding help on a locked-down or offline network Something running on a schedule, where per-call pricing would be awkward If you've wired Lizard into an editor, a script or a larger tool, the setup details are the useful part — that's what others can copy.