{"version":"2.1.300","anchor":"credential-file-descriptor-reads-now-record-their-source","canonical_anchor":"credential-file-descriptor-reads-now-record-their-source","heading":"Credential reads now record where the credential came from","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/credential-file-descriptor-reads-now-record-their-source","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Credential reads now record where the credential came from\n\nWhen Claude Code reads a credential or token, it now records which route it used, such as a file or a passed-in descriptor\n\n**What**\n\nWhen Claude Code reads a credential or token, it now records how it got it. The routes are:\n\n- `file`\n\n- `descriptor_direct`\n\n- `descriptor_by_path`\n\n- `file_after_socket`\n\n- `file_after_failed_read`\n\nA file descriptor is a handle a program can be given to read data without opening a named file. A related change adds a tunnel input for remote sessions.\n\n**Why**\n\nThis is for troubleshooting only and does not change how sign-in works.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}