pintalisted

# Pinta Workflow: the user opens the Pinta Chrome extension, draws / picks elements on their running app, and clicks Submit. The companion server (one process per project, discovered via `~/.pinta/registry.json`) receives the session. Your job is to wait for sessions, then edit the matching source files. > **Compliance & safe usage (read once).** Pinta is **bring-your-own-Claude**: > it runs as a skill inside the user's *interactive* Claude Code terminal and > never proxies, stores, or shares Anthropic credentials. Keep it in that lane: > **(1)** interactive terminal use only — no headless, `claude -p`, Agent SDK, > cron, or CI; **(2)** one user runs their **own** Claude account/key — never > route multiple users through one subscription; **(3)** no "Login with > Claude.ai" / OAuth proxying. Interactive Claude Code use is the supported > lane under Anthropic's subscription terms; third-party tools that route > requests through subscription credentials are not. Heavy / automated > workloads belong on **API billing**. ## Arguments `/pinta` accepts an optional flag controlling delivery mode: | Flag | Behavior | When to use | |---|---|---| | `--push` *(default)* | Open one long-lived SSE stream via Monitor. Each new submission arrives as a single notification — no polling noise in the transcript. | Default. Best for Claude Code (which has Monitor). | | `--polling` | Long-poll loop with `curl --max-time 30`. Each cycle is one Bash call. Generates more transcript lines but wor