Run one of wtf's : commands on the workspace: decode, protocol, rows, cursors (help commands). Answers with the rows it added or removed; undo takes a step back.

When a search expression holds, as a table of times; show adds values, count_only counts. With @<clock> first, a match is a cycle whose ending edge samples it true (@clk x: the cycles x is high), reported at the cycle's start; without, where it becomes true (rose(x): x's edges). A bus: decode it (help decode).

The reference for one concept: its form, recipes and details. Topics: names, patterns, times, radix, expressions, decode, records, workspace, commands; without a topic, lists them. Call it when an argument's doc or an error isn't enough.

The open waveform: file, time range, signals, and the interfaces a built-in protocol decodes, each with its decode line.

Choose the trace the other tools work on: trace opens a waveform (VCD, FST or GHW file) in a new workspace; session goes back to one of your workspaces (sessions); neither re-reads the current one's file, after the simulation ran again, keeping its rows. Answers with info, which lists the interfaces to decode.

Show your workspace to the user as evidence: it replaces the view of every wtf window on this trace (theirs is one u away), or with none open writes <trace>.agent.session.toml for them to open.

What can be decoded; with a name, its roles, params, streams and fields (help decode).

Records of a decoded stream, or of several in start order (a decode's name: its results), as a table: n, start (the rising edge that starts the record's first clock cycle), end (the edge that samples its last) and the fields; where, group_by, count_only (help records).

Draw signals over a time range as text, as wtf's screen does; without signals, the workspace.

The open sessions: the user's wtf windows and agents' workspaces, with ids and traces, yours marked. open starts one or switches between yours.

Search the waveform's design, scopes (instances) and signals, by a regex in slashes found anywhere in the path, as grep does (/uart/, /_valid$/); none lists it all, folded to fit.

What the user is looking at in their wtf window on this trace, worded as view words the workspace, to start from what they see. Changes nothing unless adopt: that replaces the workspace's rows, cursors and range with the user's, dropping yours; command undo brings them back.

Values of signals from from to to: the value at from, then each change, as time value lines; omit to for one time. A struct or array also lists its fields. For when something happens, find.

Describe the workspace in words: rows, cursors with the time between them, visible range. Drawn: render; the user's window: user_view.

Set up the whole workspace in one call: rows, cursors, range, decodes (help workspace). Answers as view does.