YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
Screenpipe Windows dev image
This directory builds the shared Windows 11 development image used by
develop-screenpipe-windows. It is separate from the release runner and never
copies, stops, or modifies that machine.
The build creates a temporary Windows 11 VM, provisions Codex and the complete
Screenpipe native toolchain, warms the debug-dev cache, generalizes the VM,
publishes an immutable Azure Compute Gallery version, and deletes the temporary
build resource group. The gallery remains in rg-screenpipe-win-dev-images.
./infra/windows-dev-image/build.sh 2026.8.24
If the host loses Azure connectivity after the exact tagged build VM is created but before provisioning begins, resume that VM explicitly:
RESUME_EXISTING_BUILD=true ./infra/windows-dev-image/build.sh 2026.8.24
Normal runs refuse pre-existing build groups. Resume mode verifies the VM's project, environment, and image-version tags before using it.
After publishing, launch a fresh VM from the exact image version and run
smoke.ps1 -AutonomousVisualTaskId <task-id>. Then dispatch that exact immutable
visual smoke task and verify console auto-logon,
native validation, recording/evidence upload, credential cleanup, and shutdown
without an inbound rule or operator session before setting validated=true.
The single fresh-image acceptance run may set
ALLOW_UNVALIDATED_IMAGE_FOR_SMOKE=true; all development dispatches require a
validated image.
ALLOW_UNVALIDATED_IMAGE_FOR_SMOKE=true \
AZURE_IMAGE_VERSION_ID=<exact-fresh-gallery-version-resource-id> \
AZURE_WORKER_IDENTITY_RESOURCE_ID=<managed-identity-resource-id> \
./infra/windows-dev-image/dispatch-autonomous.sh <smoke-task-id> <base-sha> <prompt-file>
dispatch-autonomous.sh uploads the exact task and versioned runtime scripts,
invokes bootstrap once, and returns. The VM then owns Codex, testing, video,
private evidence, push/PR delivery, cleanup, and shutdown; no host process is
needed. Runtime OpenAI credentials and GitHub App signing configuration come only from
managed identity plus Key Vault. See the GitHub delivery identity contract below. This workflow never uses the release builder, a GitHub Actions
runner, or any publication action.
AZURE_IMAGE_VERSION_ID=<exact-gallery-version-resource-id> \
AZURE_WORKER_IDENTITY_RESOURCE_ID=<managed-identity-resource-id> \
RESUME_LOCAL_HEAD=<optional-existing-PR-head-sha> \
./infra/windows-dev-image/dispatch-autonomous.sh <task-id> <base-sha> <prompt-file>
Each task uses a new resource group and the exact gallery image ID. The disposable VM has a Standard public IP for Azure-supported outbound access and an NSG with zero custom inbound rules. Dispatch verifies both properties before bootstrap; it never opens RDP or any other inbound port.
Defaults target West US 2 and Standard_D16s_v5. Override
AZURE_SUBSCRIPTION_ID, AZURE_LOCATION, AZURE_VM_SIZE,
AZURE_GALLERY_RESOURCE_GROUP, AZURE_BUILD_RESOURCE_GROUP,
AZURE_GALLERY_NAME, or AZURE_IMAGE_DEFINITION when necessary.
GitHub delivery identity
The worker uses the organization-owned screenpipe-windows-development GitHub App, never a personal
access token or personal fork. Install it only on the required repositories,
with contents and pull requests write access (and mandatory metadata read).
Store JSON with clientId, appSlug, and privateKeyPem in the Key Vault
secret screenpipe-windows-github-app. The signing key stays in memory and is
passed to github-app-token.mjs over stdin. The helper verifies the App and
installation and requests a token for the task's one repository. No user OAuth
authorization is used.
GitHub installation tokens expire after one hour. The worker obtains a fresh
token before checkout, after native work before pushing, and before PR
delivery. GH_CONFIG_DIR is task-local. Final cleanup removes the token and
CLI configuration; the result manifest records the bot login and installation
ID. Authentication errors flow into worker stderr and the existing failure
manifest/evidence upload. There is no fallback to a personal credential.
Existing task blobs using githubSecretName must be redispatched with the new
worker and githubAppSecretName; do not rewrite historical task evidence.
Disable every version of screenpipe-github-pr-token and replace the worker
identity's vault-wide read grant with secret-scoped read grants for the OpenAI
secret and this App secret. Old workers then fail to obtain the personal token.
The shared image does not need rebuilding: dispatch supplies the versioned
helper and worker alongside the immutable task blob.
Validate authentication with node --test infra/windows-dev-image/github-app-token.test.mjs,
then prove a real branch push and PR author under the App installation.