Claude Code Trace
It evaluates agent behavior with a fixed set of interpretable metrics plus action-window questions, while minimizing or explicitly confirming session data before sending.
It evaluates agent behavior with a fixed set of interpretable metrics plus action-window questions, while minimizing or explicitly confirming session data before sending.
Claude Code Trace prepares a locally redacted session efficiency input and sends it to Jev after the user selects Analyse efficiency and confirms the payload. Ten base metrics use Noul questions and thinkingBalance uses a rubric Score; additional Noul questions are generated for bounded action windows. Typed probabilities and rubric positions are converted into dashboard metrics and trace-linked findings.
Did the agent make steady, meaningful progress toward the user’s task?
Redacted EfficiencyInput: base questions assess session/task signals; generated window questions are limited to chunks of six actions, with up to twelve windows.
Were the tool calls useful and proportionate to completing the task?
Redacted EfficiencyInput: base questions assess session/task signals; generated window questions are limited to chunks of six actions, with up to twelve windows.
Does the trace indicate that the user’s requested task was completed successfully?
Redacted EfficiencyInput: base questions assess session/task signals; generated window questions are limited to chunks of six actions, with up to twelve windows.
Choose Analyse efficiency for a Claude Code session.
Inspect locally redacted data and explicitly confirm sending.
Send state and generated metric/window questions to System One.
Review dashboard metrics and trace annotations; re-analysis replaces prior result for the session.
It evaluates agent behavior with a fixed set of interpretable metrics plus action-window questions, while minimizing or explicitly confirming session data before sending.