Subscribe to our newsletter or follow us on Twitter for update notifications.
January 2025
January 13, 2025
Documentation Launch 🎉- Launched comprehensive documentation at docs.kleap.co
- 55+ pages covering all features
- Tutorials for common use cases
- Integrated search
January 2025 (Earlier)
Preview Improvements- Upgraded to Daytona sandboxes for faster previews
- Reduced sandbox startup time to under 2 seconds
- Improved hot reload reliability
- Updated SaaS template with latest shadcn/ui components
- Added new minimal template for quick starts
- Improved mobile responsiveness in all templates
- Better code generation accuracy
- Improved understanding of complex prompts
- Faster response times
December 2024
Single-Email Transfer Flow- Simplified app transfer process
- Transfer apps with just an email address
- Improved transfer confirmation UX
- New template browser in app creation
- Preview templates before selecting
- Category filters for easier discovery
- Fixed file sync issues in certain edge cases
- Improved error messages for failed deployments
- Fixed authentication state persistence
November 2024
Daytona Migration- Migrated from CodeSandbox to Daytona for sandboxes
- 10x faster sandbox creation
- More reliable file synchronization
- Configurable auto-stop (15 minutes default)
- Faster history loading
- Better diff visualization
- Improved restore functionality
Earlier Updates
Q3 2024
- Initial public beta launch
- Core AI chat functionality
- Supabase integration
- Vercel deployment
- Element selection
- Basic templates
Q2 2024
- Private alpha testing
- Core architecture development
- Integration groundwork
Upcoming
We’re working on:- More templates
- Enhanced collaboration features
- Additional integrations
- Performance improvements
- Mobile app support
Have a feature request? Share it on Discord or email [email protected]
Version Numbers
Kleap uses continuous deployment, so we don’t have traditional version numbers. Updates are deployed as they’re ready, and this changelog reflects significant changes.Breaking Changes
We strive to avoid breaking changes. When necessary, they are:- Announced in advance
- Documented with migration guides
- Rolled out gradually