Zum Hauptinhalt springen

AI models that run on this device.

Two small chat models run in a computer’s browser here; every other model is a file you download.

I'm new: start here

Get a model running on your computer, then ask it to draft an email.

A model is a file. A chat app opens that file and lets you talk to it. This guide uses LM Studio, a separate app.

  1. 1. Find a model that fits

    This walkthrough uses Qwen2.5-1.5B-Instruct-GGUF, a small chat model. Check the app requirements above first. This model has not been tested on your computer.

    Want more choices? Use the finder, choose “Ask questions and write”, then select your computer's memory.

    Find a model for my computer

    A file-size match is a starting point. It does not prove a model will run well or write good emails. For a file you already chose, use its file-opening help below.

  2. 2. Get the app and model

    1. Download LM Studio for Linux, install it and open it.
    2. Open Discover. Search for Qwen2.5-1.5B-Instruct-GGUF, or paste the model's Hugging Face address.
    3. Open the file choices. Choose Q4_K_M only if the app marks it as supported by your computer. This is a smaller version of the model.
    4. Click Download and wait until it finishes. The model downloads from its publisher, rather than Hugging Bay.
    Already downloaded a model file from Hugging Bay?

    Keep the exact filename. The file-opening guide explains how to import it. Double-clicking the file may not open a chat.

    Open a downloaded model file

    After importing, continue to step 3 below.

  3. 3. Run it on your computer

    1. Open Chat in LM Studio.
    2. Use the model picker at the top to select the model you downloaded. Wait for it to finish loading.
    3. Type the example below into the message box and send it.
    Write a short, friendly email asking to move our meeting to Friday.

    You're running a model when its reply appears in the chat. Read the draft and check its details before using it.

    If it does not load, close other apps and try a smaller file. If the app reports unsupported hardware, check its requirements or use another supported computer.

    Help if the model will not load
Other apps and source instructions

LM Studio: getting startedOllama: setup and first chatJan: setup and first chat

App requirements and controls can change. Check their instructions if your screen differs.

Quick answer: compatibility and sources

How do I use I'm new: start here?

It depends on your client and setup. Find a model, get an app and send your first message on your computer. Check the current file record before downloading. Metadata access, file hosting and a tested runtime are separate things.

Model weights are learned parameters; a runtime is the software that loads them. RAM is working memory, separate from disk space for downloaded files.

Page-copy provenance: the revision record names apps/web/server.mjs, apps/web/lib/aeo-page.mjs, apps/web/lib/api-status-contract.mjs, apps/web/lib/agent-readable.mjs, apps/web/lib/docs-hub-model.mjs, apps/web/lib/compare-pages.mjs and commit 8871bab84e1cf80aea1686a944ec335078a6c036. This identifies the text source; it is not a model test receipt. A SHA-256 checksum fingerprints file bytes, not safety or answer quality. See what file verification checks. Run receipts, when present, belong to a specific model file and setup; this page asserts no model test.

Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/server.mjs, apps/web/lib/aeo-page.mjs, apps/web/lib/api-status-contract.mjs, apps/web/lib/agent-readable.mjs, apps/web/lib/docs-hub-model.mjs, apps/web/lib/compare-pages.mjs · Full revision record

Key facts

Catalog vs runtime
Metadata access, file hosting and a tested load are separate checks.
Checksum
SHA-256 confirms file identity, not license permission or answer quality.
Receipts
Run evidence is scoped to one file and setup; it does not transfer to other files.

Evidence you can inspect (plain text)

  • GET /openapi.json lists request and response shapes for public API reads.
  • GET /api/agent-discovery lists agent-facing interfaces when enabled.
  • Open /artifact/hf-model-qwen-qwen3-8b/files for model exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-qwen-qwen3-8b for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-qwen-qwen3-8b/card.md for machine-readable source facts (not a runtime test).
  • These documents describe interfaces and catalog reads; they do not execute or score models.

Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.

Which date applies to which fact

  • Committed page-copy sources:
  • Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
  • Run receipts: Only on /evidence pages when recorded; otherwise unmeasured

Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.