Gel Project Init Configuration Directory Incorrect
Author: chuckyQCreated May 24, 2026Updated May 24, 2026
- Gel Version: 7.1+ec15259
- Gel CLI Version: Gel CLI 7.10.2+e00c46c
- OS Version: Windows 11
Steps to Reproduce:
- Create an empty directory (some-sample-dir)
- Run
gel initin this directory - Create a
main.gofile and add the sample code found on the Golang client library here - Run
go mod init mymod - Run
go get github.com/geldata/gel-go - Run
go run main.go - An error will show in the console stating
Found 'gel.toml' but the project is not initialized. Run 'gel project init' - Run
go mod vendor - Add the following
fmt.Printlnin the fileconnutils.gofound ingeldata/gel-go/internal
if !exists(stashDir) {
fmt.Println(stashDir) # Add this
return errors.New("Found `gel.toml` " +
"but the project is not initialized. Run `gel project init`.")
}- Run
go run main.go
On my machine, I have the following output
C:\Users\Charles\AppData\Local\EdgeDB\config\projects\some-sample-dir-ca0e140e388a02df16b4c64518652ed2f59648e5I found the folder in the projects directory to have the path of
C:\Users\Charles\AppData\Local\EdgeDB\config\projects\some-sample-dir-99fb64a9fe6875f3a7a40a20ec17ca86f7bb6f87These added values to the folder (I am guessing some type of hash) are not evaluating the input data in the same way and it is causing the program to fail.
When I manually fix the project folder name in my C:\Users\Charles\AppData\Local\EdgeDB\config\projects with the value shown in the previous fmt.Println statement, the program will run.
After fixing the path, there are more issues connecting to the gel instance through the command line, but I want to focus on this bug first.
Source: geldata/gel