# debugger: Use current worktree directory when spawning an adapter \(\#31054\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/0415e853d5456fa4d138f8f9aea0e85f3c4954d4)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 0415e853d5456fa4d138f8f9aea0e85f3c4954d4

Requested commit: 0415e853d5456fa4d138f8f9aea0e85f3c4954d4

Commit: 0415e853d5456fa4d138f8f9aea0e85f3c4954d4

Tree: a912cb5ccb04915aba03cf1d0c9925e854e67d04

Author: Remco Smits

Committer: GitHub

## Message

```
debugger: Use current worktree directory when spawning an adapter (#31054)

/cc @osiewicz 

I think bringing this back should fix **bloveless** his issue with go
debugger.
This is also nice, so people are not forced to give us a working
directory, because most adapters will use their **cwd** as the project
root directory. For JavaScript, you don't need to specify the **cwd**
anymore because it can already infer it

Release Notes:

- debugger beta: Fixed some adapters fail to determine the right root level of the
debug program.
```

## Parents

- [1c9b8183424d56f0f8f445f151f38b2b208f7786](https://git.cafe/gitcafe/zed/commit/1c9b8183424d56f0f8f445f151f38b2b208f7786?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/0415e853d5456fa4d138f8f9aea0e85f3c4954d4?format=markdown)