Workflows

These workflows are intended for coding agents inspecting an AI SDK DevTools generations.json file.

Inspect What Just Happened

The default command inspects the latest root run with tool calls/results, usage, cache usage, step status, timeline, a narrative summary, final output, and diagnostics. Add --messages <number> when transcript messages are needed.

aisdk-dt --file <path>

Inspect a specific run:

aisdk-dt inspect <runId> --file <path>

Find Recent Runs

aisdk-dt runs --limit 10 --file <path>

Include child runs:

aisdk-dt runs --all --children --limit 20 --file <path>

Find Failed Or In-Progress Runs

aisdk-dt runs --errors --file <path>
aisdk-dt runs --in-progress --file <path>

Inspect One Run

aisdk-dt inspect <runId> --file <path>

Include nested child runs and trace spans:

aisdk-dt run <runId> --include-children --timeline --file <path>

Read The Prompt Transcript

aisdk-dt messages <runId> --limit 12 --max-chars 500 --file <path>
aisdk-dt inspect <runId> --messages 12 --max-chars 500 --file <path>

Filter by role:

aisdk-dt messages <runId> --role user --max-chars 500 --file <path>

Inspect Outputs

List the steps first:

aisdk-dt steps <runId> --file <path>

Then inspect one step:

aisdk-dt output <stepId> --text --max-chars 800 --file <path>

Include reasoning or tools only when needed:

aisdk-dt output <stepId> --reasoning --max-chars 800 --file <path>
aisdk-dt output <stepId> --tools --max-chars 800 --file <path>

Inspect Final Output

aisdk-dt final <runId> --file <path>
aisdk-dt final --latest --max-chars 2000 --file <path>

Use this when the default inspection preview identifies the last meaningful output but exact content matters.

Inspect Tool Calls And Results

aisdk-dt tools <runOrStepId> --file <path>

Include available tool definitions:

aisdk-dt tools <runOrStepId> --available --file <path>
aisdk-dt tools <runOrStepId> --available-only --file <path>

Filter to one tool call:

aisdk-dt tools <runOrStepId> --tool-call-id <toolCallId> --file <path>

Check Token Usage

aisdk-dt usage <runOrStepId> --file <path>

Use this when debugging cost, cache behavior, or unexpectedly large prompts.

Inspect Stream Events

aisdk-dt events <stepId> --last 20 --file <path>
aisdk-dt events <stepId> --chunks --type response.created --file <path>

Use event summaries for aborted or hung streams before reaching for raw payloads. The event diagnosis calls out common patterns such as aborted streamed tool input or missing terminal events.

Query Raw Payloads

Start with a narrow JSON path:

aisdk-dt raw <stepId> --request --json-path 'model' --file <path>
aisdk-dt raw <stepId> --response --json-path 'content[0]' --max-chars 800 --file <path>

Use --full only for deliberate local inspection.

Build A Timeline

aisdk-dt timeline <runId> --file <path>

Use timelines for multi-step runs, nested agent calls, and tool-heavy traces.