Examples/qPCR run

qPCR run

Created from a prompt

OpenCode (DeepSeek V4 Pro via OpenRouter) in a Vercel Sandbox. Starter only (AGENTS.md, serve.py, player/, helpers/dom/view_kit). No hardcoded demo code. Cursor did not edit workspace/.

2026-10-15 · task lxEFIW9yJWsY · opencode · openrouter/deepseek/deepseek-v4-pro-0813

The prompt

Build a qPCR review screen for a small plate. One row is the target gene, one row is a reference gene. Each row has a standard curve over several dilutions, a control in triplicate, a treated sample in triplicate, and a no-template well. Show the amplification curves and the melt curves, and the cycle where each well crossed the line.

I call the run good, or I name one fault: primer dimer, contamination in the no-template well, a standard curve that amplified poorly, inhibition, or a pipetting miss in a triplicate. If the run is good, I also report how many times higher the target is in the treated sample, after accounting for the reference. On a bad run, naming the fault is the whole score. On a good run, calling it good is only part, and the fold change is the rest. A close fold change should count more than a wild one. Do not mark the fault on the plate before I submit. Several runs, one per fault and a clean one. The same run should be the same curves.

Live environment

Running the prompt-created workspace on this machine — not a mock. Save an episode, then open Replay below to scrub the timeline.

opening · 0 ms

Generated workspace

Exact files the agent wrote — not rewritten by hand.

# AI : shared Action contract — the page posts {"move": "..."}; keep this shape.
from pydantic import BaseModel


class Action(BaseModel):
    move: str