Add session rename API parity with Copilot CLI (/rename and /session rename)

[brunoborges]

Copilot CLI supports renaming the active session via /rename <name> (alias of /session rename <name>), but this capability is not exposed in the SDK APIs.

Please add first-class session rename support in copilot-sdk so applications can rename sessions programmatically without invoking CLI commands manually.

Problem

Today, SDK consumers cannot rename the current session after creation. CLI users can, through:

• /rename <name>
• /session rename <name>

Both commands behave the same way.

Why this matters

• Increases feature parity between CLI and SDK experiences
• Supports chat UIs/workbenches that allow conversation renaming
• Avoids brittle workarounds that shell out to CLI command text
• Improves metadata management for long-lived and resumed sessions

Requested capability

Add APIs to name / rename a session. Suggestions:

• add name to SessionMetadata
• session.rename(name)
• session.getName() returns the name of the session
• client.renameSession(sessionId, name)
• client.getSessionName(sessionId) returns the name of the session
• client.listSessions() should include names, if set, in the SessionMetadata objects / data structures

Expected behavior

• Renames the target/current session
• Follows the same validation rules as CLI rename commands
• Returns success and/or updated session metadata
• Works consistently for active and resumed sessions

Acceptance criteria

• Session rename is available through the official SDK API surface
• Behavior matches CLI (/rename and /session rename)
• Documented in SDK docs with examples
• Covered by tests (including invalid names and resumed sessions)

[github-actions]

Thanks @brunoborges for opening this enhancement request!

This is a clear and well-documented feature request to add session rename capabilities to all SDK implementations, bringing them to parity with the CLI's /rename and /session rename commands.

Labels applied:

• enhancement — New feature request
• sdk/dotnet, sdk/go, sdk/nodejs, sdk/python — Applies to all SDK implementations

The suggested API surface (session.rename(), client.renameSession(), etc.) and acceptance criteria are helpful for implementation planning. This would indeed improve feature parity and support common use cases like chat UIs that allow conversation renaming.

AI generated by Issue Triage Agent