feat(desktop): add Fork to the Open menu#2354
Open
eodwyrd wants to merge 2 commits into
Open
Conversation
Adds Fork (the Git client) as a target in the workspace Open dropdown so you can jump from a workspace straight into Fork with the repo open. Fork is a repository GUI, so it always opens the workspace root and ignores any file path. It launches through the existing openMacApplication runtime helper (open -a Fork <repo>) - the same mechanism Cursor/Zed use when their CLI is absent - so there are no runtime changes, and it only appears when Fork.app is installed. Bundles a 64x64 Fork icon alongside the other editor-target icons. macOS only for now; Windows can follow once its launcher is verified. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
eodwyrd
force-pushed
the
feat/open-in-fork
branch
from
July 23, 2026 15:23
0674575 to
e31f72b
Compare
eodwyrd
added a commit
to eodwyrd/paseo
that referenced
this pull request
Jul 23, 2026
eodwyrd
added a commit
to eodwyrd/paseo
that referenced
this pull request
Jul 23, 2026
eodwyrd
marked this pull request as ready for review
July 23, 2026 15:28
Contributor
|
| Filename | Overview |
|---|---|
| packages/desktop/src/features/editor-targets/targets/fork.ts | Implements Fork detection and workspace-root launching consistently with the existing editor-target runtime. |
| packages/desktop/src/features/editor-targets/registry.ts | Registers the new Fork target in the existing target list without altering registry behavior. |
| packages/desktop/src/features/editor-targets/registry.test.ts | Covers macOS availability, off-platform hiding, missing-app handling, descriptor output, and workspace-root launching. |
| packages/desktop/assets/editor-targets/fork.png | Adds the valid PNG asset automatically included by the existing editor-target resource mapping. |
Reviews (1): Last reviewed commit: "feat(desktop): add Fork to the Open menu" | Re-trigger Greptile
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Fork (the Git client) as an option in the workspace Open dropdown, so you can jump from a workspace straight into Fork with the repo open.
Why
Finder and the editors are already there, but if you live in a Git GUI there's no quick way over. This scratches that itch. Related to #261 (more Open targets) — though that one's about editors, and this is a Git client, so figured it's worth its own small thing.
How it works
Fork's a repository GUI, so it always opens the workspace root (never a single file). It launches via the existing
openMacApplicationruntime helper — literallyopen -a Fork <repo>— the same mechanism Cursor/Zed already use when their CLI isn't around. No runtime changes needed, and it only shows up whenFork.appis actually installed.I went with
open -a Forkover Fork'sforkCLI on purpose: the CLI is opt-in (you have to install it separately) and cwd-based, whereas the app bundle is always there once Fork's installed and reliably opens the repo as a tab.Scope
macOS only for now — that's what I could actually test. Windows Fork launching can be a follow-up once someone can verify it.
One small quirk worth flagging: if Fork is fully quit, launching it opens the repo tab but Fork's own session-restore focuses whatever tab was last active rather than the one you just opened (it's still there, one click away). When Fork's already running it focuses the repo correctly. That's Fork's behaviour, not something we can override cleanly.
Screenshots (desktop / macOS)
Fork in the Open dropdown, with its icon:
The workspace it opens from:
How I verified
npm run typecheck,npm run lint,npm run format, targeted vitest — all green.