{"version":"2.1.247","anchor":"device-flow-docs-describe-the-surface-parameter-claude-code-","canonical_anchor":"device-flow-docs-describe-the-surface-parameter-claude-code-","heading":"Device-flow docs describe the surface parameter Claude Code sends","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/device-flow-docs-describe-the-surface-parameter-claude-code-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Device-flow docs describe the surface parameter Claude Code sends\n\nOAuth docs now note that Claude Code sends a surface parameter and its own user agent.\n\n**What**\n\nThe OAuth device-authorization documentation for third-party server implementors now records that the request body may carry a `surface` extension parameter, that Claude Code sends `surface=claude_code`, and that it sends a `claude-code` user agent on metadata, device, token and refresh requests.\n\n**Evidence**\n\n`surface=claude_code`\n\n- Area: Auth\n- Names: `surface=claude_code`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}