bug: Workspace is incorrect when switching to a non-Local backend

[jpelletier1]

When switching from a Local backend -> custom backend, such as one hosted on a home server, the workspace defaults to the file path of the Local server.

Example:

Let's say I have two backends:

• Local (default). This is my local file system. The Home directory is /Users/joepelletier
• Home Server. This is an additional backend I added. The Home directory here is /Users/homeadmin

When I switch from Local --> Home Server, the Home Server workspace modal displays this error (see screenshot).

Expected result:
Workspace should default to /Users/homeadmin

[CryptoJones]

This is already fixed on main — fix shipped in #306 (merged 2026-05-11), which:

1. Added the active backend's id and orgId to the React Query keys for both useHomeDirectory and useSearchSubdirs (so switching backend invalidates the cache for the next fetch), and
2. Added a reset useEffect in FolderBrowserModal keyed on [active.backend.id, active.orgId] that nulls currentPath on switch, letting the open/init effect re-seed from the new backend's homeData.home.

Both pieces are still in place: src/components/features/home/workspace-dropdown/folder-browser-modal.tsx:118-120 and src/hooks/query/use-search-subdirs.ts:24, 35.

The existing __tests__/components/features/home/workspace-selection-form.test.tsx didn't drive a backend switch, so the fix had no regression coverage. #713 adds a focused FolderBrowserModal test that switches active backend mid-test and asserts the breadcrumb re-seeds to the new home (and was verified to fail when the reset effect is removed).

Closing as already-fixed; PR #713 backfills the regression test.

[jamiechicago312]

Great issue for new contributors! 🎉

Why this is a good first issue:
This is a concrete frontend bug with a clear repro: switch from one backend to another and the workspace picker shows data from the wrong backend. The likely fix is bounded to query/cache scoping rather than a large architectural rewrite, so it is a good way to learn how Agent Canvas handles backend-aware state.

Instructions for tackling this issue:
The first places to inspect are:

• src/hooks/query/use-local-workspaces.ts
• src/hooks/query/use-resolved-workspaces.ts
• src/hooks/query/query-keys.ts
• src/hooks/query/use-settings.ts (good example of a backend-aware query key)
• src/components/features/home/workspace-selection-form.tsx

A strong hypothesis is that workspace queries are cached under keys that do not include the active backend identity, so data from the local backend can leak into a different backend after a switch.

A good implementation plan is:

1. Reproduce the issue by switching between two backends with different home/workspace roots.
2. Check the React Query keys for workspace-related queries and compare them with backend-aware hooks such as useSettings().
3. Update the workspace query keys (and any related invalidation logic) so cached results are scoped by backend id / org when appropriate.
4. Add a regression test — either at the hook level or through workspace-selection-form — that switches the active backend and verifies the second backend gets fresh workspace data instead of reusing the first backend's cache.

Getting started:
You can work on this issue without asking for it to be assigned to you. Feel free to open a pull request directly!

Need help?
Join our Slack community: https://go.openhands.dev/slack

This comment was created by an AI agent (OpenHands) on behalf of the maintainers.

[CryptoJones]

@jamiechicago312 Please read me comment above.