Taste

Taste is powered by our meta neuro-symbolic AI model taste-1 with continuous reinforcement learning (RL). We combine reasoning with neural intuition to create an invisible architecture of your choices, structures, patterns and tooling preferences.

• Continuously learning side learns the texture of your code (explicit & implicit feedback).
• Meta Neuro-Symbolic AI model taste-1 enforces the invisible logic of your choices.
• Reflective Context Engineering of a self-aware RL feedback loop to build skills.

✓ 10x faster coding, 2x faster code reviews, 5x fewer bugs.

Taste: The Next Frontier in AI Coding

taste-1

The taste-1 model is the core of our taste architecture. To build your taste profile it:

• Learns from you — every accept, reject, and edit becomes a signal
• Thinks like you — learns patterns and micro-decisions you'd never document
• Grows with you — a continuous learning loop that never goes stale

Unlike traditional coding assistants that rely on generic best practices, Taste builds a personalized model of your team's code review patterns, style preferences, and architectural choices. It observes how you write, review, and merge code to develop an intuitive understanding of your quality standards and design philosophy.

How to get started

Once installed, just start coding. Taste learning runs in the background and builds your profile from every interaction.

Taste sharing and portability

The architecture of Taste is fundamentally built around the principle that taste should be transferable and composable. Your learned preferences aren't locked in a single project. They can be used across all your projects, shared with your team, and composed together to match your workflow. You can view and manage everything in the Command Code Studio.

Settings

Taste learning runs in the background, learning from your interactions. You can turn it on or off at two scopes — per project and for your user account — from the /taste panel inside Command Code.

Changing settings from /taste

Run /taste to open the Taste Settings panel. It has two rows:

• This project — writes .commandcode/settings.json (committed, shared with your team)
• User — writes ~/.commandcode/config.json (applies to all your projects)

Where taste is set

Command Code checks these files in order of priority to determine whether taste learning is enabled:

To disable taste learning for a project, add the following to .commandcode/settings.local.json:

The override in .commandcode/settings.local.json will take precedence over the project-level setting.

Manage taste

Sharing and managing taste profiles is as simple as using Git. The npx taste CLI tool is your primary interface for pulling, pushing, listing, and composing taste models, which you can view in the Command Code Studio.

This unified interface lets you push your learned preferences to the Command Code Studio, pull taste from teammates or the community, and compose multiple taste profiles to match your workflow.

This pushes your entire project's taste to commandcode.ai/username/taste, and pulls taste from remote to your local project:

Taste packages

A taste package is a collection of learnings organized by category (e.g., cli, typescript, architecture). Each package contains a taste.md file with preferences and patterns Command Code has learned.

Taste packages are of three types:

Project

Project specific taste packages are automatically learned and stored in your project.

• Path: .commandcode/taste/
• Use case: Learnings unique to this codebase

Global

Your personal taste packages accessible across all projects on your machine. Use the -g flag to push/pull global packages.

• Path: ~/.commandcode/taste/
• Use case: Your personal taste that follows you across projects

Remote

Taste packages on cloud under your profile at commandcode.ai.

• Path: commandcode.ai/username/taste
• Use case: Team sharing, backup, sync across machines, public packages

File structure

File structure for project and global taste packages:

Project taste vs. individual packages

You can either push/pull your entire project taste or individual packages.

Project taste (push --all)

When you use push --all, Command Code pushes your entire project's taste as a single unit:

• Bundles all packages from your project together
• Project name is derived from your current directory
• Pushed to remote under your namespace

Individual package (push <package>)

When you push a specific package, only that single package is uploaded:

• Pushes one package at a time
• You choose the namespace (personal or organization)
• Great for sharing specific learnings with others

Command reference

Complete reference for all npx taste commands. Manage your taste packages across project, global, and remote.

taste push

Push taste packages from your local project to remote or global.

Options

Targets

Remote is the default — pushes to cloud under your profile at commandcode.ai/username/taste (use case: team sharing, backup, sync across machines, public packages). Use -g to push to your global packages at ~/.commandcode/taste/ instead (use case: personal taste that follows you across projects).

Examples

Bundles all your project's taste packages and uploads them to commandcode.ai/username/taste. Your team can then pull with npx taste pull username/project-name.

Prompts you to select a namespace (personal or organization), then uploads only the cli package. If you have push access to multiple accounts, you get prompted.

Uploads the cli package directly to the myteam namespace without prompting.

Uploads the package and makes it publicly discoverable by other Command Code users.

Completely replaces the remote package without merging. By default, push intelligently merges learnings.

Merge behavior

By default, taste push intelligently merges your local learnings with existing remote/global content:

• New learnings are added
• Updated learnings (changed confidence) are updated
• Identical learnings remain unchanged

Use --overwrite to skip merging and completely replace the target.

Output

taste pull

Pull taste packages from remote or global to your project.

Options

Targets

Remote is the default — pull from cloud under your profile or others' profiles at commandcode.ai/username/taste (use case: get taste from teammates, sync across machines, pull public packages). Use -g to pull from your global packages at ~/.commandcode/taste/ instead.

Examples

Downloads all taste packages from teammate/awesome-project to your local project.

Downloads only the cli package from ahmadawais's profile.

Copies the cli package from ~/.commandcode/taste/ to your current project.

Copies all packages from your global to the current project.

Completely replaces your local cli package with the remote version.

Merge behavior

By default, taste pull intelligently merges remote learnings with your local content:

• New learnings from remote are added locally
• Updated learnings (changed confidence) are updated
• Identical learnings remain unchanged

Use --overwrite to skip merging and completely replace local content.

Output

taste list

List all available taste packages.

Options

Scopes

By default, taste list shows packages in your current project's .commandcode/taste/ directory. Use -g to list your global packages at ~/.commandcode/taste/, or --remote to list packages stored on cloud under your profile at commandcode.ai/username/taste.

Output

The command displays:

• Package name: The taste package identifier
• Public badge: [public] for publicly discoverable packages
• Stats: Star count (★) and download count (↓) for public packages
• Learning count: Number of learnings in the package
• Last updated: When the package was last modified

taste lint

Validate taste file format and structure. This command checks your taste files for errors and warnings before pushing.

Arguments

Options

Examples

Validates the cli taste package in your local project.

Validates all taste packages in your local project's .commandcode/taste directory.

Validates the cli package from your global.

Validates all packages in your global at ~/.commandcode/taste.

Output

The command provides detailed validation results:

What gets validated

Behavior

• Validates both main taste.md and category-specific taste files
• Supports automatic header migration for legacy format files
• Errors indicate problems that must be fixed before pushing
• Warnings indicate potential issues but don't block operations

taste open

Open a taste package in your default editor. This command provides quick access to edit your taste files directly.

Arguments

Options

Examples

Opens the cli taste package from your local project in your default editor.

Opens the cli package from your global at ~/.commandcode/taste.

Output

Editor configuration

The command uses your system's default editor set via the $EDITOR environment variable. If not configured, you'll see setup instructions:

After adding the export, restart your terminal or run source ~/.zshrc.

Behavior

• Opens the taste file in your default editor
• For category-specific files: Opens at line 1
• For main taste.md files: Searches for the category heading and opens at that line
• Automatically navigates to the correct location in the file

Common workflows

Share your project taste with the team

Use your taste across projects (via global)

Backup and sync via remote

Next steps

• Build something cool with Command Code and see your taste in action
• View and manage your packages in the Command Code Studio
• Join our Discord community for feedback, requests, and support.