Skip to content

Guardrail Challenge: Ship It (Patch) world — CLI support#7

Open
RayirthDinesh wants to merge 2 commits into
mainfrom
feat/guardrail-challenge-ship-it-world
Open

Guardrail Challenge: Ship It (Patch) world — CLI support#7
RayirthDinesh wants to merge 2 commits into
mainfrom
feat/guardrail-challenge-ship-it-world

Conversation

@RayirthDinesh

@RayirthDinesh RayirthDinesh commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

Guardrail Challenge: Ship It (Patch) world — CLI support

Adds ship_it world support to the guardrail commands so players can attack "Patch", the autonomous repo assistant, from the CLI.

Changes

  • guardrail start --world {assistant_pro,ship_it} — pick the challenge world.
  • Ship It plant verbs: issue, pr, commit, comment, cilog, readme, webpage, deploy-target, access-request, app-consent, org-policy (mapped to the backend plant kinds).
  • info / catalog accept --world and default to the active session's world.
  • Warn when the server's started world differs from the requested --world (older backends).

Every tool side-effect stays simulated — nothing is really sent or executed.

Reuse the guardrail group for a second world. 'start --world ship_it' binds the
session (world persisted in config); info/catalog honor it. Adds the Ship It
flat plant verbs (issue/pr/commit/comment/cilog/readme/deploy-target/
access-request/app-consent/org-policy; webpage shared). api.py threads the world
param. 94 tests green.
…orld

An older backend ignores the world param and returns no 'world' field; the CLI
previously trusted its own --world and falsely reported 'ship_it'. Now it trusts
the server's reported world and warns on a missing/mismatched world.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant