Google Jules Project Configuration
Optimize any repository to run successfully and securely inside Google Jules's isolated cloud VM.
Operating Principles
- Graceful Fallbacks: Cloud VM sandboxes lack access to host-specific tools (like 1Password CLI
opauthentication). Always wrap credential-pulling tasks with fallback options (like using.env.exampleor local defaults). - Service Port Invariance: Local Postgres in a VM runs on standard port
5432instead of host-mapped Docker ports (like5439). Ensure database URLs are adjusted for native services. - Self-Documenting: Maintain a
## Jules Setupsection inAGENTS.md(orREADME.md) detailing the setup script and VM snapshot configuration.
Quick Navigation
| Action | Command / File |
|---|---|
| Configure repository for Jules | python3 /home/delorenj/.gemini/config/skills/jules-config/scripts/jules-init.py |
| View/Edit Jules VM setup script | scripts/jules-setup.sh |
| Documented VM setup process | AGENTS.md or README.md |
How to Run
To optimally configure the current repository, execute the following command from the root:
python3 /home/delorenj/.gemini/config/skills/jules-config/scripts/jules-init.py
This utility automatically:
- Detects language runtime (Bun, Node, Python).
- Detects database dependencies (PostgreSQL, MySQL).
- Patches standard
mise.tomlhooks soop(1Password) doesn't hang. - Generates an executable
scripts/jules-setup.shthat boots local services, provisions users/DBs, installs packages, runs migrations/seeds, and executes unit tests. - Documents the setup in
AGENTS.mdso the Jules agent inherits these VM bootstrap instructions.
Out of Scope
This skill does NOT cover:
- Deploying to production hosting: Use docker compose, Traefik, or cloud hosting deployment scripts.
- Tiller sheet synchronization credentials: Jules does not run Google service account credentials; it runs against the mock database seeded by
seed.ts. - Hindsight bank configuration: Hindsight memory banks are configured via the Hindsight CLI separately.