These docs are in English. If you prefer German, write us at beta@clickprobe.ai.

ClickProbe — Closed-Beta Onboarding Guide

This guide is in English. If you prefer German, write us at beta@clickprobe.ai — we’re equally happy in DE or EN.


What is ClickProbe?

  • 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 reports bugs without knowing your code.
  • Cloud AI, local browser. The exploration intelligence runs in our EU cloud; a small binary on your machine controls the browser and fetches your target URL locally — your source code and local files are never reachable by the cloud. What the AI observes while exploring (page structure, extracted page text, and screenshots captured for your bug reports) does reach the cloud by design; see Testing Localhost & Internal Apps for the full guarantee and how to restrict where the browser is allowed to navigate.
  • Pay-as-you-go. You pre-load credits and pay only for actual Anthropic usage + a small session fee. No subscription required.

Before you start — beta pricing

As a closed-beta participant you receive €10 in free exploration credits, pre-loaded to your account. This covers roughly 200 short exploration sessions — more than enough to evaluate ClickProbe seriously.

There is no credit card required to use these pre-loaded credits. If you wish to top up, you can do so at any time from the dashboard (Cards via Stripe).


Step 1 — Create your account

  1. Open https://app.clickprobe.ai/auth/signup in your browser.
  2. Enter your business email address.
  3. Choose your sign-in method:
    • Magic link (recommended) — we email you a one-click link; no password needed.
    • Google OAuth — click “Continue with Google” if your work email is a Google Workspace account.
  4. Click the link in your email (magic link only). You land on the ClickProbe dashboard.

Beta note: Your account will show €0 balance initially. Ingo will grant your €10 credit within one business day of you confirming your account via email to beta@clickprobe.ai. If you need it sooner, just say so.


Step 2 — Install the ClickProbe Proxy

The proxy is a single static binary (~15 MB). It runs on your machine, controls a local Chromium browser, and connects to our cloud over a single outbound WebSocket (port 443). No inbound firewall changes needed.

Download

Download and install with one command — macOS/Linux:

curl -fsSL https://clickprobe.ai/install.sh | bash

Windows (PowerShell):

irm https://clickprobe.ai/install.ps1 | iex

Both scripts download the right archive for your OS from clickprobe.ai/downloads/, verify its SHA256 checksum, and put clickprobe-proxy on your PATH. If you’d rather download and extract manually, the published archives are:

OSFile
macOS (Apple Silicon)clickprobe-proxy-darwin-arm64.tar.gz
macOS (Intel)clickprobe-proxy-darwin-amd64.tar.gz
macOS (universal)clickprobe-proxy-darwin-universal.tar.gz
Linux (x86-64)clickprobe-proxy-linux-amd64.tar.gz (or .deb / .rpm)
Linux (ARM64)clickprobe-proxy-linux-arm64.tar.gz (or .deb / .rpm)
Windows (x86-64)clickprobe-proxy-windows-amd64.zip

Every archive ships alongside a SHA256SUMS file — verify before running:

sha256sum --check SHA256SUMS

Install manually (macOS / Linux)

tar -xzf clickprobe-proxy-linux-amd64.tar.gz
sudo install -m 0755 clickprobe-proxy /usr/local/bin/clickprobe-proxy
clickprobe-proxy login

Sign in with the same account you created in Step 1, then keep the proxy connected:

clickprobe-proxy service run

(Leave this running — there is no background service yet in the beta on macOS. On Linux, the .deb/.rpm packages register a real systemd user unit instead; see Onboarding Guide → Step 3.)

Install manually (Windows)

Expand-Archive clickprobe-proxy-windows-amd64.zip -DestinationPath C:\Users\you\bin
C:\Users\you\bin\clickprobe-proxy.exe login
C:\Users\you\bin\clickprobe-proxy.exe service run

Sign in with the same account you created in Step 1. service run keeps the proxy connected — leave it running in the terminal window (there is no background Windows service yet in the beta).

Verify it’s online

After authentication, your terminal shows:

ClickProbe Proxy vX.Y.Z — connected
Account: your@email.com
Proxy ID: prx_xxxxxxxxxxxxxxxx

The dashboard at https://app.clickprobe.ai → Machines shows the proxy as Online (green dot).


Step 3 — Run your first exploration session

  1. Go to https://app.clickprobe.ai → Projects → New Project.
  2. Enter:
    • Name: anything descriptive (e.g., “My App — Staging”)
    • Target URL: the full URL of the web app you want to test — including http://localhost:PORT if you’re testing locally, see Testing Your App on localhost.
    • App description (optional but recommended): 1–3 sentences about what the app does. The more context, the more targeted the bug reports.
  3. Click Save, then Start Exploration.
  4. Choose your proxy machine.
  5. Click Launch — the AI begins exploring. There’s no fixed time limit; it runs until it finishes or your account’s spend cap (set in /app/billing) would be exceeded.

Bugs stream into the Bug Inbox (left nav) as they’re found.


Watching a session locally

Each ClickProbe proxy ships with a local WebUI for watching sessions in real time, without needing to log in to the cloud dashboard. It binds to http://127.0.0.1:9100 (loopback only — never externally reachable) and is protected by a per-startup random token.

Open the WebUI

clickprobe-proxy webui

This prints the URL + token and opens your default browser.

What you’ll see

PagePurpose
DashboardAuth state, tunnel state, Chromium version, port + token.
SessionsLast 50 local sessions; deep-linkable to the cloud dashboard.
Live sessionStep-by-step view of the currently-running exploration, including the latest screenshot the AI has captured. Screenshots appear only when the AI actually takes one — the exploration prompt is deliberately sparing about this to save tokens, so the pane may sit on “Waiting for screenshot…” between captures rather than updating every step.
SettingsEdit <data-dir>/config.yaml.

Sharing a diagnostics bundle

If the proxy misbehaves, email beta@clickprobe.ai with the clickprobe-diag.zip from the Diagnostics page. It contains redacted logs, a redacted copy of your config (the WebUI token is stripped), current state, and version info. See Proxy Connection Troubleshooting for corporate-network and connectivity issues specifically.


Step 4 — Sign the AVV (Data Processing Agreement)

Under GDPR, because ClickProbe processes data from your users’ web sessions on your behalf, kenaro GmbH acts as a data processor. We need a signed Auftragsverarbeitungsvertrag (AVV / DPA) before you handle any personal data in your sessions.

  1. Download the AVV template: AVV template (DRAFT PDF)
  2. Fill in your company details on the signature page.
  3. Sign the document (Adobe Reader, DocuSign, or handwritten scan — any method works).
  4. Email the signed PDF to legal@clickprobe.ai — Subject: AVV — [Your Company Name]
  5. Ingo counter-signs and returns within 1 business day (Mon–Fri).

DRAFT notice: The current AVV template is pending final review by a DACH tech lawyer. Your signature is not void, but the reviewed version will be sent for re-signing within 30 days of lawyer sign-off.


Beta support

  • Feedback, questions, ideas: beta@clickprobe.ai — in English or German.
  • Response target: best-effort, we aim to reply within 1 business day (Mon–Fri). Not a contractual SLA; a beta commitment.


Quick-reference checklist

  • ☐ Account created at app.clickprobe.ai/auth/signup
  • ☐ Email confirmed to beta@clickprobe.ai (triggers €10 credit grant)
  • ☐ clickprobe-proxy downloaded, SHA256 verified, installed
  • ☐ Proxy running and showing “Online” in the dashboard
  • ☐ First exploration session launched
  • ☐ AVV downloaded, signed, emailed to legal@clickprobe.ai
  • ☐ Counter-signed AVV received from kenaro GmbH