Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[Feedback]: Global Taste learning and shared preferences across all projects

Aberta
#141 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
18/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
git
Domínio
desktop

Direção de pesquisa

Start by finding where Taste reads and writes .commandcode/taste/ per repository, and how the "Inherit from user" setting is wired in the Settings area. Agree the storage-scope design (Global, Project, Both) with maintainers before coding, since the issue proposes options but no decision. Done means global-only mode writes to the user config directory, creates no in-repo Taste folders, and project overrides still apply in Both mode.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement
What problem are you trying to solve?

I'm using Command Code Desktop on Windows and regularly work across many different repositories.

Currently, Taste creates separate .commandcode/taste/ directories inside individual repositories instead of maintaining one shared collection of personal preferences.

Most of my coding preferences, workflows, and conventions apply to all my projects, regardless of the repository.

I'd like Taste to automatically learn from all my sessions across different repositories and remember those preferences globally, without creating separate Taste files in every project.

Currently, learned preferences are fragmented across repositories, and automatically generated Taste files can also end up appearing as untracked files in Git.

What would improve it?

I'd like an option to make Taste learning fully global at the user level.

Ideally, this would:

  • Automatically learn from sessions across all repositories and projects.
  • Store all learned preferences centrally in the user's configuration directory (e.g. ~/.commandcode/taste/).
  • Automatically apply those preferences to every project.
  • Continuously update the same global preference collection when working in different repositories.
  • Avoid creating .commandcode/taste/ directories inside repositories when using global-only mode.
  • Allow viewing, editing, and managing global preferences directly from the Desktop app.
  • Work automatically without requiring manual synchronization, push/pull commands, or copying files between repositories.

A possible solution would be a configurable Taste storage scope:

  • Global (User): Learn from all projects, store preferences centrally, and apply them everywhere.
  • Project: Learn and store preferences only within the current repository.
  • Both: Maintain shared global preferences alongside project-specific preferences, allowing project-specific rules to override global ones when necessary.

This would make Taste much more useful for developers working across multiple repositories while keeping personal preferences separate from project files.

The existing "Inherit from user" setting appears to control whether learning is enabled, rather than where preferences are stored.

What do you do today?

No response

Product area

Settings

Linguagem predominante
Shell
Estrelas
96
Forks
7
Merge médio
2h 46min
PRs com merge (30d)
1

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de CommandCodeAI/desktop

Todas as issues de CommandCodeAI/desktop

Issues semelhantes

Mais issues de Shell/Bash

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.