Review before committing
Greptile: CLI reviews committed branch changes; its documented workflow ignores uncommitted changes. Greptile workflow documentation.
Perch reads the current working file with perch check. For a known requirement, select its rule name and method instead of requesting another broad review. A local CLI describes where the command runs; Perch sends relevant source to hosted TypeSafe models for analysis.
How do saved requirements differ?
Greptile: Repository instructions and cascading directory-specific standards. Greptile rule documentation.
Perch stores English ensure rules in perch.yaml or .perch/rules/. Project, file and method scopes determine what is checked. Run the named check after an edit and after the repair; a rule finding can fail the command and a CI gate. Perch rules · Working-file checks.
What does the review bill depend on?
Compare Greptile's billing unit and Perch's usage estimate
Is the CLI open source and offline?
Greptile: Commercial review service. Greptile product or license source.
Perch’s CLI is MIT-licensed; hosted model inference is a separate paid service included in its published check rate. It does not run the model offline. Unchanged requests can reuse cached answers for free. Fresh judgments can vary, and a passing requirement check does not prove application correctness. Perch MIT license.
When does Greptile fit the workflow?
Greptile provides repository-aware branch and PR review with custom standards. Its free Starter PR tier can fit one active developer; local CLI reviews require a trial or paid plan.