# Is it possible to set the process 'cwd' (aka 'working directory') via the tooling API?

**URL:** <https://discuss.gradle.org/t/is-it-possible-to-set-the-process-cwd-aka-working-directory-via-the-tooling-api/7185>\
**Category:** Old Forum Archive\
**Created:** [October 22, 2012, 3:29pm UTC](https://discuss.gradle.org/t/is-it-possible-to-set-the-process-cwd-aka-working-directory-via-the-tooling-api/7185 "2012-10-22T15:29:00Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![luke\_daley](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/luke_daley/32/9890_2.png) [@luke\_daley](https://discuss.gradle.org/u/luke_daley)\
**Post date:** [October 23, 2012, 5:36pm UTC](https://discuss.gradle.org/t/is-it-possible-to-set-the-process-cwd-aka-working-directory-via-the-tooling-api/7185/4 "2012-10-23T17:36:00Z")

</div>

Points noted, thanks. I’ll bring this to Szczepan’s attention.

> At the same time, it still makes sense to strive for the commandline tools and IDE tools to behave the same way as much as is possible / reasonable.

The thing here though is that we don’t guarantee the cwd when invoking via the command line. If you’re using the daemon from the command line then the working directory may not be the project directory. Or even if you’re executing from a subproject.

---

_[View the full topic](https://discuss.gradle.org/t/is-it-possible-to-set-the-process-cwd-aka-working-directory-via-the-tooling-api/7185)._