Taste packages not being generated despite extensive Command Code usage on Windows VS Code setup

[X-eyn]

Summary

I’ve been using Command Code extensively in a Next.js + TypeScript project for several hours on Windows using VS Code, and Command Code history/checkpoints/files are all being generated correctly.

However, Taste does not seem to actually learn or generate any packages.

Current project structure:

.commandcode/taste/taste.md

Current contents of taste.md:

# Taste (Continuously Learned by [CommandCode][cmd])

[cmd]: https://commandcode.ai/

Commands/output (run from the VS Code integrated terminal on Windows):

command-code taste list

returns:

No taste packages found in project

and:

command-code taste push --all

returns:

Pushing 0 packages to <project> (remote)

Error: No taste packages found in project

But:

• .commandcode/projects/... history files exist
• .commandcode/file-history/... exists
• checkpoints/history are actively being created
• I’ve been using Command Code heavily throughout the day in VS Code on Windows

I expected categorized packages like:

.commandcode/taste/typescript/taste.md
.commandcode/taste/architecture/taste.md

Questions:

1. Under what conditions does Taste actually generate packages?
2. Is there a manual trigger for taste extraction/learning?
3. Is this expected behavior, or could something be misconfigured on Windows/VS Code?
4. Are there workflows/actions specifically required for Taste learning to occur?

Using:

• Command Code v0.26.7
• Windows
• VS Code
• Next.js + TypeScript project

Expected Behavior

Taste.md file was supposed to be populated properly when coding during the session

Actual Behavior

Test.md didn't get populated even after 7-8 hours session

Steps to reproduce the issue

1. Create a Next.js + TypeScript project on Windows and use Command Code extensively in VS Code for several minutes so that .commandcode/projects, .commandcode/file-history, and checkpoints are generated.

2. Verify that only the base file exists at .commandcode/taste/taste.md with default contents and no categorized Taste package directories are created.

3. Run command-code taste list from the VS Code integrated terminal and observe the output: No taste packages found in project.

4. Run command-code taste push --all and observe: Pushing 0 packages to <project> (remote) followed by Error: No taste packages found in project.

Command Code Version

0.26.7

Operating System

Windows

Terminal/IDE

VSCode

Shell

No response

Additional context

No response

[thisisfaizi]

Facing the same issue. I've Consumed the Go plan, but the Taste.md file is still empty.