Skip to content

FAQ

Jules is a software coding agent that helps you fix bugs, add documentation, update your app, and implement new features. It integrates with GitHub and works asynchronously — meaning you can submit a task, go do something else, and return when it’s done. Jules is currently in Public Beta.

Yes, for now, Jules is free of charge. Jules is in beta and available without payment while we learn from usage. In the future, we expect to introduce pricing, but our focus right now is improving the developer experience.

Each task runs in a fresh virtual machine where Jules clones your repo, installs dependencies, and makes changes based on your prompt. You can provide setup scripts to ensure your project builds and tests correctly.

How does Jules run code, and what should I know about security?

Section titled “How does Jules run code, and what should I know about security?”

When you run code in Jules, it’s executed in a secure, cloud-based virtual machine (VM) with internet access. While this gives you powerful tools to test, build, and debug in context, it’s important to treat the environment with the same security precautions you would for any public or shared compute surface. If you’re not sure whether something is safe to run, we recommend reviewing it carefully (including non-code components). Jules is a large language model based system which operates on both the code and non-code files in a repository.

You are responsible for the code you run. That means:

  • Don’t commit secrets (like API keys, tokens, or credentials) to your repo, especially if you’re pulling code into Jules from a Git provider.
  • Avoid known security vulnerabilities in your dependencies or scripts. Consider following GitHub’s Quickstart for securing your repository if you’re using GitHub.
  • Be cautious with third-party packages or shell commands that could compromise your system, your data, or others.

Can Jules run long-lived commands like npm run dev?

Section titled “Can Jules run long-lived commands like npm run dev?”

No. Long-running processes like dev servers or watch scripts aren’t currently supported in setup scripts. Use discrete install/test commands instead.

Jules is language agnostic but works best with projects that use:

  • JavaScript/TypeScript
  • Python
  • Go
  • Java
  • Rust

Support depends on what’s installed on the VM and the clarity of your environment setup script.

Yes! Jules is designed to be asynchronous. You can leave the app after submitting a task. Make sure to enable notifications so you’ll be alerted when a plan is ready or a task completes.

How do I provide feedback or report a bug?

Section titled “How do I provide feedback or report a bug?”

Click the feedback button in the bottom left of the Jules UI. No account or tracking system required — feedback goes straight to the team.

Jules will retry automatically. If it continues to fail, it will mark the task as failed and notify you. Common causes include broken setup scripts or vague prompts.

You can revise and rerun the task once you’ve addressed the issue.

By default, you can run:

  • 2 tasks concurrently
  • 5 total tasks per day

If you need more, you can request increase limits.

Can I change which repos Jules has access to?

Section titled “Can I change which repos Jules has access to?”

Yes. Go to your GitHub settings:

  1. Click your profile —> settings
  2. Select applications in the sidebar
  3. Find Google Labs Jules and click configure
  4. Adjust repository access

Then refresh Jules and your new repos will appear. Learn more about managing tasks and repositories.

No. Jules does not train on private repository content. Privacy is a core principle for Jules, and we do not use your private repositories to train models. Learn more about how your data is used to improve Jules.