Vitrinka
Author, operated by LEFTEQ
One tunnel for your whole dev team: a tester circles a bug and writes one sentence, an agent fixes it and posts the after-shot.
Facts
- Findings answered
- 148 from 37 sessions, across 3 PRs
- Tester time
- 3.9 h
- First commit to v5.10
- About 12 weeks
Vitrinka is where testers, designers and coding agents meet on one board.
The problem
Bug reports lose their context between the person who saw the bug and the one who fixes it — and agents need that context more than people do.
What I built
Boards where a tester circles what is wrong and writes one sentence; the agent receives the exact element, the screenshot and the state, fixes it, and posts the after-shot back to the same spot.
One Go binary with SQLite runs both the public service and self-hosted installs, with SSO (Entra, Keycloak, Okta), roles, an audit log and an offline mode for strict-security environments.
What this means for your project
Weekly demos on my projects happen on Vitrinka boards: you mark what you want changed, and you watch it change.
Built with
- Go
- SQLite
- TypeScript
- MCP
- Claude Code and Codex plugins