Roadmap: where CoreCoder goes after v0.8.0

Abierto
#40 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Morrow588 ya está trabajando en esto.

Desde el 15/10/2026.

  • #41 de @Morrow588 — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python
Área
ai, cli, documentation

Línea de trabajo

This is a maintainer roadmap, not a task, and it names no single file to change. The closest concrete starting point is the eight essays in article/, whose line pins the issue says have drifted as MCP, hooks and plan mode landed, and the 227-test suite that backs the README numbers. There is no defined done state here; the issue stays open and is edited as items land, so a newcomer should read it for context and comment before starting any item.

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

Descripción

v0.8.0 is out and the engine is where I want it: 1,322 net lines covering the loop, the model interface, context compression, tools and sessions, with plan mode, hooks, checkpoints and MCP stdio on top, 227 tests green. This issue is the running note for what comes next, and just as much for what does not.

The promise that shapes the roadmap. CoreCoder's value is that one person can read all of it in an afternoon and trust every number on the README. Anything that trades readability for features is a regression here, no matter how useful that feature would be in a daily driver.

Next up, roughly in order:

  1. Keep the reading series honest. The eight essays in article/ pin specific lines, and the engine kept growing after the first ones (MCP, hooks, plan mode all landed later). The pins need a sweep, and MCP plus plan mode probably deserve essays of their own.

  2. MCP streamable HTTP, maybe. Stdio covers local servers; the HTTP transport is how hosted servers talk, and people hit it in the wild. It goes in only if it stays around a hundred lines. If it starts growing an error taxonomy and auth branches, it does not belong in this repo.

  3. Provider dialects as they surface. The 400 adaptation (max_tokens to max_completion_tokens, dropping temperature) handles everything seen in the wild so far. New dialect cases get added only with a real 400 message in hand, never on speculation.

  4. Windows paths. Every Windows report so far got a real fix (doc pins, session paths). That bar stays.

Explicitly not on the roadmap: a TUI framework, more built-in tools beyond the current eight, multi-agent orchestration. Those are fine features for a product and poison for a reading reference.

This issue stays open and gets edited as things land. Suggestions welcome, especially the kind that end with "and it only costs twenty lines".

Lenguaje dominante
Python
Estrellas
1.8k
Forks
453
Merge medio
6 h 16 min
PR fusionados (30 d)
15

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 he-yufeng/CoreCoder

Todos los issues de he-yufeng/CoreCoder

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.