Add fast GCP assistant iteration lane#132
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
adamcohenhillel
marked this pull request as ready for review
July 18, 2026 22:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
assistant-apkGCP Lab lane that restores the warm Android snapshot, builds onlyOpenPhoneAssistant, and publishes the signed APK, SHA-256 sidecar, and source refOPENAI_API_KEYfrom GitHub Actions secrets while preserving the ignored local-file fallbackWhy
The AI Phone iteration loop depended on a full Android image build, one GCP zone, and machine-local eval secret files. That made assistant-only changes slower and made the CI path fragile after moving development to a new computer or when the primary GCP zone had no capacity.
Impact
Assistant changes can return a pushable APK without rebuilding/exporting a complete image. GCP capacity shortages can fail over without hiding build, permission, or configuration failures. The persistent physical-device runner can execute eval workflows using the existing repository secret instead of requiring a copied secret file.
Validation
./scripts/check.shgit diff --checkopenphone_agentopenphone-deviceself-hosted runner confirmed online and idleNot run
actionlintwas not installed locally