jietuba

Open-source Windows screenshot tool with scrolling capture, annotation, OCR, translation, pinned-image editing, GIF recording and clipboard history. 开源 Windows 截图工具:长截图、标注、OCR、翻译、钉图编辑、GIF 录制与剪贴板历史。

Runs with mockssource: GitHubhomepageC++MITcommit 2d720c9d16c6

C++, MIT licensed. The project labels itself: clipboard history, clipboard manager, gif recorder, image pinning, ocr, onnxruntime, paddleocr and pyside6.

jietuba runs, with stand-ins for the services it depends on. An Argusic agent installed it in 25 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Full test suite runs on Linux (offscreen Qt) with 1872 tests passing; 8 failures are Windows-only path and font differences; Rust libs (longstitch, pyclipboard, ppocr_rust) compiled natively; win32, comtypes, gifrecorder, winreg, and ctypes.windll are mocked as Linux-incompatible Windows dependencies.

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 56 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
2
last tested
stars
573
forks
67
open issues
25
watchers
10
size
75 MB
created
last push

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.

Time lost to each failure while testing jietuba, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • evdev (pynput dependency) requires python3-dev headers for C compilation8 minutes
  • ctypes.windll not available on Linux5 minutes
  • gifrecorder Rust crate links Windows user32/gdi32, cannot build5 minutes
  • pywin32 (Windows-only) not available on Linux3 minutes
  • Python 3.11 required but container has 3.122 minutes
  • comtypes (Windows-only) not available on Linux2 minutes
Install time
25 minutes
Cold machine to finish
59 minutes
Errors hit and fixed
8 hit, 8 fixed with no human help
How the result was proved
pytest main/tests --tb=line -q: 1872 passed, 8 failed, 1 skipped, 643 warnings in 500s
Model tokens used
1,962,070
Exact commit tested
2d720c9d16c6
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.

6. test_build_file_payload_normalizes_path - Windows backslash normalization
7. test_extract_first_file_path_from_content_reads_json_payload - path normalization
8. test_rows_are_single_line_like_the_clipboard_panel - full vs basename path
exec
/bin/sh -lc 'ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes…
 exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:: not found
2026-10-19T23:23:35.957027Z ERROR codex_core::session: failed to record rollout items: thread 01a15…
2026-10-19T23:23:35.957061Z ERROR codex_core::session: failed to record rollout items: thread 01a15…
2026-10-19T23:23:35.957069Z ERROR codex_core::session: failed to record rollout items: thread 01a15…
tokens used
1,962,070

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 25 minutes.
  • Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

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.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.17
Argusic Runner1/3Did not run20.000.03

Topics (from GitHub)

clipboard-historyclipboard-managergif-recorderimage-pinningocronnxruntimepaddleocrpyside6rustscreen-capturescreen-recorderscreenshotscreenshot-annotationscreenshot-toolscrolling-screenshotsnipping-tooltranslationwindows

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/jietuba.svg)](https://argusic.com/subject/jietuba)

Questions

Does jietuba run?
jietuba runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 25 minutes, hitting 8 errors on the way, and recorded the session.
How did Argusic test jietuba?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2d720c9d16c6. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test jietuba?
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 jietuba take to install?
25 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 jietuba need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jietuba?
8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for jietuba?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion