n8n-io/n8n · error

Instance AI runtime workspace has no filesystem.

Error message

Instance AI runtime workspace has no filesystem.

What it means

LazyRuntimeWorkspace.getFilesystem resolved the runtime workspace, but the workspace object exposes no filesystem capability. Any file read/write routed through this resolver therefore cannot proceed; only sandbox-level operations may still be available.

Solutions

1. Use sandbox command-based file operations instead of the filesystem API
2. Provision a workspace provider that includes a filesystem

When it happens

Trigger: Thrown at packages/@n8n/instance-ai/src/workspace/lazy-runtime-workspace.ts:144 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of n8n-io/n8n@5ac6606e81 (2026-08-12). Data as JSON: /api/errors/f0949f4fc4c21dc1. Report an issue: GitHub.

Appendix: source

Thrown at packages/@n8n/instance-ai/src/workspace/lazy-runtime-workspace.ts:144

			return;
		}

		this.workspaceDestroyPromise = workspace.destroy().then(() => {
			this.workspacePromise = undefined;
			this.resolvedWorkspace = undefined;
			this.notifyDestroyed();
		});
		try {
			await this.workspaceDestroyPromise;
		} finally {
			this.workspaceDestroyPromise = undefined;
		}
	}

	async getFilesystem(): Promise<WorkspaceFilesystem> {
		const filesystem = (await this.getWorkspace()).filesystem;
		if (!filesystem) {
			throw new Error('Instance AI runtime workspace has no filesystem.');
		}

		return filesystem;
	}

	async getSandbox(): Promise<WorkspaceSandbox> {
		const sandbox = (await this.getWorkspace()).sandbox;
		if (!sandbox) {
			throw new Error('Instance AI runtime workspace has no sandbox.');
		}

		return sandbox;
	}

	private setResolvedWorkspace(workspace: Workspace | undefined): void {
		this.resolvedWorkspace = workspace;
		if (!workspace) return;

View on GitHub (pinned to 5ac6606e81)