Inspect a run
See what your Apps did: the run list, each run read back step by step, a run followed live, and your feedback on the result.
Kortecx keeps a record of every run. A run does not disappear when it finishes: the record stays, and you can open it again later.
This page is the tour of the ways to read that record. Most of it is read-only — you are looking at what already happened.
Two ids you will keep seeing
An instance id (32 hex characters) names one run. A step id (64 hex characters) names one step inside a run.
Start from the list of runs
If you do not have an instance id in hand, list the runs that were recorded. They come back newest first.
One run, step by step
A run is a set of steps with edges between them. The console draws that shape: which step ran, what it reached for, what came back, what was refused, and where it stopped.
The reasoning trail
When a run reasons in a loop — think, act, observe, think again — each turn is recorded, not just logged. Reading the turn-by-turn trail is limited to the platform's own engineers today; a run's summary shows each step's state and the tools it called.
Reading the actual output
A run's record points at each step's output rather than carrying it, which is why a run stays quick to read however large its outputs are. A run's summary shows each step's output, up to its first 280 characters.
Tokens and time
Each run's own record carries its token counts and how long it took. For what a run costs, see Cost.
Failed runs
A run that gave up reads
failed in the list of runs, with the reason it failed.
Run it again with a change
Reading a run often ends with wanting to try it differently. 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.