feat: add clientName to SessionConfig and ResumeSessionConfig

[Copilot]

Tracks official SDK PR #510. The CLI protocol already supports clientName on session.create and session.resume requests, but the SDK types were not exposing it. clientName identifies the calling application and is forwarded as part of the User-Agent header.

Changes

• SessionConfig — added optional clientName field (after sessionId, before model) in constructor, fromArray(), and toArray()
• ResumeSessionConfig — same, as first parameter (matching official SDK ordering)
• Tests — updated SessionConfigTest and ResumeSessionConfigTest to cover the new field in full-field and toArray scenarios

Usage

Copilot::run(
    prompt: 'Hello',
    config: new SessionConfig(clientName: 'my-laravel-app'),
);

config: new ResumeSessionConfig(clientName: 'my-laravel-app'),

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/copilot_internal/user
  • Triggering command: /home/REDACTED/.local/bin/copilot copilot --headless --stdio --log-level info (http block)
  • Triggering command: /home/REDACTED/.local/bin/copilot copilot --headless --stdio --log-level info stty stty n/stty (http block)
  • Triggering command: /home/REDACTED/.local/bin/copilot copilot --headless --stdio --log-level info pilot-sdk/vendor/bin/stty stty ndor/bin/stty (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.