StackBlitz WebContainer and GitHub repository: deployment log routing

Direct Answer

Build logs (npm install, compile, test) appear only in the StackBlitz IDE terminal and preview console because WebContainer execution runs entirely in the browser tab. Deploy logs — including failures — reside only on the external deployment provider's dashboard (Vercel, Netlify, Cloudflare Pages, etc.). StackBlitz does not automatically mirror or aggregate deploy logs back into the WebContainer terminal. The two log streams remain separate unless the template's deploy script explicitly streams the provider's output back to the terminal.

An authenticated GitHub push from StackBlitz does not trigger an automatic redeploy unless the deployment target has a GitHub webhook configured (e.g., Vercel/Netlify "Deploy on push" setting). The OAuth scope that enables the push is repo (full private repo control) or public_repo (public repos only); this scope controls push permission only, not redeploy behavior.

Confirmed Facts

• WebContainer builds execute in-browser; terminal buffer persists only for the lifetime of the browser session. Closing the tab discards build logs.
• Deployment runs on the target platform's infrastructure. Their dashboards retain logs per provider policy (typically 30–90 days).
• The "Push to GitHub" button in StackBlitz requires a GitHub OAuth connection with repo or public_repo scope.
• No server-side build queue or log store exists for public WebContainer sessions.

Likely Explanations (Template-Dependent)

• Some templates define a deploy script in package.json that invokes a CLI (vercel, netlify, wrangler). That CLI's stdout/stderr appears in the StackBlitz terminal during execution, but the provider's full build log (including post-upload steps) remains on their platform.
• If a template uses GitHub Actions for deployment, logs appear in GitHub's Actions tab, not in StackBlitz.
• StackBlitz Enterprise/Team plans may offer persistent logs or remote execution; the public WebContainer does not.

Verification Steps

1. Open a public template with a deploy script (e.g., vite, nextjs, astro). Run the build, then trigger the deploy script. Observe that build logs stay in the terminal; deploy CLI output appears there, but the provider's dashboard shows a separate, more complete log.
2. In the deployment provider's settings, disable "Deploy on push" webhook. Use StackBlitz's "Push to GitHub" button. Confirm no new deployment is created.
3. Check the OAuth consent screen when connecting GitHub: it lists repo or public_repo. Revoke and re-grant with only public_repo to confirm push to private repos fails.
4. Close the browser tab mid-build, reopen the project. The terminal buffer resets, confirming no server-side persistence.

One Missing Diagnostic Detail

Which deployment target (Vercel, Netlify, Cloudflare Pages, custom) and which StackBlitz template are you using? The template's package.json scripts and .stackblitzrc determine whether a deploy CLI runs inside the WebContainer and whether its output streams to the terminal.