CommandCodeAI / CommandCodeAI/command-code

bug: ENAMETOOLONG on Taste Learning

Open
#639 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

Description

Summary

When learning taste inside a somewhat lengthy path, encountered a ENAMETOOLONG error:

◼ taste learning failed: ENAMETOOLONG: name too long, mkdir
'/Users/xxxxxxxxxx/projects/xxxxxxxxxx/command-code-mods/.commandcode/taste/--prefers-using-command-code's-built-in-hook
-system-(`onstop`-with-`{continue:-true}`,-`preparenextturn`-for-model-switching)-over-shelling-out-to-external-api-call
s-(e.g.,-`curl`).-when-the-framework-provides-a-seam,-use-it-instead-of-reaching-for-raw-http.-confidence:-0.9'
  • notice the --
  • seems to use a taste preference as a "category" which is typically: ui, workflow, database etc something short and topical

Note xxxxxxxxxx is same number of chars but a user path.

Expected Behavior
  • taste directory and files names to be short and topical
  • taste learning to be written properly
Actual Behavior
  • error and taste failed to be saved
Steps to reproduce the issue
  • Unsure
Command Code Version

1.11.1

Operating System

macOS

Terminal/IDE

ghostty

Shell

zsh

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

OS: macOS Tahoe 26.5.2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing taste learning in a lengthy path on macOS with the reported version and inspect how taste directory and file names are generated. Done means learning writes short, topical names successfully without an ENAMETOOLONG error.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, zsh
Domain
cli, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.