Piik
Free, open-source screen sharing for private live streams with friends. Watch together in a browser or self-host Piik. 免费开源的私密屏幕共享，支持游戏直播、一起看电影与自部署。
Runssource: GitHubTypeScriptMITcommit bd59e7f79883
TypeScript, MIT licensed. The project labels itself: live streaming, p2p, private streaming, screen sharing, self hosted, watch together and webrtc.
Piik runs. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Node.js v24.19.0 and Go 1.27.3 installed, npm deps resolved, all 1708 vitest tests pass, Go server compiles and runs serving 200 on /healthz, web UI builds successfully
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 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- zip/unzip commands not installed, causing test failure: spawnSync zip ENOENT3 minutes
- Node.js v18.19.1 installed but v24.19.0 required (>=24.0.0 <27)2 minutes
- Go compiler not found, required for server binary2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test exited 0, 1708 passed; go test ./... all passed; go build ./cmd/piik-server built 57MB binary; ./piik-server -check-config returned config=ok; curl localhost:8788/healthz returned 200
- Model tokens used
- 79,638
- Exact commit tested
- bd59e7f79883
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
echo \"\" # Also check Vite proxy to Go # Actually let's just verify the Go server is running by checking it responds wait 2>/dev/null || true" in /work/repo succeeded in 7853ms: time=2026-10-23T08:40:46.840Z level=INFO msg="Piik server is listening" event=ready version=develop… 200 time=2026-10-23T08:40:54.832Z level=INFO msg=piik-server event=stopped failed=false The server answers with 200 on `/healthz`. Now generating the final result: tokens used 79,638 The server answers with 200 on `/healthz`. Now generating the final result:
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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 8 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
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
Topics (from GitHub)
live-streamingp2pprivate-streamingscreen-sharingself-hostedwatch-togetherwebrtc
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/piik)Questions
- Does Piik run?
- Yes. Piik runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test Piik?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bd59e7f79883. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Piik?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Piik take to install?
- 8 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 Piik need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Piik?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Piik?
- 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.