running-in-the-cloud

Install and run Summer Engine headless on Linux machines without a display.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill running-in-the-cloud-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: running-in-the-cloud
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/running-in-the-cloud
Command: npx skills add https://github.com/SummerEngine/summer --skill running-in-the-cloud-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a game engine in cloud containers, CI jobs, or remote agent sandboxes fails because these Linux environments have no display, no GPU, and no browser for login. This Skill provides the exact setup recipe for installing Summer Engine, launching it headless, rendering pixels via xvfb and software GL, and authenticating without a browser. ## Core Features & Use Cases - Headless Installation and Launch: Register a prebuilt binary via SUMMER_ENGINE_BINARY, download via SUMMER_ENGINE_URL, or fetch the latest Linux release, then boot the editor with --headless --editor. - Rendering Without a GPU: Determine when xvfb-run plus Mesa llvmpipe with the opengl3 driver is required for screenshots, previews, and verification frames versus when pure headless suffices. - Browser-Free Authentication: Use auto-generated local API tokens for engine operations and inject SUMMER_TOKEN for gateway features like asset search and generation. - Use Case: A CI pipeline needs to run scene verification probes on every commit. Use this Skill to install the engine in the container, launch it under xvfb-run, and capture verification frames without any human login. ## Quick Start Install Summer Engine on this Linux server and launch it headless so we can run scene checks without a display.

Frequently Asked Questions about running-in-the-cloud

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Summer Engine on a Linux server without a display?

Launch the engine binary with --headless --editor --path <project-dir> to boot the full editor with no window. For anything that renders pixels, use xvfb-run with --rendering-driver opengl3 and Mesa's software rasterizer.

How to install Summer Engine in a Docker container or CI job?

Set SUMMER_ENGINE_BINARY to a prebuilt engine binary path and run summer install to register it, or set SUMMER_ENGINE_URL to download a specific artifact. Verify readiness with summer doctor, which checks Engine, Local API, and MCP tools.

Why do screenshots return null or blank images in headless mode?

The --headless flag uses a dummy renderer that produces no pixels. Screenshots, scene previews, and verification frames require a virtual display via xvfb-run plus the opengl3 rendering driver with software GL.

Does Summer Engine need a login to run in the cloud?

Local engine operations need no login; the engine auto-generates API tokens on every launch. Only gateway features like asset search and generation require a credential, passed as the SUMMER_TOKEN environment variable.

Can I use Vulkan or Forward+ rendering in a cloud container?

Most containers have no Vulkan device, so Forward+ and Mobile renderers are unavailable. You get software GL through Mesa llvmpipe, which produces trustworthy colors and composition but not GPU-specific effects or meaningful performance numbers.

What are the limitations of software GL rendering for game verification?

Software rendering via llvmpipe measures CPU performance, not the game's real GPU behavior, so never quote FPS from these runs. Budget seconds per frame, and treat driver-dependent output as unreliable.