Bake CPU torch and MCP allowlist into Cloud Agent snapshots - #17
Merged
Merged
Conversation
The Sept 19 snapshot this environment boots from only ran pip + the docs MCP shim. New agents still had to install torch at runtime, and Cloud stdio had no allowlisted PATH command. Snapshot install now runs cloud-install.sh; start only refreshes the shim. Co-authored-by: ale93.moro <ale93.moro@gmail.com>
command -v missed the MCP shim because install shells do not have $HOME/.local/bin on PATH. Export it and test the shim by absolute path. Co-authored-by: ale93.moro <ale93.moro@gmail.com>
alex-16moro
marked this pull request as ready for review
September 20, 2026 11:35
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
2 participants
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.
Summary
The Configuration tab on snapshot
bld-20260919-df62bfdd-806d-4125-8bb0-448a5615a04bis install-only (pip install -r requirements.txt && bash .cursor/install-docs-mcp.sh). That snapshot is what this Cloud environment still boots (gitSetup: reuse).startalready landed onmainvia PR #15, but install still does not bake CPU torch/diffusers, does not self-test the docs MCP server, and does not allowlist the Cloud stdio commanddiffusers-docs-mcp.This change:
.cursor/cloud-install.sh(pyyaml, CPU torch, diffusers, MCP PATH shim,docs_mcp_server.py --selftest).cursor/environment.jsoninstallat that script; keepsstartas the shim-only refreshoverlay/environment.jsonfor fork launchesdiffusers-docs-mcp(does not register Hub HTTP)Convention gate
N/A — no scheduler/model source changes.
Tests run
Local:
Draft builds of environment 69ccaac6-b427-11f1-bb68-864e54d14197:
INSTALL_FAILEDoncommand -v diffusers-docs-mcp(PATH). Fixed in75cb3fd.SUCCEEDED. Install exit 0: torch 2.14.0+cpu, diffusers 0.40.0, MCP self-test OK, shim present.Fresh-agent verify on that successful snapshot (
cloud_requested_environment_build_id=bld-20260920-fa15e62f-77a9-4d4c-a333-e0e294ab6de6, branchcursor/env-torch-mcp-start-3eed): torch/diffusers import without pip, start script exit 0, MCP self-test OK.Human judgment (not the gate)
diffusers-docs-mcp(this running agent cannot reconnect MCP mid-run)