- What is Descant?
- Descant is a shared, fully autonomous software engineering system for your team. It runs multiple frontier models through a rigorous process with quality quantified and verified, at scale, with every cent tracked to the work produced.
- How does Descant work with GitHub?
- Connect your GitHub repository and assign the work. Descant plans and implements changes from GitHub issues, reviews its work, opens pull requests, and responds to a separate Descant reviewer through approval. Issues, branches, pull requests, reviews and required checks remain in GitHub.
- What kind of work can I give Descant?
- Start with a specific issue, or make work available for continuous development. Give Descant the refactor, migration, feature or larger initiative you want carried through. For larger assignments it breaks the work into manageable issues and coordinates their dependencies.
- How does Descant verify the quality of its work?
- Structured evidence and software-enforced checks carry the engineering standard through implementation, verification and independent review. A requirement needs a corresponding implementation and verification, a review finding needs a recorded resolution, and claimed fixes are checked against the resulting changes.
- How does Descant perform on benchmarks?
- Descant Soprano 7: 82.3% on DeepSWE v1.1. The Results page shows the benchmark and the supporting work.
- Do my branch protections and merge rules still apply?
- Yes. Your existing branch protections and repository rules continue to apply. Enable automatic merging for approved pull requests, or keep the final merge with a person.
- What is Issuegraph?
- Issuegraph is how Descant coordinates large engineering initiatives. It makes dependencies, priorities and opportunities for parallel execution explicit, so independent work can move forward in parallel while dependent changes follow in order.
- How much work can Descant run at once?
- Each account starts with 6 concurrent runs. You can raise your own limit up to 100 in Settings under Usage, and higher limits are available on request.
- How is Descant priced?
- Buy credits once and use them as Descant ships. There are no seats and no subscription, credits never expire, and auto-reload when credits run low is optional. Your credits fund a complete engineering process, including investigation, development, verification and independent review.
- Can I see what each change cost?
- Yes. The dashboard gives your team a shared view of active work, completed changes and spending, with costs tracked down to the cent, from your desk or your phone.
- Can I use Descant with the agents my team already uses?
- Yes. We encourage it, and it's how we use Descant ourselves. Research, ideate and work through system architecture, technical designs, specifications and protocols with your favorite agents, then turn that work into issues with requirements and acceptance criteria. Through the API, CLI and MCP, those agents can file issues, follow progress and report back while Descant executes the work. Descant turns requirements and acceptance criteria into structured data that software quantifies and verifies, not a model's assertion. Agents can synthesize research and evidence, but model intelligence can't replace information that is truly missing.
- Is our code used to train Descant?
- No. Your repository is used to perform the work you request. Customer code is not used as training data for the product.
- How does Descant keep autonomous work secure?
- Descant separates customer-code execution from model and repository access, restricts execution-network traffic, and delivers changes through your repository's pull-request workflow. Your team controls access and automatic merging.
- Will Descant keep up as models improve?
- Descant is built to advance with the models. Models can be replaced across the system, and the combinations and engineering practices around them are evaluated against the quality and cost of the work.
