FAQs

What can I use Jolt for?

Jolt helps you:

• Get immediate answers about any part of the codebase
• Build new features faster
• Identify and fix bugs
• Write tests, add documentation, and refactor code
• Onboard and uplevel developers quickly

Check out real examples here.

Who is Jolt for?

Jolt helps teams across engineering organizations:

• Developers: Write code faster, understand unfamiliar parts of the codebase, and get unblocked quickly
• Engineering Managers: Accelerate team velocity, reduce onboarding time, and maintain consistent code
• CTO, VPs, and Directors of Engineer: Scale knowledge, reduce tech debt, improve productivity, and answer questionnaires faster
• Product Managers: Get quick technical feasibility answers and understand implementation trade-offs
• Technical Customer Support: Respond to customer issues faster by understanding relevant code components
• QA Engineers: Understand code behavior for testing and identify potential edge cases
• Technical Writers: Create accurate documentation with deep understanding of code and architecture

What languages does Jolt support?

Jolt is built to support a wide range of languages and frameworks including popular frontend, backend, and full-stack technologies. Jolt works best with, but is not limited to:

• TypeScript and JavaScript
• Python
• Go
• Ruby
• Java, Kotlin, and Scala
• C#, ASP, and .NET
• HTML, CSS, SCSS, and LESS
• GraphQL
• Rust
• PHP
• Protocol Buffers
• Markdown and MDX

We're constantly adding better language support, so let us know if you want to see your language listed here.

Is there a codebase size limit for Jolt?

Jolt uses HyperContext to fully understand your codebase no matter the size or complexity. Jolt will scale with your team from startup to established enterprise.

If you're using Jolt with a free tier team, you limited to repos that are roughly 50K lines of code or less. If you need to work with larger codebases or more credits, please contact us at support@usejolt.ai.

What Git providers are supported?

• GitHub
• GitLab
• BitBucket
• Azure DevOps

What types of files can I attach?

Jolt supports pictures, PDFs, and text-based files as attachments as additional context including:

• JPEG, PNG, GIF, and SVG images
• PDFs (on the web only)
• Any text-based file

Is Jolt a Replacement for Copilot or Cursor?

While tools like Copilot and Cursor focus on line-by-line autocomplete, Jolt is designed for a fundamentally different and more powerful use case: understanding and working with entire codebases.

The key difference is that Jolt's HyperContext automatically understands your entire codebase without requiring you to manually specify context files. This becomes especially valuable in larger codebases (100K+ lines) where manually finding relevant files becomes unfeasible or time-consuming.

Some developers use both:

• Jolt for understanding codebases, making multi-file changes, and getting answers about any part of the code
• Copilot/Cursor for real-time code completion while typing

What are credits and how are they used?

Credits are a blended metric based on usage. Factors include the size of your codebase and the amount of code written by Jolt.

Does Jolt train on your data?

No, we do not train AI models on your codebase, plans, chat messages, or any other user data. This means any chat messages or code provided by users are not used to improve or modify the underlying AI models.

Is my data safe with Jolt and is Jolt SOC2 compliant?

Yes, we take data security seriously. Jolt is SOC2 Type II compliant, which means we've undergone rigorous third-party auditing of our security controls, policies, and procedures to ensure your data is properly protected. Our compliance demonstrates our commitment to maintaining the highest standards of security, availability, and confidentiality for all customer data.

Does Jolt respect .gitignore files?

Yes, Jolt fully respects your .gitignore files. When analyzing your codebase, Jolt follows the same rules as Git and will not process or send any files that are listed in your .gitignore file to our servers. This ensures that sensitive files, build artifacts, dependencies, and other ignored content remain private and are never included in Jolt's analysis of your codebase.

Need more help?

If you're experiencing issues with Jolt, check out the troubleshooting guide for solutions to common problems including IDE setup, Git configuration, and extension updates.