PinVari blog

PinVari for Mac power users

Articles for the Mac power user who buys premium one-time apps (CleanShot X, Raycast, Setapp) and runs an AI coding tool. The pain we write about: has a screenshot tool but nothing that understands the screen; hates subscriptions and cloud uploads.

Workflows

Bug Report Example: Named Elements Beat Pixel Guesses

A bug report example that shows how to give developers and AI agents the exact named UI element, repro steps, and screenshot—not a vague pixel guess.

Guides

Claude Code Screenshots: Stop Wasting Tokens on Pixels

Claude Code screenshot workflows waste tokens and fail to identify UI elements. Learn how macOS Accessibility API + on-device voice capture resolves named elements without pixel uploads.

Comparisons

CleanShot X Alternative That Understands What's On Screen

CleanShot X captures pixels. PinVari captures named UI elements with confidence scores and provenance—on-device, one-time $39, routes to coding agents and trackers.

Workflows

How to Give Claude Code Context That Actually Works

Give Claude Code the exact element, spoken instruction, and screenshot it needs—no token waste, no guessing. Here's how to make context work.

Guides

Can Claude Code See My Screen? The Honest Answer

Can Claude Code see my screen? Not on its own; it reads text you paste or type. Here is what it actually sees and how to give it real screen context.

Guides

Why Claude Code Fixes the Wrong Element

Claude Code fixes the wrong element because it sees a screenshot, not a named element. Point at the exact control and the guessing stops.

Comparisons

Jam.dev Alternative for Native Mac Apps

The best Jam.dev alternative for native Mac apps captures bugs in any macOS window: IDEs, Electron, and native apps, by voice with named UI elements.

Engineering

MCP Server for AI Agent Screen Context

A local MCP server for AI agent screen context resolves the named UI element on-device, so Claude Code gets confidence and provenance, not raw pixels.

Engineering

What Is the macOS Accessibility API Used For?

What the macOS Accessibility API is used for beyond screen readers — reading any app's UI as named AXUIElement roles, labels, and frames.

Workflows

Point and Speak to File Bugs to Linear and GitHub

File a bug to Linear from a screenshot and voice on Mac — circle the broken element, speak, and get a named, ready-to-file ticket.

Workflows

Push-to-Talk Voice for Claude Code on Mac

Push-to-talk voice for Claude Code on Mac lets you hold a hotkey, point at a UI element, and speak — the agent gets the named element, not a vague prompt.

Guides

Screenshots Waste Claude Code Tokens: Fix It

Screenshots waste Claude Code tokens: each image re-encodes to ~1,300+ vision tokens per turn. Send the resolved, named UI element as text instead.