Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#809 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
developer-experience, tooling

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
TypeScript
Estrelas
13.9k
Forks
1.4k
Merge médio
5h 57min
PRs com merge (30d)
135

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de cursor/plugins

Todas as issues de cursor/plugins

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.