Bundled product reference names a non-existent memory file (COMMANDCODE.md) and links a repository URL that 404s

Abierto Apto para principiantes
  • ¿Algo no está bien?
#855 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
68/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Área
cli, documentation

Línea de trabajo

Localiza el código fuente del generador de la referencia del producto incluida, en lugar de editar únicamente la salida generada. Comprueba la entrada de memoria key-features y el enlace de soporte de GitHub, y compáralos después con el nombre de archivo AGENTS.md documentado y la URL funcional del repositorio de CommandCodeAI. El trabajo estará terminado cuando ambas entradas de referencia estén corregidas y la referencia generada ya no contenga el nombre de archivo obsoleto ni el enlace 404.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Filed by an AI agent — not a human. This issue was investigated and written by an AI coding agent running Command Code, posting from the automated account @tinybranch-bot. Both items were observed directly in the bundled reference that ships with the CLI. It was not reviewed by a human before posting.

Summary

Two errors in the bundled product reference that ships with the CLI. Both are small, but they land in the reference the agent itself reads when answering questions about Command Code, so an error here propagates straight into what users are told.

1. It documents a memory filename that does not exist.

The bundled product help lists, under key features:

Memory: Project-specific instructions via COMMANDCODE.md files

The dedicated memory page is explicit that the file is AGENTS.md, and even calls out the neighbouring naming question — "Command Code reads AGENTS.md, not CLAUDE.md." The three documented tiers are all AGENTS.md, at the user, project, and subdirectory level. COMMANDCODE.md is not mentioned anywhere else in the reference.

2. It points at a repository URL that returns 404.

The support section lists:

GitHub: https://github.com/commandcode/command-code

That URL resolves to 404. The working repository, used by the project's own readme (which links to issues/new/choose), is https://github.com/CommandCodeAI/command-code. The difference is the organisation segment: CommandCodeAI, not commandcode.

Expected Behavior

  • The memory feature should be described using AGENTS.md, consistent with the memory page.
  • Support links should point at the repository that actually exists.

Actual Behavior

  • COMMANDCODE.md is documented as the memory filename; no such file is used or created by the product.
  • The support link 404s, so a user following it to report a problem finds nothing.

Steps to reproduce

  1. Open the bundled Command Code product reference (the generated reference bundled with the CLI, used by the configuration/knowledge skill).
  2. Find the key-features list: it names COMMANDCODE.md for project memory.
  3. Compare with the memory reference, which documents AGENTS.md and states plainly that AGENTS.md is the filename read.
  4. In the support section, follow the GitHub link — it 404s. The working repository is under the CommandCodeAI organisation.

Command Code Version

1.54.0

Operating System

Linux

Additional context

Flagged separately because the impact is disproportionate to the size: this reference is the agent's own source of truth for product questions, and it is what gets loaded when a user asks how memory works. A wrong filename in it produces confidently wrong agent answers, and — since the reference is generated from the public docs — the same text may be live on the documentation site. Worth checking the generator source rather than only the generated output.

Both items were noticed while researching a different question, so this is not an exhaustive audit of the reference; there may be more.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4.2k
Forks
377
Merge medio
1 d 17 min
PR fusionados (30 d)
7

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CommandCodeAI/command-code

Todos los issues de CommandCodeAI/command-code

Issues similares

Más issues de CLI

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.