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

pstack: in Claude Code, every review seat runs on Claude; allow an external-CLI seat such as codex

Abierto
  • ¿Algo no está bien?
#809 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
developer-experience, tooling

Línea de trabajo

Start with docs/harness/claude-code.md and its Models table, then trace how setup-pstack reads or writes pstack-models.mdc. Check the related tool mapping work in #601 for existing conventions. Done means Claude Code can run a configured external CLI reviewer and setup-pstack can detect Codex and offer it as a second family; the issue leaves the accepted role syntax open.

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

Descripción

What happens

pstack's review panels are built on two model families. interrogate defaults Reviewer B to grok-4.7-xhigh-fast, arena tells the cross-judge to prefer a different family from the parent, and reflect puts the tooling reviewer on Grok.

In Claude Code the harness adapter (docs/harness/claude-code.md, Models table) maps any non-Claude slug to "omit model so the agent runs on the session model, and say so". The Agent tool only accepts opus, sonnet, haiku, fable. So every panel seat runs on Claude and the adversarial design collapses to one family, silently from the user's point of view unless they read the reply closely.

Why it matters

On 2026-10-24 we ran a read-only codex exec pass over a test suite that two Claude passes (the author and an Opus reviewer via interrogate-style prompts) had already reviewed. Codex found three defects in the project's own lint tests that both Claude passes had walked past; 27 of its 33 findings held. That is the signal the two-family design is meant to produce, and Claude Code users cannot get it through pstack today.

Proposal

Let a role line in pstack-models.mdc name an external CLI seat, and have the Claude Code adapter run that seat over Bash instead of dropping it to the session model. Concretely:

  • A value such as codex (or codex-review, or a generic cli:<command>) on interrogate reviewers, arena cross-judge pool and reflect tooling.
  • The adapter row: "a codex seat runs codex exec --sandbox read-only --ephemeral -o <report> - with the same reviewer prompt on stdin, from the checkout root, and the lead reads the report file as that reviewer's findings".
  • setup-pstack detects codex on PATH and offers it as the second family when the harness is Claude Code.

We have this working as a project skill (.claude/skills/codex-review with a bin/review brief|diff wrapper and a SessionStart hook that re-applies the two role lines after /setup-pstack regenerates the file). Happy to contribute the adapter row and the setup-pstack detection as a PR if the shape above is acceptable.

Related: #601 (tool mappings for Claude Code and Codex), #734 (running pstack inside Codex, which is the other direction).

Lenguaje dominante
TypeScript
Estrellas
13.9k
Forks
1.4k
Merge medio
5 h 57 min
PR fusionados (30 d)
135

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 cursor/plugins

Todos los issues de cursor/plugins

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.