kortecxdocs
Beta tasks

Judge a run you did not like

For a beta user: find a run, read what it did, score it, say what was wrong, and run it again with a change.

For a beta user whose App gave an answer that was not what they wanted. After this page you can find that run, read it step by step, put a number and a comment on it, and start it again. Not here: building the App (Apps) or what a run costs (Cost).

Runs are family 01, which reads four bars evidenced in the census at revision 3ec0e4f4, 2026-10-20.

As of 2026-10-21, the command-line and SDK steps on this page use the cloud SDK built from source, until its first publish to the package registries.

Find the run

Open the run list in the console. It shows every run, newest first.

Each run in the list carries an id. Keep it: reading one run takes it.

Read what it did

A run does not disappear when it finishes: the record stays, and you can open it again later.

A run that gave up reads failed in the list of runs, with the reason it failed.

Say what was wrong

Reading a run often ends with a judgement: this answer was good, this one was not. You can record that so it is there next time.

Put a number on it

A score summarises a run's trajectory: whether it reached a terminal, how many turns and tool calls it spent, how much of its budget it burned, and how many proposals were rejected.

Run it again with a change

A run an app started can be forked, which starts a new run: a retry re-runs only the steps that did not finish, and a restart re-runs one step and everything after it, reusing the rest.

What it refuses, and what the exit codes mean

A content reference that is not in the scope you asked for is refused the same way whether it is missing or simply not yours, so nothing here can be used to probe what exists.