The Key Difference
Greptile builds: A semantic graph of your codebase
Buoy adds: Design system context to that graph
Feature Comparison
Feature
Greptile
Buoy
Focus
Codebase understanding
Design system compliance
Strength
Semantic code search, context
Token matching, pattern detection
Learns from
Your entire codebase
Your design tokens & components
Reviews
Code logic & patterns
Design consistency
Adapts via
Developer feedback (thumbs up/down)
Token definitions & config
Integration
Reads CLAUDE.md automatically
Writes to CLAUDE.md
What Each Tool Catches
Greptile catches:
- • Logic inconsistencies
- • Pattern violations
- • Missing error handling
- • Code that contradicts existing patterns
Buoy catches:
- • Hardcoded design values
- • Token misuse
- • Component drift
- • Design system anti-patterns
The Greptile + Buoy Workflow
Greptile learns from your team:
- • Watches which comments get thumbs up/down
- • Learns from developer replies
- • Adapts to your preferences
Buoy adds design expertise:
- • Knows your exact token values
- • Tracks component patterns
- • Flags design system violations
Together: Reviews that understand both your code AND your design system.
Auto-Learning Integration
Greptile automatically reads these files for context:
CLAUDE.md .cursorrules agents.md
Run buoy onboard to add design system context to CLAUDE.md
Greptile picks it up automatically.
Already using Greptile?
Add Buoy context in seconds:
# Option 1: Update CLAUDE.md (Greptile reads this!)
npx @buoy-design/cli begin
buoy onboard
# Option 2: Export dedicated Greptile config
buoy lighthouse --export-greptile > greptile-buoy.jsonYour design system is now part of Greptile's context.