DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to ask questions about pictures without uploading them with Poly Strata

Send screenshots or photos to a local vision model that reads images on your PC.

Who it is forA user with private images, such as scanned receipts, product photos, or screenshots of internal dashboards, and a PC with a suitable card.

The problemPicture-reading AI services require uploading the images, which may include personal or confidential content.

The outcomeYou get answers about the pictures from a model running on your PC, and the images are never uploaded.

What you need first

  • A Windows or Linux PC with an NVIDIA card, or an AMD card with 12 GB or more for Qwen3.8-Flash-Next
  • Enough disk space for the model file you pick, from about 11 GB to 114 GB depending on the model
  • Enough RAM for the model you pick, since large models such as GLM 5.3 Flash and DeepSeek V4 Flash keep most of their file in RAM
  • A coding agent that can point at a custom API base, if you want to use one with the local server

Steps

  1. Install Poly Strata with the one-click installer for your operating system.
  2. Pick a model that reads pictures, such as Qwen3.8-Flash-Next, Gemma 4 26B-A4B, or MiniCPM-V 4.7 35B-A3B.
  3. Start the server with that model and send it one image with a question through the localhost API.
  4. Check the answer against the picture yourself before you rely on it.

Prompt for your agent

Using the PolyStrata server on localhost with <vision model name>, send the image <image path> and ask: <question>. Expected output: a text answer describing the image. Verify that the answer matches what is visible in the image and that the image was not sent to any remote service.

Caveat. Only Qwen3.8-Flash-Next uses the unchanged Strata engine; the picture-reading models on the other engine are experimental.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page