[waleedlatif1]

Summary

• Raise the Mothership code-call ceiling (run_code / run_function) from 300 s to 900 s
• A render or build that needed more than five minutes was cut off at the ceiling and failed. The model then either started over in smaller pieces or escaped the call with a background process, which stalled once the idle workbench paused. Over a recent week, calls that ran into the ceiling failed about 83% of the time, and they took about a sixth of all code-call time
• No behavior changes until the worker raises its own schema maximum (companion PR). Until then the worker never requests more than 300 s
• Every other layer already scales with the requested budget: the deadline header, the session sandbox lease (idle window + remaining budget), the provider command timeout, and per-second sandbox metering

Type of Change

• Improvement

Testing

• function-execute-session.test.ts: the timeout table now covers 900 and 901 s through the dispatcher and the real handler; it fails on the 300 s ceiling and passes on 900 s
• Live E2B probe: a command that printed nothing for 420 s ran to completion (exit 0, stdout intact). The command stream carried a keepalive frame every 50 s throughout, so a 350 s idle cut on the network path never fires
• Lint on the changed files; CI runs the rest

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Companion: simstudioai/mothership#902 (the worker raises its schema maximum; merge and release this PR first)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Nov 3, 2026 12:50am UTC

[github-actions]

✅ Cross-repo companion check

All declared companion PRs are merged into staging.

• ✅ simstudioai/mothership#902 — merged into staging — improvement(worker): let a code call run for up to fifteen minutes

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no new blocking issues were found.

Summary

Raises the run_code and run_function ceiling from five to fifteen minutes.

• Mothership code calls can use a timeout of up to fifteen minutes.
• Callback access and project upload bindings stay available during long code calls.

_{Reviews (3) · Last reviewed commit: "fix(mothership): keep a long code call's..." · Reviewed by Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 4 files

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 5 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}