Frequently Asked Questions (FAQ)

Below you’ll find answers to the most common questions about Chronos, covering how it works, technical behavior, performance results, access availability, and integration inside the Kodezi ecosystem.

General Questions

Q. What is Chronos-1?
A. Chronos-1 is a debugging-first language model engineered for repository-scale reasoning, multi-file debugging, and automated code repair. It powers self-healing and autonomous maintenance inside Kodezi OS, CLI, and Web IDE.

Q. Is Chronos-1 publicly available?
A. Not yet. Chronos-1 becomes available in Q1 2026 within Kodezi OS, Kodezi CLI, and the Kodezi Web IDE.

Q. Does Chronos-1 replace tools like Copilot or Cursor?
A. No. These tools help you write new code. Chronos-1 is designed to debug, maintain, and evolve existing codebases autonomously.

Q. Does Chronos-1 work on entire repositories?
A. Yes. Chronos-1 retrieves only the necessary files using Adaptive Graph-Guided Retrieval (AGR) and performs multi-file debugging with full repository context.

Q. Can Chronos-1 operate without prompts?
A. Yes. Inside Kodezi OS, Chronos-1 works autonomously—detecting failures, generating fixes, validating patches, and maintaining documentation without manual triggers.

Technical Questions

Q. How does Chronos-1 retrieve debugging context?
A. Chronos-1 uses Adaptive Graph-Guided Retrieval (AGR), which traverses dependencies, call graphs, dataflow paths, and code history to assemble the exact context needed for debugging.

Q. Does Chronos-1 learn over time?
A. Yes. Chronos-1 uses Persistent Debug Memory (PDM) to store recurring bug patterns, fix outcomes, semantic snapshots, and historical diagnostics for each repository.

Q. Does Chronos-1 validate its fixes?
A. Yes. Every patch is tested inside a real Execution Sandbox with unit tests, integration tests, CI/CD simulations, linting, and type checks.

Q. Does Chronos-1 generate documentation?
A. Yes. The Explainability Layer produces root-cause summaries, patch explanations, risk assessments, and documentation updates.

Q. Can Chronos-1 debug multi-file failures?
A. Absolutely. Chronos-1 is specifically optimized for cross-file reasoning and handles scenarios where symptoms and root causes live in different parts of the repo.

Performance Questions

Q. How accurate is Chronos-1 at debugging?
A. Chronos-1 achieves:

• 80.33% on SWE Bench Lite
• 67.3% real-world fix accuracy in large multi-file failures
• 89% developer preference in blind evaluations

Q. How does Chronos-1 compare to general-purpose LLMs?
A. General LLMs drop to 13–15% debugging accuracy. Chronos-1 leads with a 20-point margin over the next-best debugging system.

Q. How well does Chronos-1 perform on complex projects?
A. Chronos-1 excels across diverse ecosystems:

• SymPy: 96.1%
• Sphinx: 93.8%
• Django: 90.4%

Q. Does Chronos-1 work on large repositories?
A. Yes. Chronos-1 maintains high accuracy even on repos with 1M+ lines, outperforming baselines by 15×.

Q. Which languages does Chronos-1 support?
A. Chronos-1 achieves strong consistency across Python, JavaScript, Java, Go, C++, and Rust.

Access & Pricing

Q. How do I access Chronos-1?
A. Chronos-1 will be available starting Q1 2026 through:

• Kodezi OS
• Kodezi CLI
• Kodezi Web IDE
• Kodezi Enterprise API

Q. Will Chronos-1 have an API?
A. Yes. The Enterprise API launches in Q1 2026 for CI/CD, internal tools, and automation pipelines.

Q. How is Chronos-1 priced?
A. Chronos-1 is included within Kodezi OS, Kodezi CLI+OS plans, and enterprise subscriptions.
API pricing will be announced during the launch window.

Q. Is there early access?
A. Yes. Users can join the early access waitlist at https://kodezi.com/os.

Q. Are there usage limits?
A. Chronos-1 inside Kodezi OS and CLI offers full autonomous debugging with integrated compute—no token or credit limits for debugging operations.

Integration Questions

Q. Where does Chronos-1 work best?
A. Chronos-1 is most powerful inside Kodezi OS, where it can continuously monitor code, detect regressions, run fix loops, and update documentation autonomously.

Q. Can Chronos-1 run from the command line?
A. Yes. Kodezi CLI allows developers to run:

• kodezi debug
• kodezi fix
• kodezi analyze
• kodezi explain

Q. Does Chronos-1 integrate with CI/CD?
A. Yes. Through the upcoming Enterprise API, Chronos-1 can automatically analyze build failures, provide root-cause summaries, and generate fix PRs.

Q. Does Chronos-1 integrate with observability tools?
A. Chronos-1 can ingest logs, traces, and error signals from systems like Sentry and Datadog to diagnose real-world failures.