Repository navigation
Feat/pi host - #69
Closed
JhonMA82 wants to merge 11 commits into
Closed
Feat/pi host#69JhonMA82 wants to merge 11 commits into
JhonMA82 wants to merge 11 commits into
Conversation
- super-board-host.sh: AI_AGENT=pi or PI_CODING_AGENT=true means pi, checked before the Codex ids so a pi launched from a Codex shell reports the innermost host - SUPER_BOARD_HOST accepts claude|codex|pi - test-host.sh covers the Pi markers, precedence and the override
- --host pi: project .agents/skills stops at the owning repo root (same boundary as Codex), plus .pi/skills, ~/.agents/skills and the Pi agent directory (PI_CODING_AGENT_DIR, default ~/.pi/agent/skills) - the eight core skills keep the .claude/skills launcher contract for Pi - Pi settings skills/packages cannot be verified here: fail closed with an actionable message and accept an authoritative --catalog instead, mirroring unsupported Codex activation - tests: core direct read, native/user roots, ancestor boundary, settings and catalog paths
- pi -p -a with a deterministic tool allowlist; project trust comes from -a so .pi/extensions (guards) and project skills load - explicit --pi[=model] is required: unlike Codex there is no Claude-usage fallback that may start Pi on its own - model precedence --pi=<model> > pi.model > pi.ladders (or defaults) by tier x complexity; ungraded cards take the medium cell - Pi has no --output-schema: the worker writes its final JSON to a private result file and the wrapper validates it fail-closed; exit 9/10/79 keep the verification/skills/halt contract - test: opt-in refusal, flags, model precedence, ladders, review consent, result-file failures, separate-git-dir worktree
- super-board-pi-wave.sh: explicit --pi required, haiku router (pi.router_model) grades Ready cards, pinned models skip it, lane process groups/locks/halt contract identical to the Codex wave - super-board-stop.sh: stop Codex and Pi waves through one marker table, each wave TERM-cancels its lane groups before any claim is released - calibration refuses a completed receipt while a pi-wave marker exists - tests: router/pinning/fallback, routing summary, halt/readiness locks, concurrency, TERM cancellation and the Pi stop marker
- run-workflow.md gains "Pi runs": explicit --pi only (no Claude-usage fallback), host switch inside Pi, wave/lane invocation, no sandbox but -a trust plus guards extension, tier x grade ladders and pinning - skills-readiness.md documents Pi's discovery roots and the fail-closed settings/packages policy; onboard/README/SKILL.md route --pi and the Pi host; config-schema gains pi.model, pi.router_model, pi.ladders
- .pi/extensions/super-board-guards.ts translates Pi tool calls (bash, read,
grep, edit, write) into the same stdin JSON the .claude guards already read,
turns a deny into {block, reason} and appends PostToolUse key-literal
warnings to the tool result; a missing script or crashing guard fails open
- guard-protected-push stays opt-in: the extension runs it only when
settings.json wires it, the same switch onboard and --protect-main flip
- cleanup-wt --auto --fetch runs detached on interactive session start only;
lanes already get the merge gate's --post-merge pass
- install.sh copies extensions/*.ts to .pi/extensions/ (skipped by
--no-hooks; installed by --no-hooks --protect-main for the push guard)
- setup.py accepts --host pi; tests drive the real extension through Node
type stripping against a stub Pi API and fake guard scripts
- a live smoke showed bare haiku/sonnet/opus resolving to a ':batch' catalog variant that no chat endpoint accepts; the PI_LADDERS defaults and the router default now use claude-haiku-latest / claude-sonnet-latest / claude-opus-latest, which resolve unambiguously and take :thinking - the worktree guard's reason no longer sends Pi users to Claude-only tools: it names the host's own isolation and the Claude spelling as one example - docs (run-workflow, README table, config schema, release notes) and the lane tests follow the new defaults
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.