CommandCodeAI / CommandCodeAI/command-code

Config option to show/hide taste findings

Open
#711 1 comment 1 reaction 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

Feature Description

Taste findings are noisy and constantly require to scroll by them - a simple toggle in the config to show/hide would be enough to alleviate the issue

also found another user's complain in discort

From Ikaren:
one feedback that I have is that, I don't know if I am the only one that feels this problem, but while I am still trying to figure out how taste exactly works and how it is beneficial, I am a bit annoyed how the CC Cli presents it's updates after every turn, because, for example, I will be reading the models output, watching if it doesn't do any mistake, it ends it's turn, outputs it's response of what it did, I am reading the response to check if he did everything correctly and suddenly, BAM, absolute monster of a scroll is made because taste decided to make 1001 updates, which just sends the previous output flying up on the terminal, and this happens every turn. Could we possibly make taste less verbose? Maybe just just display a small toaster or tag saying that "taste was updated"?

Image
Use Case

No response

Additional Context

No response

How important is this to you?

None

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 tracing the CLI's taste-finding output and existing configuration options. Add a configuration-controlled way to show or hide taste findings, then verify that each setting produces the expected terminal output without changing other updates.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.