Jules automatically looks for AGENTS.md in the root of your repository and uses it (or the README) for hints when setting up its environment. Each task runs in a fresh, short-lived VM where you can add an environment setup script, and you approve Jules' plan before it changes code. MCP support covers a vetted list of services that you connect with API keys in Settings. Higher limits come with Google AI Pro and Ultra.
Jules at a glance
| Global instructions | ? Not documented Not documented |
|---|---|
| Project instructions | ✓ YesAGENTS.md in the repository root |
| Nested / subfolder | ? Not documented Not documented |
| AGENTS.md | ✓ Yes Root AGENTS.md, read automatically |
| Skills (SKILL.md) | ? Not documented Not documented |
| MCP config | ◐ Partial Vetted servers only (e.g. Linear, Neon, Supabase, Context7), configured in Settings with API keys |
| Permissions / allowlist | ◐ Partial Plan review and approval before coding |
| Sandbox | ✓ Yes Every task runs in a fresh short-lived VM |
| Hooks | ? Not documented Not documented |
| Claude Pro/Max login | ✕ No Not supported |
| ChatGPT Plus/Pro login | ✕ No Not supported |
| API key / own plan | ✕ No Google account; higher limits via Google AI Pro / Ultra |
Exact file paths
| Path | Scope | What it does |
|---|---|---|
AGENTS.md | Repository root | Instructions and environment hints |
Environment setup script | Jules repo settings | Install/test commands run in the VM |
Using a shared AGENTS.md with Jules
Native: repository-root AGENTS.md only. See one AGENTS.md for every agent, or generate one with the AGENTS.md generator.
Copy-paste examples
AGENTS.md section Jules can use for setup
File: AGENTS.md
## Setup
```bash
npm ci
npm run build
```
## Test
`npm test` must pass before you open a PR.
Safe permissions preset
Safe Jules workflow
File: Jules settings
1. Review every plan before approving it.
2. Keep production secrets out of the repo and the setup script.
3. Use a setup script with discrete install/test commands (no dev servers or watchers).
4. Connect only the MCP services Jules needs, with scoped API keys.
5. Require PR review / branch protection on main: Jules works through pull requests.
Jules' docs don't describe command allow/deny lists; isolation comes from the per-task VM and plan approval.
Gotchas
- Long-running processes such as dev servers don't belong in setup scripts.
- Treat the VM like any internet-connected machine: don't put production credentials in it.
FAQ
Does Jules use AGENTS.md?
Does Jules support MCP?
Sources
Checked against these official pages on 2026-10-12. Cells marked "Not documented" mean we could not find the behaviour in these docs; it may still exist.