Repository navigation
Greptile awkwardness #3020
Description
As seen while running /ship for the first time on a branch:
● Agent "Greptile comment triage" finished · 11s
Step 10: Greptile has nothing to triage, because no PR exists yet.
I actually use Greptile. But why is it doing this on ship? Why is it not running in land-and-deploy? But doing it in land-and-deploy is wrong too, then you have to make fixes, and go back and ship again.
/ship should see if Greptile is enabled (if possible) on the repo, then commit and push the code to a PR (so Greptile can run), then while it's doing all the other review passes in ship, Greptile will be running, finally, /ship can get the Greptile results and merge it all together with all the other findings as part of the review in /ship.
Activity
v1.91.32.0 fix: Codex works from zsh, free text never enters shell co…
capy-ai commentedon Oct 6, 2026
Partly fixed in v1.91.32.0 (#3057): /ship no longer dispatches Greptile triage when there is no PR,
ghis missing or logged out, or the remote is not GitHub, and it records the reason. Running Greptile in parallel during /ship (push early, merge the findings) is tracked in TODOS.md.Upgrade: Claude Code
/gstack-upgrade; Codex and other hostscd <source from ./setup --status> && git pull && ./setup --host <host>. If it still reproduces, reopen with your./setup --statusoutput.v1.91.34.0 fix: /autoplan on current Claude Code and long sessions, q…
v1.91.32.0 fix: Codex works from zsh, free text never enters shell co…
v1.91.34.0 fix: /autoplan on current Claude Code and long sessions, q…