You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just installed newly openchamber.AppImage on linuxmint, when i want to create worktree i got message:
failed to create worktree
Unable to query remote origin
For the maintainer: not-ours — this is a git network/auth failure, not an OpenChamber code bug.
The error "Unable to query remote origin" is generated at service.js:4282/4299 when the validation step runs git ls-remote --heads origin refs/heads/<branch> to confirm the remote branch exists before creating the worktree. If that git command fails (network down, no SSH keys, expired token, wrong remote URL), OpenChamber surfaces this message.
The code path is intentional: withWorktreeRemoteStartRef in worktreeCreate.ts:130 automatically resolves the start ref to a remote tracking branch when the user is on a branch with an upstream that is not ahead — so this error can appear even for a "simple" worktree creation from the current branch.
What the reporter can try:
Run git ls-remote origin from the terminal in their project directory — if that fails, the remote is unreachable from their machine.
This was fixed by #3457 and ships in v2.1.1: creating a worktree no longer asks the remote first, it checks local branches only. If it still fails there, comment and I'll reopen it.
Activity
openchamber-bot commentedon Sep 15, 2026
For the maintainer: not-ours — this is a git network/auth failure, not an OpenChamber code bug.
The error "Unable to query remote origin" is generated at
service.js:4282/4299when the validation step runsgit ls-remote --heads origin refs/heads/<branch>to confirm the remote branch exists before creating the worktree. If that git command fails (network down, no SSH keys, expired token, wrong remote URL), OpenChamber surfaces this message.The code path is intentional:
withWorktreeRemoteStartRefinworktreeCreate.ts:130automatically resolves the start ref to a remote tracking branch when the user is on a branch with an upstream that is not ahead — so this error can appear even for a "simple" worktree creation from the current branch.What the reporter can try:
git ls-remote originfrom the terminal in their project directory — if that fails, the remote is unreachable from their machine.git credential fill).git remote get-url origin.No OpenChamber code change needed — the underlying
git ls-remotefailure is real and correctly surfaced.erikdemarco commentedon Sep 16, 2026
testing the suggestion gives this result:
yulia-ivashko commentedon Oct 9, 2026
This was fixed by #3457 and ships in v2.1.1: creating a worktree no longer asks the remote first, it checks local branches only. If it still fails there, comment and I'll reopen it.