Documentation
Everything you need to run ClickProbe against your own app — from your first exploration session to wiring bug resolution into your IDE. These docs are in English; write us at beta@clickprobe.ai if you prefer German.
User Guide
- Test Credentials Many apps have a login wall. If ClickProbe never gets past it, it can only ever explore the one page behind it. The Credentials section on a project's edit…
- What the tester does to your app ClickProbe's AI has no knowledge of how your app works. It looks at what's on the page, guesses what a button or a link does, and clicks it to find out —…
- Onboarding Guide This guide walks a fresh user through the 7-step onboarding wizard at /app/setup. Target: first bug found in under 10 minutes.
- Testing Your App on localhost ClickProbe's local proxy is what makes testing localhost possible at all: the AI's browser runs on your machine, not in our cloud, so it can reach anything…
- Proxy Connection Troubleshooting clickprobe-proxy needs to reach a handful of ClickProbe-owned (and Chromium-owned) hosts over plain outbound HTTPS/WSS. This page covers the failure modes that…
- Updating the ClickProbe Proxy clickprobe-proxy is a binary you install and run on your own machine — it does not auto-update. This page covers how to check your version, how to update on…
- Bug Inbox The bug inbox is your central view of every issue ClickProbe has found across all your projects. Navigate to it at /app/bugs.
- Issue Tracker Integration Export ClickProbe bugs as GitHub Issues or GitLab Issues with one click from the bug drawer.
- Webhooks Webhooks let ClickProbe notify your external systems — Slack, Microsoft Teams, Discord, or any HTTPS endpoint — when events occur in your account.
- Email Notifications ClickProbe sends three types of email notifications. All can be managed from the Settings → Notifications page (/app/settings/notifications).
- ClickProbe — Closed-Beta Onboarding Guide - An AI that tests your web app like an intelligent human tester would — it reads the live page structure, guesses what UI elements do, clicks them, and…
IDE Integration
- ClickProbe IDE Integration clickprobe-proxy --agent-stdio is a stdio MCP server that exposes 9 tools to your coding agent:
- ClickProbe + Claude Code Add clickprobe-proxy as a stdio MCP server so Claude Code's coding agent can call clickprobe.* tools.
- ClickProbe + Cursor Add clickprobe-proxy as an MCP server in Cursor’s mcp_settings.json.
- ClickProbe + VSCode GitHub Copilot Agent Mode Add clickprobe-proxy as an MCP server for VSCode GitHub Copilot agent mode.
- Resolve Bugs from Your IDE Once the proxy is logged in with the agent:resolve scope, a coding agent can close bugs directly from your chat — no browser required.
- Auto-close bugs via commit message (GitHub & GitLab) If you already mark PRs with Fixes JIRA-1234 to close issues in your tracker of choice, ClickProbe supports the same idiom. Push a commit whose message…
- ClickProbe IDE Integration — Troubleshooting Fixes for keychain prompts, 401 loops, Windows path quoting, WSL, and Docker.