Skip to content

fix: agents not appearing on Linux Mint (and likely macOS) when no folder is open#70

Open
d4rkd0s wants to merge 2 commits intopablodelucca:mainfrom
d4rkd0s:fix/linux-macos-no-workspace-support
Open

fix: agents not appearing on Linux Mint (and likely macOS) when no folder is open#70
d4rkd0s wants to merge 2 commits intopablodelucca:mainfrom
d4rkd0s:fix/linux-macos-no-workspace-support

Conversation

@d4rkd0s
Copy link

@d4rkd0s d4rkd0s commented Mar 5, 2026

Confirmed working on Linux Mint. If you launch VS Code without a folder
open (just `code` on its own, which is the natural way to open it on
Linux and macOS), clicking + Agent would start Claude in a terminal but
no character would ever appear in the office.

The extension was silently bailing out because it couldn't determine a
project directory when no workspace folder was set. The fix falls back
to the home directory, which is exactly where Claude Code writes its
session files in that scenario. macOS should work too for the same
reason. If any Mac users run into issues, drop a comment and we can
patch it quickly.

Windows behavior is unchanged.

Tested on

  • Linux Mint / VS Code 1.109.5
  • Open VS Code with no folder, open Pixel Agents panel, click + Agent
  • Before: office renders, nothing spawns
  • After: character appears and walks around normally

d4rkd0s and others added 2 commits March 4, 2026 19:07
When VS Code is launched without a folder (e.g. bare `code` command,
common on Linux and macOS), `workspaceFolders` is empty and
`getProjectDirPath()` returned null. This caused `launchNewTerminal()`
to bail out early before sending `agentCreated` to the webview, so no
character ever appeared despite the terminal being created.

Fix: fall back to `os.homedir()` in both `getProjectDirPath` and the
`cwd` used for terminal creation. This matches the directory Claude Code
itself uses when started with no explicit working directory, ensuring the
extension correctly locates the JSONL transcript files.

Windows behavior is unchanged: workspaceFolders is always populated in
the common Windows workflow, so the fallback is never reached there.

Co-Authored-By: Logan <d4rkd0s@github.com>
- Add platform support note to Requirements section
- Replace "Windows-only testing" known limitation with a
  helpful tip for Linux/macOS users launching VS Code
  without a workspace folder open

Co-Authored-By: Logan <d4rkd0s@github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant