# feat\(analytics\): credit v2 threads and turns to the starting client \(\#7774\) · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/8622f36fbb8098569023342ec42e1a68ca29e193)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 8622f36fbb8098569023342ec42e1a68ca29e193

Requested commit: 8622f36fbb8098569023342ec42e1a68ca29e193

Commit: 8622f36fbb8098569023342ec42e1a68ca29e193

Tree: 319ea2426de8ffc7dbc11512334ab1ab9f9b2033

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(analytics): credit v2 threads and turns to the starting client (#7774)

Main records which client surface started each thread and turn; the v2
dispatch path replaced the v1 handler that did the recording, so v2
environments only reported connections. The v2 RPC layer now records
client.thread.started on thread launches (plus client.turn.requested when
the launch carries an initial message) and client.turn.requested on
message dispatches, using the connection's announced origin. Recording is
best-effort — attribution can never fail the user's command.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [ea87825eea9948a55dccaadea619f7ef002aadcf](https://git.cafe/pingdotgg/t3code/commit/ea87825eea9948a55dccaadea619f7ef002aadcf?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/8622f36fbb8098569023342ec42e1a68ca29e193?format=markdown)