Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#809 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
developer-experience, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
TypeScript
Sterne
13.9k
Forks
1.4k
Ø Merge
5 Std. 39 Min.
Gemergte PRs (30 T.)
145

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus cursor/plugins

Alle Issues in cursor/plugins

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.