@blaxel/core 0.3.22-preview.295 → 0.3.22-preview.297

package/dist/cjs/common/settings.js

@@ -30,8 +30,8 @@ function missingCredentialsMessage() {
     return "No Blaxel credentials found. Set the BL_API_KEY and BL_WORKSPACE environment variables, or run `bl login`.";
 }
 // Build info - these placeholders are replaced at build time by build:replace-imports
-const BUILD_VERSION = "0.3.22-preview.295";
-const BUILD_COMMIT = "b3a3c720b8b461f985e37dbe11ff2219dcb53454";
+const BUILD_VERSION = "0.3.22-preview.297";
+const BUILD_COMMIT = "a8db9db09b9cc600365c17dd7b2a347aeef8ecf9";
 const BUILD_SENTRY_DSN = "https://fd5e60e1c9820e1eef5ccebb84a07127@o4508714045276160.ingest.us.sentry.io/4510465864564736";
 const BLAXEL_API_VERSION = "2026-04-28";
 // Bun < 1.3.11 never sends connection-level WINDOW_UPDATE: the pooled h2

package/dist/cjs/sandbox/sandbox.js

@@ -253,8 +253,15 @@ class SandboxInstance {
     /**
      * Fork this sandbox into a new sandbox or application.
      *
-     * Pass `snapshotId` to fork from a specific snapshot (create a sandbox from a
-     * snapshot) instead of the sandbox's live state.
+     * Forking into a sandbox copies the source sandbox's live state straight into
+     * the fork: no snapshot is taken, persisted, or left behind, and the returned
+     * `snapshotId` is empty.
+     *
+     * Pass `snapshotId` to fork from an existing snapshot instead of the source's
+     * live state (create a sandbox from a snapshot). Forking into an application
+     * (`targetType: "application"`) still goes through a snapshot, which is
+     * recorded because the application revision references it. In both of those
+     * cases the response carries the snapshot the fork came from.
      *
      * @param targetName - Name of the sandbox/application to create.
      * @param options - Fork options (target type, port, traffic, snapshot, ...).

package/dist/cjs/types/client/types.gen.d.ts

@@ -3720,7 +3720,7 @@ export type SandboxForkRequest = {
      */
     prefix?: string;
     /**
-     * Snapshot ID to fork from. When set, the application revision references this snapshot.
+     * Snapshot ID to fork from. When set, the fork is created from that existing snapshot (and an application revision references it). When omitted, a fork to a sandbox copies the source sandbox's live state directly and no snapshot is persisted; a fork to an application still takes a snapshot, since its revision references one.
      */
     snapshotId?: string;
     /**
@@ -3745,7 +3745,7 @@ export type SandboxForkResponse = {
      */
     name?: string;
     /**
-     * The snapshot ID the fork was created from
+     * The snapshot ID the fork was created from. Set only when the fork went through a snapshot, meaning an explicit snapshotId was supplied or the fork target is an application. Empty when the fork copied the source sandbox's live state directly.
      */
     snapshotId?: string;
     /**

package/dist/cjs/types/sandbox/sandbox.d.ts

@@ -24,9 +24,10 @@ export type SandboxForkOptions = {
     /** URL prefix for the application fork. */
     prefix?: string;
     /**
-     * Snapshot ID to fork from. When set, the fork is created from this snapshot
-     * instead of the source sandbox's live state — this is how you create a
-     * sandbox from a snapshot.
+     * Snapshot ID to fork from. When set, the fork is created from this existing
+     * snapshot — this is how you create a sandbox from a snapshot. When omitted,
+     * a sandbox fork copies the source sandbox's live state directly, without
+     * persisting a snapshot in between.
      */
     snapshotId?: string;
     /**
@@ -123,8 +124,15 @@ export declare class SandboxInstance {
     /**
      * Fork this sandbox into a new sandbox or application.
      *
-     * Pass `snapshotId` to fork from a specific snapshot (create a sandbox from a
-     * snapshot) instead of the sandbox's live state.
+     * Forking into a sandbox copies the source sandbox's live state straight into
+     * the fork: no snapshot is taken, persisted, or left behind, and the returned
+     * `snapshotId` is empty.
+     *
+     * Pass `snapshotId` to fork from an existing snapshot instead of the source's
+     * live state (create a sandbox from a snapshot). Forking into an application
+     * (`targetType: "application"`) still goes through a snapshot, which is
+     * recorded because the application revision references it. In both of those
+     * cases the response carries the snapshot the fork came from.
      *
      * @param targetName - Name of the sandbox/application to create.
      * @param options - Fork options (target type, port, traffic, snapshot, ...).