Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

skillopt-sleep: make transcript sources and backends pluggable (entry points), and fail on unknown backend names

Abierto
  • ¿Algo no está bien?
#314 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
32/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
developer-experience, tooling

Línea de trabajo

Start by reading harvest_sources.harvest_for_config() and backend.get_backend(), then trace how --source and --backend choices are built. The proposal spans plugin registration, module loading, checkpoint keys, and a public helper API; the author offers to implement parts 1–3 and 5 with tests. Done means existing names still work, plugins can register sources and backends, and unknown backend names raise an error.

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

Descripción

Problem

harvest_sources.harvest_for_config() and backend.get_backend() are fixed if-chains. Every new harness needs a change to core: open right now are #153 (Antigravity), #266 (DeepSeek Harness, from #225), #282 (Codex CLI rollouts), #114 (Hermes as backend and source), plus #97 (VS Code Copilot). Also, get_backend() returns MockBackend() for any name it does not know, so a typo or an out-of-tree backend silently produces a 0.0 -> 0.0 night instead of an error.

Motivating case

On one macOS machine we run a nightly cycle over claude, codex, cursor, opencode and copilot_cli natively, plus three stores upstream cannot read:

  • zcode: an OpenCode fork whose db.sqlite lacks the agent and metadata columns harvest_opencode requires, so it finds 0 sessions.
  • Antigravity: per-conversation SQLite with protobuf steps; we also read the antigravity-cli and antigravity-acp conversation dirs, which #153 does not.
  • Crush: a per-project crush.db listed in projects.json.

Today these reach the engine only by pre-writing digests.json into the handoff dir before round 1. Every model call goes through the handoff backend plus an external answerer, because no backend can be registered from outside. The adapters and the runner are public: https://github.com/djbclark/djbclark-ade/blob/master/bin/skillopt_sources.py and https://github.com/djbclark/djbclark-ade/blob/master/bin/skillopt-night

Proposal
  1. Two entry-point groups, consulted after the built-ins: skillopt_sleep.sources (name -> harvest(cfg, *, since_iso, limit, scope, invoked_project) -> list[SessionDigest]) and skillopt_sleep.backends (name -> factory(cfg) -> Backend). --source and --backend accept any registered name, and choices= lists come from the registry.
  2. --source-module pkg.mod:func and --backend-module pkg.mod:Class for unpackaged adapters.
  3. get_backend() raises on an unknown name instead of returning MockBackend (keep mock explicit).
  4. Key the harvest checkpoint by (project, source) (#312) so several sources can feed one project.
  5. A small public helper API (is_headless_replay, is_agent_session, is_meta_prompt, detect_feedback, redact_secrets), so external sources apply the same filters and redaction as built-in ones.

The existing sources would register through the same mechanism, and per-source PRs such as #153 and #266 would become optional plugins instead of core changes.

Offer

I am happy to send a PR implementing 1-3 and 5 with tests (keeping every current --source and --backend name working), and 4 separately if #312 is accepted. Tell me if you prefer a different shape, for example a config-file registry instead of entry points.

Version context: main at 343db229dbd5ddaf9df6b1d5540d8bcdb2604d5c.

Lenguaje dominante
Python
Estrellas
18.2k
Forks
1.7k
Merge medio
4 d 1 h
PR fusionados (30 d)
10

Preparar el entorno

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 microsoft/SkillOpt

Todos los issues de microsoft/SkillOpt

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.