kiji-proxy tested by Argusic Runner

Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100

all runs of kiji-proxyai-gatewaydata-anonymizationdata-maskingllm-securitypii-detectionprivacy

Session recording

Loading recording...

Download the original recording · fingerprint 5b3f0686e6515837...

What the test found

Installed and verified: Go backend builds and serves /health 200 with the quantized ONNX PII model loaded, masks real emails end-to-end via /api/pii/check, Unix desktop Electron app launches and stays running on the virtual display, Python (2 passed) and Go (512 passed) unit suites are green, and the frontend production bundle builds cleanly.

Real end-to-end verified: quantized ONNX model loaded (737MB, 53 PII labels), /health returned 200 healthy, /api/pii/check masked [email protected] to a fake email with EMAIL label at confidence 0.997, Electron v43 desktop app launched on Xvfb DISPLAY=:99 with main+gpu+renderer processes staying up and UI served at localhost:8080. 512 Go PASS assertions across 11 packages, 2 Python pytest PASS, tsc type-check clean, ruff clean. Benchmark smoke_test: 3/4 detection cases pass, 1 fails on FIRSTNAME/SURNAME/COMPANYNAME in a structured block (model accuracy, not setup). No third-party API keys needed for PII detection; proxy-to-upstream LLM phase requires real keys (unverified).

Argusic installed kiji-proxy in 26 minutes and launched it; verification reached Verified running for real. 9 of 9 recorded errors were worked through (see the timeline below).

Runsall runs of kiji-proxy

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion