feat: add PROJECTS_EXCLUDED_PATHS to hide unwanted projects from /projects

[Johell1NS]

Motivation

The /projects command lists every project OpenCode has ever tracked (the whole worktree of every session). When a user works from many paths — including system or home directories — the list gets polluted with projects they never want to switch to. This makes switching projects via /projects slower and noisy.

Change

Adds an optional PROJECTS_EXCLUDED_PATHS env var (comma-separated absolute paths, same format as OPEN_BROWSER_ROOTS). Any project whose worktree matches one of these paths is filtered out of the /projects list.

PROJECTS_EXCLUDED_PATHS=/home/me/.config/opencode/skills,/home/me/backup

The filter is applied after the existing linked-worktree hiding, keeps the previous behaviour when the var is unset, and is logged for transparency.

Files changed

• src/config.ts — parse PROJECTS_EXCLUDED_PATHS into config.bot.excludedProjectPaths
• src/app/services/project-service.ts — filter resolved projects
• .env.example — document the new variable
• tests/config.test.ts — cover env parsing (unset, comma-separated, whitespace/empty entries)
• tests/app/services/project-service.test.ts — cover filtering (unset, single/multiple paths, applied after linked-worktree hiding)

Testing

npm run lint && npm test && npm run build all pass (1224 tests).

[kamysheblid]

In an earlier PR maintainer had the idea of using menus instead which might be better, so there would be an archive button in the menu when you first run /projects that will remove projects from being displayed in the menu until they are opened again using the directory.

The main issue is that you might implement it and maintainer might not accept the PR.

[grinev]

@Johell1NS thanks for PR

Can you please fix one issue before merging

Major: src/app/services/project-service.ts:71-74 compares excluded paths with raw string equality. This can fail for valid equivalent
paths, such as /home/user/repo vs /home/user/repo/, or C:\Repo vs C:/Repo on Windows. The existing worktreeKey helper already
normalizes these differences, but it is not used here.

Please normalize both configured paths and project worktrees before comparing them, and add tests for trailing separators and Windows
path casing/separators. Otherwise, configured projects may remain visible in /projects.

[Johell1NS]

Hi @grinev, thanks for the review!

Fixed the Major issue you flagged in src/app/services/project-service.ts:71-74.

Now both the configured PROJECTS_EXCLUDED_PATHS and the project worktrees are normalized via the existing worktreeKey() helper before comparison. This correctly handles:

• trailing separators (/home/user/repo vs /home/user/repo/)
• Windows separators (C:\Repo vs C:/Repo)
• case-insensitivity on Windows (C:\Repo vs c:\repo)

Used a Set<string> of normalized keys for efficiency and updated the hiddenExcluded logging.

As requested I added dedicated tests in tests/app/services/project-service.test.ts:

• filtering when excluded path has trailing slash
• filtering when worktree has trailing slash
• Windows casing differences
• Windows mixed separators
• combined trailing + casing case

Verification locally: npm run lint && npm test && npm run build all passed (1229 tests, +5 new).

Fix published in commit 4d6767c on branch feat/projects-excluded-paths. Let me know if you'd like any further adjustments!