
How cubic learns
cubic automatically learns when you:- Reply to its comments: Type a response explaining what cubic should do differently, and it remembers for next time
- Provide context in threads: Explain why something matters to your team, and cubic incorporates that knowledge
- React to suggestions: Thumbs up/down help cubic calibrate what’s useful vs noise for your specific codebase
What cubic remembers
- Team-specific patterns: “We always use early returns” or “Integration tests required for API endpoints”
- Technical constraints: “This library causes performance issues in our stack”
- Process requirements: “Check with platform team before modifying auth service”
Privacy and control
- Explicit learning only: cubic only learns from feedback directly addressed to it in comments
- Team-scoped: Learnings never leak between different organizations or repositories
- Transparent history: View all learned patterns in your cubic dashboard (coming soon)