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
{{ message }}
Repository navigation
Recipes Page Not Finding/Displaying List of Recipes #783
When i launched localhost:9080 and logged in, I was able to successfully log in, create recipes, and see them be created on the file system properly. However, on the home page, it doesn't display any recipes at all, and searching fails to find any existing ones. This is also true through restarting.
I am however able to access them if i go directly to the url (so for example, localhost:9080/recipe/French/crepes.cook, even though searching for French or Crepes doesn't return anything. Furthermore, in the command line I tried cook r crepe (among others) and it returned no results each time.
This was also the case when I binded the server to an IP. Also tested with another device using --host mode and it behaved the same as the PC (able to log in, directly access recipe via full known link, create, etc. - but no ability to view/search recipes from main page)
I am running the .exe on Windows using the command line, tried latest version and 1 behind as well. Application also has full firewall permissions, as well as read/write (known since it was able to read/write .cook files from the editor with updates)
Thanks for the detailed report! The detail that the recipe URL works while the list and search come up empty narrows it down a lot.
We think we've found one cause. On Windows, when the recipes folder is on a mapped network drive or a network share (a NAS, \\server\share\…), CookCLI resolves the folder to a form (\\?\UNC\…) that the file search underneath can't walk. It then finds no recipes, even though opening one by its exact path still works. A fix is in #787. Some virtual drives can do the same.
To check that this is what you're seeing, could you tell us:
Where is your recipes folder? Is it on a local disk (C:\…), a mapped network drive or NAS share, or inside a synced folder like OneDrive, Google Drive or Dropbox?
What exact command do you run, and from which folder? For example cook server C:\Users\me\Recipes, or cook server run inside the folder.
Could you start the server with -v and paste the line starting with Using absolute base path:? For example:
cook server -v
Feel free to replace your username with me. We only need the shape of the path (whether it starts with \\?\UNC\, \\?\Volume{, \\server\, a drive letter, etc.).
Does the folder path contain [ or ]? Those would break the search in a different way.
If it's a network drive, you can probably work around it until the fix ships by copying the folder to a local disk and starting cook server there.
Analysis and recommendations/changes made by Claude, posted on behalf of @LeMyst
The folder is on a mapped network drive / NAS Share (Tested both forms)
I run cook server "N:\Cooking Stuff\CookCLI" --host xxx.xxx.xxx.xxx - IP is used for binding purposes since I use mesh networks, also tested over LAN
3)\\\\?\\UNC\\SERVER\\data\\Cooking Stuff\\CookCLI - It seems like it's giving the \\?\UNC\ format, but slightly different, the extra \\ is probably just Windows doing \ chars weirdly in command prompt - also machine name is SERVER thus that being like that, I have 'N:' mapped to \\SERVER\data\
No special characters, only thing that isn't a solid string of Alphanumeric chars (letters, nums) is the space in 'Cooking Stuff'
Sounds like it's probably due to it being a network drive yeah, the prefix to the path is most likely the issue which makes sense, I'll keep an eye out for the commits to merge in and give it a test then, appreciate the help!
Thanks, that confirms it. N: resolves to \\?\UNC\SERVER\data\…, and the file search underneath CookCLI finds nothing under that form of path. The fix in #787 resolves it to \\SERVER\data\Cooking Stuff\CookCLI instead, which it walks normally. The space in the folder name is fine.
(The doubled backslashes are just how that log line prints the path, with each \ escaped; it isn't Windows.)
#787 has passed all checks, including a Windows test that reproduces your setup through a network share, and is waiting for review. Until it's released, starting cook server on a local copy of the folder works around it.
Analysis and recommendations/changes made by Claude, posted on behalf of @LeMyst
Activity
fix: list recipes when the collection is on a Windows network drive
LeMyst commentedon Oct 27, 2026
Thanks for the detailed report! The detail that the recipe URL works while the list and search come up empty narrows it down a lot.
We think we've found one cause. On Windows, when the recipes folder is on a mapped network drive or a network share (a NAS,
\\server\share\…), CookCLI resolves the folder to a form (\\?\UNC\…) that the file search underneath can't walk. It then finds no recipes, even though opening one by its exact path still works. A fix is in #787. Some virtual drives can do the same.To check that this is what you're seeing, could you tell us:
C:\…), a mapped network drive or NAS share, or inside a synced folder like OneDrive, Google Drive or Dropbox?cook server C:\Users\me\Recipes, orcook serverrun inside the folder.-vand paste the line starting withUsing absolute base path:? For example:me. We only need the shape of the path (whether it starts with\\?\UNC\,\\?\Volume{,\\server\, a drive letter, etc.).[or]? Those would break the search in a different way.If it's a network drive, you can probably work around it until the fix ships by copying the folder to a local disk and starting
cook serverthere.Analysis and recommendations/changes made by Claude, posted on behalf of @LeMyst
test: list a collection whose base path canonicalizes to \\?\UNC
fix: list recipes when the collection is on a Windows network drive
Wally00123 commentedon Oct 28, 2026
Hello, thanks for the reply:
cook server "N:\Cooking Stuff\CookCLI" --host xxx.xxx.xxx.xxx- IP is used for binding purposes since I use mesh networks, also tested over LAN3)
\\\\?\\UNC\\SERVER\\data\\Cooking Stuff\\CookCLI- It seems like it's giving the\\?\UNC\format, but slightly different, the extra\\is probably just Windows doing \ chars weirdly in command prompt - also machine name is SERVER thus that being like that, I have 'N:' mapped to\\SERVER\data\Sounds like it's probably due to it being a network drive yeah, the prefix to the path is most likely the issue which makes sense, I'll keep an eye out for the commits to merge in and give it a test then, appreciate the help!
LeMyst commentedon Oct 28, 2026
Thanks, that confirms it.
N:resolves to\\?\UNC\SERVER\data\…, and the file search underneath CookCLI finds nothing under that form of path. The fix in #787 resolves it to\\SERVER\data\Cooking Stuff\CookCLIinstead, which it walks normally. The space in the folder name is fine.(The doubled backslashes are just how that log line prints the path, with each
\escaped; it isn't Windows.)#787 has passed all checks, including a Windows test that reproduces your setup through a network share, and is waiting for review. Until it's released, starting
cook serveron a local copy of the folder works around it.Analysis and recommendations/changes made by Claude, posted on behalf of @LeMyst