{"version":"2.1.317","anchor":"verbose-api-request-log-includes-stated-effort","canonical_anchor":"verbose-api-request-log-includes-stated-effort","heading":"Verbose API request logs now show the effort level that was asked for","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/verbose-api-request-log-includes-stated-effort","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Verbose API request logs now show the effort level that was asked for\n\nAt the verbose log level, the API request detail line now includes a `stated_effort` field\n\n**What**\n\nWhen logging is set to verbose, each detailed record of a request sent to the API now includes a `stated_effort` field. It shows the effort level set on the last message, which controls how much work the model puts into its answer. Before, these records listed the model, thinking, output settings, temperature and beta features only.\n\n**Why**\n\nThis makes it easier to check which effort level a request actually asked for when debugging.\n\n- Area: Internals\n- Names: `stated_effort`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}