feat(command-center): choose folder when opening a terminal

[MattPua]

Problem

When multiple folders are open, opening a terminal from the command center silently opens it in whichever folder was accessed most recently, with no way to choose.

Changes

CleanShot.2026-07-08.at.11.49.18.mp4

• Opening a terminal from the command center's "Add task" popover now shows a folder picker when more than one folder is open.
• With 0 or 1 folder, behaviour is unchanged (opens in the single / most-recent folder).
• The chosen folder is persisted with the cell (survives reload) and shown in the terminal header badge.

How did you test this?

• @posthog/core command-center unit tests (47 passed), including added round-trip tests for the terminal cell value encoding (id + optional cwd).
• Typecheck clean on all touched files.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit 4441380.}

[greptile-apps]

_{Reviews (1): Last reviewed commit: "style: format setTerminalCell signature" | Re-trigger Greptile}

[greptile-apps]

The folder picker filters only by folder.name, but each item displays folder.path as its description. A user who spots a path they want and tries to type a fragment of it will see "No matching folders" even though the folder is visible in the list. Matching both name and path would make the search behave consistently with what users see.

Suggested change

	getValue={(folder) => folder.name}
	getValue={(folder) => `${folder.name} ${folder.path}`}

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[github-actions]

Clean feature addition with correct URI-encoding for the colon-separator protocol and a test that validates the round-trip with a colon-containing path. The unresolved bot comment is a P2 UX suggestion (search filters by name but displays path), not a correctness or safety issue.