Summary
I ran cmd learn-taste on two local repositories, immediately after installing and authenticating via cmd login.
There's no taste.md output.
I had cmd cli investigate and here is the findingL:
The tool tracked which sessions it processed in ~/.commandcode/projects/home-user-repo/settings.json, but the actual taste.md output files are empty.
This looks like a bug in cmd learn-taste — it logged the session IDs and "completed" but never wrote the extracted preferences to ~/.commandcode/taste/taste.md or ~/[repo]/.commandcode/taste/taste.md.
You should report this as a bug to Command Code. The tool thinks it succeeded but produced no output.
Environment: WSL2
Expected Behavior
A taste.md artifact learned from my local repositories.
Actual Behavior
settings.json logged the session but no actual taste.md output
Steps to reproduce the issue
I ran cmd learn-taste on two local repositories, immediately after installing and authenticating via cmd login.
Command Code Version
0.28.1
Operating System
Linux
Terminal/IDE
No response
Shell
WSL2/Linux bash
Additional context
No response
Summary
I ran cmd learn-taste on two local repositories, immediately after installing and authenticating via cmd login.
There's no taste.md output.
I had cmd cli investigate and here is the findingL:
Environment: WSL2
Expected Behavior
A taste.md artifact learned from my local repositories.
Actual Behavior
settings.json logged the session but no actual taste.md output
Steps to reproduce the issue
I ran cmd learn-taste on two local repositories, immediately after installing and authenticating via cmd login.
Command Code Version
0.28.1
Operating System
Linux
Terminal/IDE
No response
Shell
WSL2/Linux bash
Additional context
No response