v0.6.32: BYOK fixes, ui improvements, cloudwatch tools

[waleedlatif1]

• fix: merge subblock values in auto-layout to prevent losing router context (fix: merge subblock values in auto-layout to prevent losing router context #4055)
• fix(whitelabeling): eliminate logo flash by fetching org settings server-side (fix(whitelabeling): eliminate logo flash by fetching org settings server-side #4057)
• fix(error): catch socket auth error as 4xx (fix(error): catch socket auth error as 4xx #4059)
• fix(billing): Skip billing on streamed workflows with byok (fix(billing): Skip billing on streamed workflows with byok #4056)
• fix(subscription-state): remove dead code, change token route check (fix(subscription-state): remove dead code, change token route check #4062)
• improvement(hitl): streaming, async support + update docs (improvement(hitl): streaming, async support + update docs  #4058)
• fix(hitl): async resume (fix(hitl): async resume #4064)
• feat(block): Add cloudwatch publish operation (feat(block): Add cloudwatch publish operation #4027)
• fix(jsm): improve create request error handling, add form-based submission support (fix(jsm): improve create request error handling, add form-based submission support #4066)

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Apr 9, 2026 5:20am

[cursor]

PR Summary

Medium Risk
Medium risk because it changes core execution/resume/streaming plumbing (including new async job queueing) and billing cost behavior for BYOK streaming responses, which can affect workflow runtime correctness and cost reporting.

Overview
Human-in-the-loop resume now supports sync, SSE streaming, and true async execution, driven by executionMode stored in the execution snapshot and respected by POST /api/resume/... (including a new polling endpoint and updated docs). Async resumes are dispatched via a new resume-execution job type with BullMQ/Trigger.dev plumbing, plus new worker processor support.

Streaming execution was refactored so createStreamingResponse is executor-agnostic (takes an executeFn), properly handles paused results, and only emits selected outputs for completed blocks; chat/form/execute routes were updated accordingly.

Adds CloudWatch “Publish Metric” support end-to-end (tool + API route + block UI/docs + integrations metadata) and improves CloudWatch error handling defaults.

Includes several fixes/improvements: BYOK streaming now forces zero model cost while preserving tool costs (and tokenization skips recalculation when billing already set pricing), socket-token auth errors map to 401, speech token uses server-side usage limit checks with a UI callback to navigate to subscription settings, whitelabeling removes logo flash by fetching org settings server-side and disabling SSR for settings UI, auto-layout preserves subblock state, JSM request creation supports form answers with better error messages, and various UI/doc tweaks (SVG uploads, tool cost display, excluded output types, version strings).

^{Reviewed by Cursor Bugbot for commit db23078. Configure here.}

[greptile-apps]

Greptile Summary

This release bundles several fixes and features: BYOK cost-zeroing for streamed workflows (via a zeroCostForBYOK property interceptor on the execution output), server-side whitelabeling settings to eliminate logo flash, async/streaming HITL resume support, a new CloudWatch Publish Metric operation, improved JSM form-based request support, and removal of the now-dead getUserSubscriptionState / hasExceededCostLimit code paths.

Confidence Score: 4/5

Safe to merge; all three findings are P2 and none block correct operation in the common path.

The BYOK streaming cost-zeroing has a known edge-case silent failure, the resume-route branch condition relies on implicit ordering, and the completedBlockIds filtering can silently drop partial block output. All are bounded in impact and the developer has already noted the BYOK limitation with a warning log. No P0/P1 issues found.

apps/sim/providers/index.ts (zeroCostForBYOK silent no-op), apps/sim/app/api/resume/.../route.ts (implicit branch ordering)

Vulnerabilities

No security concerns identified. AWS credentials in the new put-metric-data route are validated server-side and never logged. The checkInternalAuth guard is correctly applied. Socket-token auth error handling correctly surfaces UNAUTHORIZED as 401 rather than 500 without leaking session details.

Important Files Changed

Filename	Overview
apps/sim/providers/index.ts	Adds zeroCostForBYOK to intercept cost writes for BYOK streaming; silently no-ops if execution.output is not yet initialised at intercept time.
apps/sim/app/api/resume/[workflowId]/[executionId]/[contextId]/route.ts	Adds streaming and async resume modes; logic is correct but the executionMode !== 'async' guard implicitly relies on the stream branch returning early.
apps/sim/lib/workflows/streaming/streaming.ts	Refactors createStreamingResponse to accept an executeFn callback; adds completedBlockIds tracking and paused-status forwarding in the final SSE event.
apps/sim/lib/billing/core/subscription.ts	Removes dead getUserSubscriptionState and hasExceededCostLimit functions; clean dead-code removal with no regressions.
apps/sim/tools/cloudwatch/put_metric_data.ts	New CloudWatch PutMetricData tool; well-structured with correct user-only visibility for AWS credentials.
apps/sim/app/api/tools/cloudwatch/put-metric-data/route.ts	New route for CloudWatch PutMetricData; uses Zod validation, checkInternalAuth, and correctly handles unit and dimensions.
apps/sim/ee/whitelabeling/components/branding-provider.tsx	Replaces cookie-based brand cache with server-fetched initialOrgSettings prop; eliminates logo flash on initial load.
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/utils/auto-layout-utils.ts	Applies mergeSubblockState after layout and on revert to prevent losing router context subblock values.
apps/sim/background/resume-execution.ts	New background task for async HITL resume; fetches paused execution by ID and delegates to PauseResumeManager.
apps/sim/lib/tokenization/streaming.ts	Adds early-exit guard in processStreamingBlockLog when cost already has billing-layer pricing (BYOK zero cost sentinel).

Sequence Diagram

sequenceDiagram
    participant Client
    participant ResumeAPI as POST /api/resume/[...]
    participant HITL as PauseResumeManager
    participant Queue as BullMQ / Trigger.dev
    participant Worker as Resume Worker

    Client->>ResumeAPI: POST with resumeInput
    ResumeAPI->>ResumeAPI: validateWorkflowAccess + preprocessExecution
    ResumeAPI->>HITL: enqueueResumeInput()
    HITL-->>ResumeAPI: { pausedExecution, resumeExecutionId, ... }

    alt executionMode = stream (API caller)
        ResumeAPI->>HITL: startResumeExecution(onStream, onBlockComplete)
        HITL-->>ResumeAPI: ReadableStream (SSE)
        ResumeAPI-->>Client: 200 SSE stream
    else executionMode = sync (API caller)
        ResumeAPI->>HITL: startResumeExecution()
        HITL-->>ResumeAPI: ExecutionResult
        ResumeAPI-->>Client: 200 JSON result
    else executionMode = async (API caller)
        ResumeAPI->>Queue: enqueue resume-execution job
        Queue-->>ResumeAPI: jobId
        ResumeAPI-->>Client: 202 { jobId, statusUrl }
        Queue->>Worker: processResume(job)
        Worker->>HITL: startResumeExecution()
        HITL-->>Worker: ExecutionResult
    else non-API caller (dashboard)
        ResumeAPI->>HITL: startResumeExecution() fire-and-forget
        ResumeAPI-->>Client: 200 JSON (immediate)
    end

Loading

_{Reviews (1): Last reviewed commit: "fix(jsm): improve create request error h..." | Re-trigger Greptile}

[greptile-apps]

zeroCostForBYOK silently no-ops when output is not yet initialised

If a provider returns a StreamingExecution where execution.output is null / undefined at the moment zeroCostForBYOK runs (i.e. the output object is created lazily during streaming rather than eagerly in executeRequest), the function logs a warning and returns without setting up the Object.defineProperty cost interceptor. The cost getter is never installed, so subsequent writes from the streaming callbacks reach output.cost unfiltered and BYOK users may be billed for model tokens they shouldn't owe.

The warning makes clear the developer is aware of this race, but there is no fallback — the cost is simply not zeroed. Consider deferring the intercept to the first write via a Proxy on the execution object itself, or asserting that all providers eagerly initialise output before returning StreamingExecution.

[greptile-apps]

executionMode !== 'async' matches 'stream' after stream branch already returned

The condition on the second branch (executionMode !== 'async') evaluates to true for executionMode === 'stream' — it only works correctly because the stream branch returns before reaching this line. The implicit coupling makes the flow fragile: if a future refactor wraps these branches in a shared helper or reorders them, the sync path will silently execute for stream mode too. Using an explicit executionMode === 'sync' guard here (or restructuring as if/else if) would make the intent unambiguous.

Suggested change

	const isApiCaller = access.auth?.authType === AuthType.API_KEY
	const snapshotConfig = isApiCaller ? getStoredSnapshotConfig(enqueueResult.pausedExecution) : {}
	const executionMode = isApiCaller ? (snapshotConfig.executionMode ?? 'sync') : undefined
	if (isApiCaller && executionMode === 'sync') {

[greptile-apps]

Blocks that stream but never fire onBlockComplete are dropped from selectedOutputs

completedBlockIds is only populated inside onBlockCompleteCallback. A block that produces streamed text but whose onBlockComplete never fires (e.g. error mid-stream, abort signal) will not be in the set, so its output key is silently excluded from the selectedOutputs final result even though streaming chunks were already sent to the client. For the HITL / resume streaming path this is the desired truncation behaviour, but it may surprise callers of the normal execute path when a partially-streamed block disappears from the final final SSE event.

[cursor]

Cursor Bugbot has reviewed your changes and found 4 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit db23078. Configure here.}

[cursor]

SVG uploads may pose stored XSS risk

Medium Severity

Adding image/svg+xml to accepted image types for profile pictures and logos introduces a stored XSS vulnerability. SVG files can embed JavaScript, and the file serving endpoint delivers them inline without sanitization. This means direct navigation to an uploaded SVG's URL can execute scripts in the application's origin, even though <img> tags safely block execution.

 

^{Reviewed by Cursor Bugbot for commit db23078. Configure here.}

[cursor]

BYOK cost interceptor may silently fail on streaming

High Severity

zeroCostForBYOK reads response.execution?.output at the moment the provider returns the StreamingExecution, but for streaming providers the output object is often not yet populated at that point. If output is undefined or null, the function logs a warning and returns without installing the getter/setter interceptor—meaning the BYOK user's model costs are never zeroed and they get billed as if using a platform key. The developer clearly anticipated this risk (the warning message says "cost may not be zeroed"), but it represents a billing-correctness gap for any provider whose streaming path lazily initialises execution.output.

 

^{Reviewed by Cursor Bugbot for commit db23078. Configure here.}

[cursor]

Form route SSE parser never captures final output

Low Severity

The form route consumes the SSE stream looking for data.type === 'complete' || data.output at the top level, but createStreamingResponse emits the final event as { event: 'final', data: { success, output, … } }. The top-level parsed object has event and data keys—not type or output—so lastOutput always remains null. This is inert today since lastOutput isn't used in the success response, but it's dead code that will silently fail if ever relied upon.

 

^{Reviewed by Cursor Bugbot for commit db23078. Configure here.}

[cursor]

BYOK setter ignores zero toolCost due to truthiness

Low Severity

In zeroCostForBYOK, the setter uses value?.toolCost && typeof value.toolCost === 'number' to capture tool costs. Because && short-circuits on falsy values, a toolCost of 0 is never captured. If a provider first writes a cost object with a positive toolCost and later overwrites it with toolCost: 0, the stale positive value persists in the closure, causing the getter to return an inflated total.

 

^{Reviewed by Cursor Bugbot for commit db23078. Configure here.}