[Bug]: Incorrect workspace detection when using git worktrees

[samneirinck]

What happened?

We have an unusual setup where we have a main repository with a bunch of configuration files, and a gitignore which ignores almost everything.

Inside that cloned folder, we git clone other repositories which can then reference the configuration files from the parent folder.

When using this approach in combination with git worktrees, auggie detects the main (config) repository as the workspace root, not the worktree folder you're currently in.

What did you expect to happen?

Workspace detection correctly identifies the current (git worktree) folder as a workspace, not the git folder a few levels up.

Steps to reproduce

git clone https://github.com/augmentcode/auggie
cd auggie/
git clone --bare https://github.com/github-samples/pets-workshop
cd pets-workshop.git/
git worktree add test
cd test
auggie

The working directory is auggie, not auggie/pets-workshop.git/test.

Auggie version

0.16.2 (commit 76169a3e)

Request ID

n/a

Environment details

Environment

• OS: MacOS
• Shell: fish
• Tool/CLI version: 0.16.2 (commit 76169a3e)

Anything else we need to know?

No response

[augmentmoogi]

@samneirinck

just to clarify - you're using nested worktrees structure

Similar to the following?

my_clone
    + .git (folder)
    + ... project  files
    + .worktrees
               + worktree1
                         + .git (file)
                          + .. project files

Is that correct?

If so, a fix is already available in the latest prerelease.