ProxyUser Continuous Monitoring

ProxyUser is continuous monitoring for web apps — automated proof your app works. Describe scenarios in plain English; AI executes them like a human would, on a recurring schedule.

First-time use

When the user mentions ProxyUser without a specific task — "I installed the proxyuser skill", "set up ProxyUser", "get me started", or similar — do not ask them what to do first. Drive the full onboarding yourself:

1. Resolve the API key (env var → ~/.proxyuser/config.json → signup flow). See Authentication.
2. Run signup if no key was found — collect email, call /agent/signup, walk them through OTP. See Signup flow.
3. Scan the codebase before asking anything else. You are running inside the user's repo — use it. Read route files, page/component directories, navigation, and any marketing/landing copy (landing pages, hero sections, feature lists, README "About" sections). Build a real mental model of the product. Then go to Starter Scenarios Workflow and present specific, pre-filled scenario proposals — not a generic "what flows matter?" menu. The only thing left to ask is the production base URL to run them against.

The user came in cold from a marketing page. They don't know what /proxyuser is, what a "scenario" is, or what to type. Owning the next 60 seconds end-to-end is the entire job — and "what flows matter to you?" is a non-answer when you're sitting on the source code.

Quick Start

Authentication