workspace.yaml missing git related info

[IeuanWalker]

Since updating from 0.1.32 to 0.2.1, git related settings no longer get added to workspace.yaml, which means the SDK returns null for those values

New workspace file -

id: 55f332f8-57fc-465e-a5f4-319f4f23ea85
cwd: D:\WS\Github-Mine\App
summary: 'review the #file:"D:\\WS\\Github-Mine\\App\\.github\\installers\\windows.nsi" file make sure it implements all the best practices'
summary_count: 2
created_at: 2026-04-06T23:55:32.558Z
updated_at: 2026-04-07T00:23:54.999Z

Old workspace file -

id: a5d30cfc-19e2-4982-9973-1b2ebf4d4d13
cwd: D:\WS\Github-Mine\App
git_root: D:\WS\Github-Mine\App
repository: IeuanWalker/App
branch: main
summary: 'In the #file:"D:\\WS\\Github-Mine\\App\\src\\App\\Components\\Popups\\Settings\\DiagnosticsS...'
summary_count: 1
created_at: 2026-04-05T11:39:59.752Z
updated_at: 2026-04-05T14:04:02.558Z

[github-actions]

Bug Investigation: workspace.yaml missing git context after v0.1.32 → v0.2.1

Thanks for the detailed report. I investigated the relevant code and confirmed this is a bug — specifically a regression in how the session's working directory is communicated to the CLI for git context detection.

What I investigated

• nodejs/src/client.ts — the createSession and resumeSession RPC call construction
• nodejs/src/types.ts — SessionConfig.workingDirectory and SessionContext types
• nodejs/src/generated/session-events.ts — the session.start event schema (includes context.gitRoot, context.repository, context.branch)
• python/copilot/client.py — same pattern in Python SDK
• CHANGELOG.md — v0.2.0 and v0.2.1 changes

Root cause

The workspace.yaml file and the session.start event's context block (which contains gitRoot, repository, branch) are populated by the CLI based on the session's working directory. In the session.create RPC, the SDK sends the optional workingDirectory parameter from SessionConfig.

The issue is here:

// client.ts — session.create RPC payload
workingDirectory: config.workingDirectory,   // undefined if not set by caller

And in Python:

if working_directory:
    payload["workingDirectory"] = working_directory  # only sent if explicitly set

In v0.2.x, if workingDirectory is not explicitly provided in SessionConfig, the field is omitted from the session.create RPC call entirely. The CLI appears to require an explicit workingDirectory to perform git context resolution — without it, git fields (git_root, repository, branch) are omitted from workspace.yaml and the session.start context.

In v0.1.32, the CLI likely fell back to its own process cwd for git detection (which is set from CopilotClientOptions.cwd). That implicit fallback is no longer happening.

Expected fix

The SDK should default workingDirectory in the session.create RPC to the client's cwd (from CopilotClientOptions) when not explicitly provided by the caller, so git detection continues to work without requiring callers to opt in. Alternatively, the CLI's fallback behavior should be restored.

Generated by Bug Handler for issue #1027 · ◷

[IeuanWalker]

I'm using the .NET SDK

[IeuanWalker]

Its wierd, when you create the session you get the git related properties back, but they arnt ever added to the workspace.yaml as before, so when you go to resume the session later on the git properties are then returned as null

[stephentoub]

Generated by Copilot.

I believe this has already been fixed/addressed.

Fix summary: Session workspace metadata now includes the git/workspace context needed by consumers of workspace.yaml.

Closing this as completed.