Skip to content

[Bug] Launcher ignores configured defaultDirectory when creating chats#421

Open
Zsailer wants to merge 1 commit into
jupyterlab:mainfrom
Zsailer:fix/launcher-uses-default-directory-oss
Open

[Bug] Launcher ignores configured defaultDirectory when creating chats#421
Zsailer wants to merge 1 commit into
jupyterlab:mainfrom
Zsailer:fix/launcher-uses-default-directory-oss

Conversation

@Zsailer

@Zsailer Zsailer commented Apr 30, 2026

Copy link
Copy Markdown
Member

When a defaultDirectory is configured (via settings or server config), chats created from the side panel correctly land in that directory. But chats created from the launcher, menu, or command palette ignore it and use the file browser's current directory instead.

The createChat command was only checking inSidePanel to decide whether to use the configured directory. Now it also checks whether a defaultDirectory is configured -- if one exists, it's used regardless of where the chat was created from. The file browser fallback only kicks in when no default is configured.

Includes a UI test that configures a default directory, creates a chat from the launcher, and verifies it lands in the right place.

@github-actions

Copy link
Copy Markdown
Contributor

Binder 👈 Launch a Binder on branch Zsailer/jupyter-chat/fix%2Flauncher-uses-default-directory-oss

Previously, only chats created from the side panel respected the
configured defaultDirectory. Chats created from the launcher, menu,
or command palette used the file browser's current directory instead.

Now all paths use defaultDirectory when one is configured, falling
back to the file browser path only when no default is set.

Adds a UI test verifying that the launcher creates chats in the
configured directory.
@Zsailer Zsailer force-pushed the fix/launcher-uses-default-directory-oss branch from a14e121 to d55ab3b Compare April 30, 2026 20:50
@Zsailer Zsailer added the bug Something isn't working label Apr 30, 2026
@Zsailer Zsailer marked this pull request as ready for review April 30, 2026 20:54
@brichet

brichet commented May 3, 2026

Copy link
Copy Markdown
Collaborator

Thanks @Zsailer for working on this.

This PR seems to revert the behavior introduced in #238, so I believe that it was expected.

cc. @andrii-i @ellisonbg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants