Availability Timeline
Detailed release timeline for Chronos-1, including beta access, platform availability, and public launch milestones.
Chronos-1 is being released in structured phases to ensure stability, performance validation, and enterprise readiness. Below is the complete availability timeline from beta access through general release.
Release Phases
Phase 1: Research Access (Now)
Chronos-1 research materials are publicly available:
- Architecture documentation
- Benchmarks and evaluation results
- Research paper
- Performance reports
This phase does not include access to the model itself.
Only documentation, benchmarks, and research tools are available during this phase, not the Chronos-1 model.
Phase 2: Q4 2025 (Closed Beta Access)
Beta access is available exclusively to:
- Kodezi OS (Beta Users)
- Kodezi CLI (Pro Subscribers)
- Kodezi Web IDE (Pro Subscribers)
What’s included in Beta?
- Repository-scale debugging
- Multi-file patch generation
- Initial version of Persistent Debug Memory
- Test-based validation loop
- Early UI integrations in Kodezi OS
- Limited API access for partners
Limitations during Beta
- Limited language coverage
- Slower retrieval on very large repos
- Memory optimizations still in progress
- Not yet available for production use
Limited Availability
Only approved early-access users can use Chronos during this phase.
Phase 3: Q1 2026 (General Availability)
Chronos becomes fully available across all platforms:
Included Platforms
- Kodezi OS
- Kodezi CLI
- Kodezi Web IDE
- Kodezi API
- Enterprise On-Premise Deployments
Features Available at Launch
- Full debugging engine
- End-to-end autonomous fix loop
- High-precision retrieval with AGR
- Complete PDM integration
- CI/CD pipeline support
- API for enterprise workflows
Enterprise Capabilities
- Full data privacy
- Server-side isolation
- Large-scale repository support
- Custom deployment workflows
Production Ready
Q1 2026 is the first release intended for production usage across engineering teams.
Phase 4: Post-Launch Enhancements (2026)
Planned rollouts after general availability:
- Advanced performance tuning
- Expanded language support
- Repository health monitoring
- Autonomous refactoring engine
- Code documentation auto-updates
- Additional debugging benchmarks