What to do:
Evaluate whether developers can quickly understand AgentGrid's core value as a visual workspace for running multiple AI coding agents (Claude, Codex, OpenCode, etc.) and locate the primary call-to-action without signing in.
Navigate to https://agentgrid.sh/ and describe what you see in the hero section and the main headline about running coding agents
Locate and read the list of supported AI agent harnesses displayed on the homepage and note which ones are mentioned
Find and click the 'Demo' link in the navigation menu to preview the visual workspace without signing in
Scroll through the homepage to identify the primary call-to-action button and describe its label and placement
Locate the 'Docs' link and verify it opens documentation about AgentGrid's features and capabilities
Evidence: Record a screen video narrating your observations about the homepage layout, agent harness visibility, Demo accessibility, and CTA prominence. Write 2-3 sentences summarizing whether the value proposition (visual workspace for multiple AI agents) is immediately clear and whether Demo or Download are easy to find.
Keep the test to five minutes. Do not sign in, enter private credentials, complete a purchase, or make destructive changes.
Send video evidence for every issue in the accepted tester chat.
Record your screen and microphone audio for the full test. Narrate your actions, every error you find, and anything confusing, poor, or worth improving.
Attach the narrated video as an MP4, MOV, or WebM no larger than 75 MB, plus at least one representative screenshot.
For each issue include a short title, a severity (critical/high/medium/low), and exact steps to reproduce.
Submissions are reviewed automatically. $4.00 is released per accepted submission.
What you must do to be paid
Before you apply
Access to a device that can open https://agentgrid.sh/
Evaluate whether developers can quickly understand AgentGrid's core value as a visual workspace for running multiple AI coding agents (Claude, Codex, OpenCode, etc.) and locate the primary call-to-action without signing in.
1. Navigate to https://agentgrid.sh/ and describe what you see in the hero section and the main headline about running coding agents
2. Locate and read the list of supported AI agent harnesses displayed on the homepage and note which ones are mentioned
3. Find and click the 'Demo' link in the navigation menu to preview the visual workspace without signing in
4. Scroll through the homepage to identify the primary call-to-action button and describe its label and placement
5. Locate the 'Docs' link and verify it opens documentation about AgentGrid's features and capabilities
Evidence: Record a screen video narrating your observations about the homepage layout, agent harness visibility, Demo accessibility, and CTA prominence. Write 2-3 sentences summarizing whether the value proposition (visual workspace for multiple AI agents) is immediately clear and whether Demo or Download are easy to find.
Keep the test to five minutes. Do not sign in, enter private credentials, complete a purchase, or make destructive changes.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 75 MB with spoken microphone narration throughout, plus at least one representative screenshot. Captions, written narration, and on-screen text do not replace the required microphone audio.
5Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
•
Access to a device that can open the target URL
•
Report every issue with a severity and exact reproduction steps
•
Only submit evidence you captured yourself during this run