Daytona proxy API key bug fixed
A bug that caused the wrong API key to be passed to Daytona sandbox proxies has been resolved — proxy mode now fetches a fresh auth token instead of reusing a stale static key.
When creating a Daytona sandbox in proxy mode, n8n was incorrectly passing a static API key instead of fetching a fresh authentication token. This meant sandbox proxies couldn't properly authenticate with the underlying service.
The fix distinguishes between two connection modes: proxy mode now resolves a fresh token on demand via getAuthToken, while direct mode continues using the static key as before. The createSandbox function was converted to async to support this token resolution.
This fix lives in the @n8n/instance-ai package and its corresponding CLI module.
View Original GitHub Description
Summary
We were not passing the correct apikey on this path to the assistant's proxy.
Related Linear tickets, Github issues, and Community forum posts
<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)