Python

You can build a fully local, sandboxed code interpreter agent. You pair Ollama (running a reasoning model such as Scout, the smallest Llama 4 variant , or DeepSeek R1) with a Docker container that runs the generated Python code. The agent sends a prompt to the local LLM, which writes Python. That code goes into a locked-down container with no network and strict limits. The output feeds back to the LLM so it can fix and retry. The whole loop runs on your machine with zero cloud calls.

Florence-2 and Qwen2-VL both run on consumer NVIDIA GPUs with as little as 8 GB VRAM. They handle OCR, object detection, image captioning, and visual question answering, all of it offline. Florence-2 uses a small sequence-to-sequence design with task prompt tokens. That makes it fast and reliable for structured extraction. Qwen2-VL takes a chat-style approach. It handles open-ended reasoning, dense documents, and follow-up questions. The two models work best as a pair, not as swaps for each other.

You can harden LLM apps against prompt injection and data leaks by stacking defenses. Input cleanup strips control tokens before they hit the model. Output filters scan replies for PII and secrets. Structured output forces the model to follow a fixed schema. Add a system prompt firewall that walls off trusted rules from user input. Together they turn one bare API call into a pipeline. Bad prompts get caught before the model runs. Risky data gets redacted after. No single layer is bulletproof. Stacked, they cut the attack surface enough that most threats give up.

You can clone your own voice with Coqui TTS using just 5 minutes of recorded audio, all on your own hardware. The steps are simple. Record clean audio. Turn it into a training set. Fine-tune an XTTS v2 or VITS model. Export the result for real-time use. On a modern GPU like the RTX 5070 with 12 GB of VRAM, fine-tuning takes 2 to 4 hours. The output sounds natural and keeps the target voice’s timbre, pacing, and accent.

The Model Context Protocol gives LLMs a standard way to call external tools, read files, and query databases. You skip the rewrite each time you switch models. You can build a working MCP server in Python with the official mcp SDK in under 100 lines. It runs with Claude Desktop or Claude Code in minutes. This guide walks the full path, from a tiny first server to production.

What MCP Is and Why It Changes Tool Use

MCP is a JSON-RPC 2.0 protocol. It lets an LLM client (like Claude Desktop , Claude Code, or Cursor) find and call tools exposed by a server process. The big shift from older function-calling is the discovery step. Instead of hard-coding tool defs into every prompt, the client sends a tools/list request when it connects. It gets back the full schema for everything the server exposes. Add a new tool, restart the server, and any client sees it on the next connect.

A custom Home Assistant integration is a Python wrapper for your hardware’s API, packaged as a HACS component. You get full entity control and automation support for unsupported or legacy devices. No fork of core HA. No wait for an official integration.

That said, custom integrations carry real upkeep. Before you reach for Python, check if a simpler path already exists.

When to Write a Custom Integration

Home Assistant ships with over 3,000 built-in integrations. Before you write a line of Python, visit home-assistant.io/integrations and search the HACS default store . Odds are good your device is already covered, or a community add-on exists.