Portable-Local-Studio
Portable local AI studio for Windows, Linux, and macOS. Zero-setup GUI for Image Generation, GGUF LLMs, Text to Speech & Speech to Text
Runs with mockssource: GitHubJavaScriptMITcommit 6c3059443666
JavaScript, MIT licensed. The project labels itself: image generation, speech to text, text generation and text to speech.
Portable-Local-Studio runs, with stand-ins for the services it depends on. An Argusic agent installed it in 13 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Frontend deps installed, React UI builds and is served on localhost:1420, all 13 regression tests pass, server API endpoints respond correctly.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- vite 8 requires Node 22.12+, system has Node 183 minutes
- npm install missing for frontend deps1 minute
- rolldown native binding missing for linux-x64-gnu1 minute
- npm run build resolves to system Node 18 via shebang1 minute
- Install time
- 13 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- node --test scripts/tests/issue-regressions.test.cjs → 13/13 pass; curl localhost:1420 → HTTP 200; HTML content verified
- Model tokens used
- 82,054
- Exact commit tested
- 6c3059443666
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
## Errors encountered
| Error | Fix | Minutes |
|---|---|---|
| Test 1 failed `@tauri-apps/api` not found | `npm install` in `app/frontend/` | 1 |
| `vite build` required Node 22.12.0+ (system has 18) | Downloaded portable Node 22, built with it …
| `@rolldown/binding-linux-x64-gnu` optional dep not installed | `npm install @rolldown/binding-lin…
| `npm run build` resolved to system Node 18 (via `#!/usr/bin/env node`) | Invoked vite directly wi…
## Verification
- `node --test scripts/tests/issue-regressions.test.cjs` → **13/13 pass, 0 fail**
- `curl -s -o /dev/null -w '%{http_code}' http://localhost:1420/` → **HTTP 200**
- `curl http://localhost:1420/` → returns proper HTML with `<title>Uncensored AI Studio</title>`
- `/api/health` → returns full JSON health report with `"platform":"linux"`, `"build":"text-image-v…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 13 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.11 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/portable-local-studio)Questions
- Does Portable-Local-Studio run?
- Portable-Local-Studio runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 13 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test Portable-Local-Studio?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6c3059443666. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Portable-Local-Studio?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Portable-Local-Studio take to install?
- 13 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Portable-Local-Studio need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Portable-Local-Studio?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Portable-Local-Studio?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.