Skip to content

Cloud: cloud.machines reports the app server link's route - #32494

Merged
teamleaderleo merged 1 commit into
feat-cmux-nextfrom
lane/cloud-link-route-report
Nov 2, 2026
Merged

teamleaderleo merged 1 commit into
feat-cmux-nextfrom
lane/cloud-link-route-report

Conversation

@teamleaderleo

@teamleaderleo teamleaderleo commented Nov 2, 2026 •

Copy link
Copy Markdown
Collaborator

The app server link's launcher (CloudService) now records its route, and cloud.machines reports it as link_route: legacy, link, native, or link (native failed: <error>) when CloudNativeFirstLauncher fell back to cmux link.

Why: the item-14 capture v12 baked CMUX_NEXT_CLOUD_NATIVE_LINK=1 and still showed only "cmux link refused the dial: unreachable", so nobody could tell whether Native fell back or never started. Captures record cloud.machines into result.json, so the next run says which path it took.

This is diagnostics only and doesn't change behaviour.

🤖 Generated with Claude Code

Agent session: agent session


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.


Summary by cubic

Reports which route the app server link launched so cloud.machines shows it as link_route: legacy, link, native, or link (native failed: <error>) when the Native-first launcher fell back.

Previously the v12 capture with CMUX_NEXT_CLOUD_NATIVE_LINK=1 only logged "cmux link refused the dial: unreachable", so it was impossible to tell whether Native fell back or never started. Captures record cloud.machines into result.json, so the next run will show the path taken. Diagnostics only; no behavior change.

Written for commit bca1fe1. Summary will update on new commits.

View guided diff Turn on auto-fix

…nk, and why Native fell back)

v12 capture (CMUX_NEXT_CLOUD_NATIVE_LINK=1) showed only 'cmux link refused the dial',
so nobody could tell whether the Native launcher fell back or never ran.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Agent-Session: https://cmux.com/deeplink/agent?id=aid-b3ddf8ea0a5ba6fad749
@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

cmux status (one comment, edited in place; each line is updated by the job that owns it)

Review bca1fe1: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr32494 -f ref=lane/cloud-link-route-report -f platform=macos -f backend_mode=local

Shipped in:

The feat-cmux-next push run https://github.com/manaflow-ai/cmux/actions/runs/41497919334 at f6b340f failed: cmux-next crash ends the app, cmux-next daemon tests.
Those jobs last passed at ac1dcde. This pull request is one of 5 merged since: #32423, #32457, #32494, #32495, #32490.
If the failure is in your change, fix forward on feat-cmux-next. Pull requests run only the tiers their paths reach (docs/ci/cmux-next-tiers.md); label a batch PR full-ci to run them all before merging.

@github-actions github-actions Bot added the risk:normal Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026
@teamleaderleo

Copy link
Copy Markdown
Collaborator Author

Review (subagent claude-opus-5-5 medium): SHIP at bca1fe1
Visual verdict: unchanged by this diff (diagnostics only, no UI).
Checked the route string per launcher branch and the fallback reason. Compile check app passed.
Follow-ups: clear fallbackReason in archive; reduce it to the error type and case.

@teamleaderleo
teamleaderleo merged commit ccb777f into feat-cmux-next Nov 2, 2026
155 of 168 checks passed
@teamleaderleo
teamleaderleo deleted the lane/cloud-link-route-report branch November 2, 2026 18:00
cmux-bot Bot pushed a commit that referenced this pull request Nov 2, 2026
…oudCredentials (tip arch red from ccb777f) (#32506)

* Cloud: the app server link's launcher and route live in CmuxNextCloudCredentials (fixes the tip arch red from ccb777f)

ccb777f (#32494) added +8 CmuxNextApp lines, which turned the tip
arch-ratchet red ([app_lines] +8 over the last green bbb2b89). Fix forward,
behavior identical: CloudService's choice of the app server link's launcher
(none for the legacy link source, cmux link, or the Native-first launcher with
cmux link as its fallback) and the `link_route` text each choice reports are
CloudAppServerLink in CmuxNextCloudCredentials, next to CloudNativeFirstLauncher.
The Native route holder is still made only for the Native choice of an app
server link, and a Native fallback is still logged on app.cloud.

CloudNativeFirstLauncherTests.theAppServerLinkReportsTheRouteItLaunched covers
each branch: the launcher, the route text, and the route after a fallback.

* CloudAppServerLink: one assignment per branch

This branch was previously deployed

1 inactive deployment
ci-routing-agent — bca1fe1c Deployed Nov 2, 2026 by teamleaderleo via namespace autofix #12597
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk:normal Risk tier (docs/ci/risk-tiers.md)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant