chore: daily morph snapshot update

[github-actions]

Automated daily morph snapshot update.

Changes

• Updated morph snapshots to latest version
• Updated IDE extension and CLI package versions

Test plan

• Verify new snapshots work by starting a sandbox session

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

---

Summary by cubic

Refreshes Morph snapshots to v75 and updates IDE/CLI dependencies to keep sandboxes current and compatible with the latest tooling.

• New Snapshots

  • Added v75 snapshots for the 4 vCPU/16 GB and 8 vCPU/32 GB presets.

• Dependencies

  • VS Code extensions: anthropic/claude-code, openai/chatgpt, ms-vscode/vscode-typescript-next, ms-python/python, ms-python/debugpy.
  • Packages: @openai/codex, @anthropic-ai/claude-code, @google/gemini-cli, opencode-ai, codebuff, @devcontainers/cli, @sourcegraph/amp.

^{Written for commit fd8d3b1. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cmux-client	Error		Jun 9, 2026 6:56pm
cmux-www	Ready	Preview, Comment	Jun 9, 2026 6:56pm

[greptile-apps]

Greptile Summary

This automated daily PR bumps IDE extension versions and CLI package versions in configs/ide-deps.json, and appends new version 75 morph snapshots for the Standard and Performance workspace presets in packages/shared/src/morph-snapshots.json.

• All IDE extensions (claude-code, chatgpt, vscode-typescript-next, ms-python, debugpy) and npm packages (@openai/codex, @anthropic-ai/claude-code, @google/gemini-cli, etc.) receive routine version bumps.
• Two new snapshot entries (version 75) are added to the 4vcpu_16gb_48gb and 8vcpu_32gb_48gb presets; the 6vcpu_24gb_48gb preset remains at version 1, consistent with its historical pattern of not being auto-updated.

Confidence Score: 4/5

Routine automated config update; safe to merge after confirming the ChatGPT extension version format change is expected.

Both files are auto-generated configuration data with no logic changes. The snapshot additions follow the existing pattern. The only item worth a second glance is the openai/chatgpt extension version jumping from 0.5.76 to 26.5602.71036, which may reflect an upstream versioning scheme change — this doesn't affect runtime behaviour but could trip up any version-comparison or display code that assumes SemVer.

configs/ide-deps.json — specifically the chatgpt extension entry.

Important Files Changed

Filename	Overview
configs/ide-deps.json	Version bumps for all IDE extensions and CLI packages; the OpenAI ChatGPT extension version jumps dramatically from 0.5.76 to 26.5602.71036, which may reflect a versioning scheme change worth verifying.
packages/shared/src/morph-snapshots.json	Adds version 75 snapshots to the Standard (4vcpu_16gb_48gb) and Performance (8vcpu_32gb_48gb) presets, and updates the top-level updatedAt timestamp; the 6vcpu_24gb_48gb preset remains at version 1, consistent with its historical pattern.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Daily GitHub Actions Bot] --> B[Fetch latest morph snapshot IDs]
    A --> C[Fetch latest IDE extension versions]
    A --> D[Fetch latest npm package versions]

    B --> E[morph-snapshots.json]
    C --> F[ide-deps.json extensions]
    D --> F

    E --> G{Which presets?}
    G -->|4vcpu_16gb_48gb| H[Append version 75 snapshot_rs3sen0a]
    G -->|8vcpu_32gb_48gb| I[Append version 75 snapshot_2jbzkve0]
    G -->|6vcpu_24gb_48gb| J[Skipped - Still at version 1]

    H --> K[Update updatedAt timestamp]
    I --> K

    K --> L[PR Created]
    F --> L

Loading

_{Reviews (1): Last reviewed commit: "chore: daily morph snapshot update" | Re-trigger Greptile}

[greptile-apps]

Unusual ChatGPT extension version jump

The openai/chatgpt VS Code extension version jumped from 0.5.76 to 26.5602.71036 — a shift from semantic versioning to what appears to be an internal build-number scheme. If the automation pulls the latest marketplace version by package ID, this is likely correct, but it's worth a quick sanity-check that the right extension is being resolved and that downstream logic (e.g. any version-range comparison or display code) handles non-SemVer strings like 26.5602.71036 gracefully.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!