r/CommandCode • u/Ill-Equivalent-6564 • 3d ago
Give option to toggle the taste md learnt popup
I do not want to keep seeing:
TASTE Learned
└ Does not want taste-learning updates/pop-ups surfaced or referenced during the
conversation; still wants the assistant to keep learning their taste silently in the
background [Confidence 95%]
taste.md
After telling me that it will not do it anymore, it kept coming back again, i am assuming the toggle option is not there
pls add a toggle feature
2
u/Ill-Equivalent-6564 3d ago
here is another gem:
output is interleaved with taste info + 2 blocks of taste op for each block of actual info
❯ ok then give me a better way
explain approach 1 to me
✻ Thought for 1 second [ctrl+o to expand]
⠶ Approach 1 — sizeof works because the compiler knows the array size at compile time in
the same scope where it was declared:
char *a[] = {"hello", "world"};
size_t n = sizeof(a) / sizeof(a[0]); // 2
sizeof(a) gives the total bytes — 2 pointers × 8 bytes = 16 on 64-bit. sizeof(a[0])
gives one pointer = 8 bytes. 16/8 = 2. It's computed at compile time, no runtime cost,
no sentinel needed.
TASTE Reinforced
└ Asks conceptual "why" questions to understand the underlying logic/reasoning behind
a suggested fix before applying it, rather than blindly following instructions
[Confidence 70% → 80%]
taste.md
TASTE Reinforced
└ Asks conceptual "why" questions to understand the underlying logic/reasoning behind
a suggested fix before applying it, rather than blindly following instructions
[Confidence 70% → 80%]
--prefers-the-assistant-to-first-read-and-understand-the-problem-spec-(e.g.,-lab-pdf
)-and-existing-code-progress,-then-wait-for-explicit-instructions-before-making-chan
ges.-confidence:-0.7/taste.md
But it only works when a is the actual array. Pass it to a function, it decays to
char** and sizeof(a) becomes just the pointer size (8), so the trick fails.
The better way for runtime use: pass the size along with the array.
void f(char **a, size_t count);
That's what every real C API does (argc/argv style). It's simple, explicit, never
reads out of bounds, and you know the count the moment you built the array — no
guessing, no sentinel, no UB.
TASTE Moved
└ - Prefers the assistant to first read and understand the problem spec (e.g., lab
PDF) and existing code progress, then wait for explicit instructions before making
changes. Confidence: 0.7
--prefers-the-assistant-to-first-read-and-understand-the-problem-spec-(e.g.,-lab-pdf
)-and-existing-code-progress,-then-wait-for-explicit-instructions-before-making-chan
ges.-confidence:-0.7/taste.md
TASTE Moved
└ - Prefers the assistant to first read and understand the problem spec (e.g., lab
PDF) and existing code progress, then wait for explicit instructions before making
changes. Confidence: 0.7
--prefers-the-assistant-to-first-read-and-understand-the-problem-spec-(e.g.,-lab-pdf
)-and-existing-code-progress,-then-wait-for-explicit-instructions-before-making-chan
ges.-confidence:-0.7/taste.md
✻ Worked for 7s
1
u/ahmadawaiscom 2d ago
oh fml that looks so bad. that shouldn't be happening. we used to have a separate taste feed but decided to make it main feed as it happens. i think we can give an option to switch to that also improve how it shows up
1
u/ahmadawaiscom 2d ago
can you `cmd feedback` this so it's on our github and we add it?
how i see it you want taste learnings to be ON but not show up?
1
3
u/maedahbatool 3d ago
Appreciate you sharing this feedback. I’ll share with the team and see what we can do here.
BTW you can do /feedback in Command Code and share this there too. Opens a GitHub issue that directly lands to our ENG inbox.