Troubleshooting

Claude or Codex isn't responding — check the provider status pages first

Before you dig into Nimbalyst settings, your network, or your API key, check whether Anthropic or OpenAI is having an outage. When their APIs are degraded or down, sessions will hang, time out, or return errors that look like a Nimbalyst bug but aren't.

• Anthropic (Claude): status.anthropic.com

• OpenAI (Codex / ChatGPT): status.openai.com

If either provider is reporting an incident on the affected component (Messages API, Claude Code, Codex, etc.), the fix is to wait for them to recover — there's nothing to change on your end.

Nimbalyst is crashing — increase the heap size

If Nimbalyst is crashing, freezing, or you're seeing out-of-memory errors (especially in large projects, long sessions, or while working with big diffs), the V8 memory limit is likely the culprit. The default heap size is 4 GB, which is enough for most projects but can be too small if you keep many sessions, tabs, or files open at once.

How to increase it:

1. Open Nimbalyst → Settings → Advanced.

2. Scroll to the Tools & Environment section.

3. Find Max Heap Size and pick a larger value (6 GB, 8 GB, 12 GB, or 16 GB).

4. Restart Nimbalyst — the new limit takes effect on the next launch.

Settings → Advanced → Tools & Environment: Max Heap Size dropdown

Pick the smallest size that comfortably fits your workload — going higher than you need doesn't make Nimbalyst faster, it just lets V8 hold more in memory before garbage collecting. If you're routinely hitting the ceiling at 4 GB, 8 GB is a reasonable next step. Reach for 12–16 GB only if you're working with very large repos or many parallel sessions.

If raising the heap doesn't fix the crashes, share details (project size, what you were doing, any error messages) via Discord or support — see Feedback, Discord, Support, Releases.