Jev debugger next step

Choose a debugger step for the evidence you need

Describe the paused state and investigation goal. Compare Step into, Step over, Step out and a configured breakpoint before issuing any debugger command.

debugger next stepLive API
Try an example

The needed observation is inside the call.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Choose the debugger action for the supplied evidence goal.

Decision rules and labels
Step intoStep overStep outContinueReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

This demo recommends one navigation command from the supplied state. It does not attach to a process, inspect variables or run an expression.

An explicit evidence goal distinguishes commands that would otherwise all be technically available. Keep the paused line, stack context and prerequisites together.

The linked debugger strategy uses Jev for bounded action selection and another model for generated parameters. This page covers only the navigation subset and does not reproduce that agent.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of choosing one tool from the supplied alternatives
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for debugger next step.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Describe the paused state and investigation goal.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Step into, Step over, Step out, Continue, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Inspect parser internalsStep into100%
Observe known helper resultStep over100%
Return to callerStep out100%
Reach known breakpointContinue100%
No investigation goalReview100%
Missing breakpointReview99.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Debugger next step: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Explaining debugger navigation using concrete paused-state examples.
  • Testing a bounded action selector before connecting runtime controls.
  • Comparing navigation commands against an explicit evidence-collection goal.

Outside this demonstration

  • Executing commands or creating breakpoint coordinates.
  • Claiming a bug is fixed because the next action seems appropriate.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does Step over skip executing the call?

No. It normally executes the call without stepping through its internals, then pauses at the next relevant point. This page only selects the label.

Why is there no Finish option?

This exercise chooses how to gather another observation. Confirming a cause or ending an investigation needs a separate evidence contract.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.