🧠 Memory Tuning for Large Projects

All Early CLI agents generate code and run tests inside a Node.js process.
For large repositories or complex test suites, you may encounter:

FATAL ERROR: Ineffective mark-compacts near heap limit  
Allocation failed - JavaScript heap out of memory

To avoid this, tune Node.js memory via the NODE_OPTIONS environment variable.

---

🧮 Recommended Default

Always set:

export NODE_OPTIONS="--max-old-space-size=5120"

This allocates ~5GB of heap memory — enough for most monorepos and concurrent processing.

📌 You can set this once in your CI environment or inline per job.

---

🧪 GitHub Actions Example

env:
  NODE_OPTIONS: "--max-old-space-size=5120"

Set this at the job or step level.

---

🧪 Jenkins Example

In your pipeline:

environment {
  NODE_OPTIONS = '--max-old-space-size=5120'
}

Or as a shell export before invoking the CLI:

export NODE_OPTIONS="--max-old-space-size=5120"
early generate-pr

---

📈 Memory Limits per CI Runner

CI Platform	Recommended Max	Notes
GitHub ubuntu-latest	6000 MB	Do not exceed --max-old-space-size=6000
Jenkins (medium agent)	5120–8192 MB	Based on node resources
Self-hosted runners	8192+ MB	Use higher values with caution

⚠️ Increasing memory allows more concurrency, but may slow down other jobs if the agent is underprovisioned.

---

🛠️ Pro Tip

Pair memory tuning with concurrency settings:

export NODE_OPTIONS="--max-old-space-size=5120"
export MAX_CONCURRENCY=4

See Concurrency & Performance for tuning recommendations.

---

✅ Summary

Variable	Value
NODE_OPTIONS	--max-old-space-size=5120
Location	CI environment or step
Required?	⚠️ Optional, but strongly recommended