Pinokio

Pinokio is a free, MIT-licensed desktop application built by solo developer cocktailpeanut that lets you install, launch, and manage open-source AI tools on your own computer with a single click. Where installing something like ComfyUI or Stable Diffusion WebUI would normally require navigating Conda environments, CUDA toolkit versions, and Python virtual environments from the command line, Pinokio replaces all of that with a browser-like interface and a JSON-based scripting system. You click Install, Pinokio pulls the GitHub repo, builds a sandboxed environment, and opens the app in its built-in browser. No terminal required.

The catalog spans over 200 community-maintained app scripts, covering nearly every major open-source AI category: image generation tools like ComfyUI and Automatic1111 (AUTOMATIC1111 WebUI), local language models via Text Generation WebUI and Ollama integrations, voice cloning, music generation with AudioCraft, video generation with Wan2.1, and more. As of April 2026, the current version is v7.2.6, following the major Pinokio 7 release in March 2026 that added native AI agent control across every installed app. Pinokio runs on Windows, macOS, and Linux with no mobile or cloud components.

What Pinokio actually is in April 2026

Pinokio operates as a "localhost platform": a persistent desktop shell that manages installation, launch, and process control for open-source AI apps via shareable JSON scripts. Each app in the catalog is defined by a script that points to a GitHub repo and specifies exactly which dependencies to install in a sandboxed Conda or venv environment. This means every installation is deterministic and reproducible: someone can share a Pinokio script URL and another person gets the identical environment on their own hardware.

The current v7.2.6 build includes the agent interpreter layer added in v7.0.0 (March 17, 2026): any Pinokio-installed app is now automatically controllable by AI agents such as Claude, Gemini, or Cursor via a SKILL.md-based protocol. The "Ask Pinokio" sidebar lets you query app state and troubleshoot errors without leaving the app page. v7.2.0 added reusable shareable tasks, supply chain attack protection for package managers, and support for private GitHub repositories.

The Pinokio 5.0 release (November 30, 2025) was the biggest conceptual pivot in the app's history. cocktailpeanut reframed it as a "localhost cloud" rather than just an app installer. Key additions included AI-assisted script generation (describe what you want in plain English; Pinokio writes the JSON installer), LAN Wide Web for accessing your apps from other devices on the local network, split-screen Cells for simultaneous front and backend views, and automatic rollback on failed installs. cocktailpeanut announced it on X with: "Anyone can make a 1-click launcher now. Even me. I never touch code when writing launchers anymore. I just throw a GitHub URL at Pinokio and ask Pinokio to build one. Everyone's on equal footing." Pinokio 3.0 (December 20, 2024) added browser automation via Playwright, the UV Python package manager for faster installs, native Hugging Face API support, and clearer error reporting.

Where Pinokio sits versus Stability Matrix and manual venv setup

The two most relevant comparisons for Pinokio users are Stability Matrix and manual command-line installation. Each solves a related problem but with different architectural decisions.

Stability Matrix (lykos.ai) is a C#/.NET desktop application purpose-built for image generation frontends: A1111, Forge, ComfyUI, InvokeAI, Fooocus, and kohya-ss. Its defining architectural advantage over Pinokio is a shared model library: models you download are stored in one directory and symlinked across all compatible frontends, meaning a 7GB Stable Diffusion checkpoint is stored once even if you run three different WebUIs. Stability Matrix also ships a cleaner native GUI rather than a browser wrapper. The tradeoff is categorical scope: Stability Matrix does not run LLM text generation tools, audio models, video generators, or arbitrary GitHub repos. It is an image-specialist tool. For a user who only wants ComfyUI and Forge, Stability Matrix is often the better fit. For a user who wants ComfyUI, Whisper, Bark, Text Generation WebUI, and Wan2.1 in one launcher, Pinokio is the only option that covers all of them.

LM Studio provides another useful comparison. LM Studio is focused exclusively on running local language models: it handles GGUF and MLX downloads from Hugging Face, provides a polished chat interface, and exposes an OpenAI-compatible API. It is outstanding at exactly that job. Pinokio can also run LLMs (via Text Generation WebUI, Open WebUI, and similar scripts), but those are just entries in its catalog alongside image, audio, and video tools. LM Studio's model browser is more polished than anything Pinokio offers for LLMs. Pinokio's advantage is breadth: if you want a single launcher for everything, including AnythingLLM-style knowledge bases alongside image and audio tools, Pinokio covers that without needing a second application.

Manual installation (cloning repos directly, managing Python venvs, installing CUDA by hand) remains the right choice for power users who need complete control. Pinokio's sandboxed-environment approach prevents you from sharing model weights across apps, uses more disk space per install, and limits the kinds of custom modifications (adding ComfyUI custom nodes outside the script, unlocking content filters, pinning specific package versions) that serious users need. Pinokio does not replace the terminal for people who are comfortable in it; it replaces the terminal for people who are not.

How the install and run loop actually works

You download the desktop installer, run it, and the application opens showing an empty library. Visit the built-in Discover tab or beta.pinokio.co gallery to browse scripts. Clicking "Install" on ComfyUI, for example, triggers Pinokio to clone the GitHub repo, create a Conda environment, install all Python packages, and download required model weights. A typical ComfyUI install takes 10 to 20 minutes depending on connection speed. Each installed app appears as a card; clicking Launch opens it in the built-in browser. Multiple apps can run simultaneously if your hardware has the capacity.

"Overall, it's fun and useful and has a ton of package options for one-click installation. Excellent for AI experimentation, free, and has extensive package options ranging from AI audio to video and photo upscaling tools." -- Peter P., SourceForge review, February 25, 2025

The script architecture also enables a useful research workflow. A developer can write a custom Pinokio JSON script for any GitHub project, share the URL, and give colleagues a reproducible one-click install for the same environment. Community scripts for Wan2.1 video generation, FLUX image generation, and voice cloning tools appear within days of new model releases on GitHub.

The recurring friction points users keep hitting

Disk space is the most consistent complaint. Pinokio installs a separate Miniconda base per app by default rather than sharing a common Python environment across tools. Users who install five or six AI apps regularly report 100 to 200 GB consumed, with multi-app setups reaching 389 GB in documented cases. pip caches alone can reach 10 GB or more for a single complex tool like FaceFusion. The Pinokio 3.0 update added a disk usage display per app, which helps users identify the largest installs, but the underlying cause (isolated per-app environments) is by design. Pinokio includes a cache-cleaning option that can reclaim significant space, but this is a manual step that surprises new users who expect smaller footprints.

"The interface, despite being beautiful, was laggy as hell.. Pinokio pulls in Miniconda and a mountain of packages [to install] even the lightest repository, consuming significant disk space." -- NeuroDonu, Medium, 2025

App script breakage is the second major friction source. Community-maintained scripts can fall behind their upstream projects. When A1111 or ComfyUI ships a breaking change, the Pinokio script may fail until a contributor updates the JSON. Power users on r/StableDiffusion have noted: "Pinokio doesn't care about stuff that was already installed, can mess up your PATH, CUDA versions, and will download new PyTorch every time you try to install something." For users who want fine-grained control over which PyTorch version ties to their GPU, Pinokio's automated approach can create conflicts that require manual intervention to resolve.

Newly released NVIDIA GPUs are a recurring pain point. When NVIDIA ships a new architecture, the pinned CUDA and PyTorch versions in existing Pinokio scripts often predate the new driver requirements. A fresh 50-series card buyer may find that several image generation scripts fail until maintainers update the dependency pins. This reflects a limitation of script-based automated installs generally, not a Pinokio-specific bug, but it is a friction point Pinokio users encounter more visibly than CLI users who can pin versions themselves.

The open-source marketing versus closed-source reality is a genuine concern for users who prioritized transparency. Pinokio's public GitHub repository is MIT-licensed, but the functional runtime is a pre-compiled binary called pinokiod that is not open-source. Independent developers who attempted to inspect the actual execution code found a closed-source core wrapped by an open-source shell. cocktailpeanut has not publicly addressed this inconsistency directly. For users who are comfortable with the tool working as expected regardless of source availability, this is a non-issue; for users who selected Pinokio specifically because of its "open source" designation, the discovery has been disappointing.

In May 2025, Pinokio experienced a domain disruption when pinokio.computer went offline due to a Squarespace registration issue, taking the in-app Discover page with it for several days. cocktailpeanut publicly asked for help on X and migrated the platform to GitHub Pages hosting as a resolution. This incident highlighted a structural fragility: if the Discover infrastructure is unreachable, new installs from the gallery are blocked. cocktailpeanut's fix -- using GitHub Pages as the canonical URL rather than a custom domain -- substantially reduces the recurrence risk.

Who Pinokio is for, and when to skip it

Pinokio is best suited for AI hobbyists and researchers who want to experiment across multiple tool categories without maintaining separate Python environments. If your workflow involves trying a new image model this week and a voice conversion tool next week, Pinokio's unified launcher removes the repeated setup overhead. Educators demoing AI without CLI experience and researchers sharing reproducible environments via URL are also natural fits.

Skip it if you need deep customization of a single tool. Someone who lives in ComfyUI and needs many custom nodes and specific model paths will hit Pinokio's sandboxed limits and find manual installation gives more control. If local LLMs are your only use case, LM Studio's model browser and Ollama's API layer are more polished choices. Pinokio's value is breadth across categories, not depth within any single one. For someone who wants a diverse no-code local AI setup covering image, audio, video, and LLM tools in one place, it remains the clearest option available as of April 2026.