CommandCodeAI / CommandCodeAI/command-code

Add per-model provider + data-retention/prompt-training disclosure

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

It should be clear what's the prompt training and data retention policy on each model/provider. I don't care if Command Code doesn't train on my prompts and doesn't retain my data, that's pointless if the underlying provider could be doing that.. You're essentially saying today like "I don't use your data dude, just chill", but omitting that the underlying providers might be doing it.. Transparency is pretty important and that's why I cancelled my sub instead of upgrading it... Thought of upgrading but gave up after realizing that. It's not enough as well that you say that 98% of your models are zdr or no prompt training... It's only enough when you at least disclosure in your website the prompt training and retention policy for each model. And if possible, provide a way of disabling models whose provider might train on prompts...

Expected Behavior

Disclosure in your website the prompt training and retention policy for each model. And if possible, provide a way of disabling models whose provider might train on prompts...

Actual Behavior

Data Retention and Prompt Training policies at PROVIDER level are not disclosure. Privacy Policy is misleading as it talks about you, not the providers.

Steps to reproduce the issue

Try finding any disclosure on the prompt training or data retention policies per model... It doesn't even disclosure the providers per model..

Command Code Version

1.26.0

Operating System

macOS

Terminal/IDE

kitty

Shell

⌘ Data Retention Policy

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 reviewing the website's model/provider listings and the existing Data Retention Policy referenced in the issue. Define how each model's provider, prompt-training policy, and retention policy will be represented, and assess the requested option to disable models with provider training. Done means the website discloses these policies per model and, if feasible, supports that opt-out.

Written by the indexing model from the issue text.

Assessment

Domain
ai, cli, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.