Roadmap: where CoreCoder goes after v0.8.0

Aperta
#40 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Morrow588 ci sta già lavorando.

Dal 15/10/2026.

  • #41 di @Morrow588 — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python
Ambito
ai, cli, documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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".

Lingua principale
Python
Stelle
1.8k
Fork
453
Merge medio
6h 16m
PR unite (30g)
15

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di he-yufeng/CoreCoder

Tutte le issue di he-yufeng/CoreCoder

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.