[teamleaderleo]

Leo: "whenever i start a chat it should be able to send me to cloud automatically".

What was wrong

Once #29107 and #29497 got a fresh Cloud machine past the team gate, the creator's first chat was still refused, in two steps.

1. Folder. A new chat with no folder of the person's own takes the workspace's first terminal folder (remoteFolder). cmux cloud start-session opens a terminal on the machine first, and a first send in a machine workspace uses the same terminal folder. On a fresh machine that terminal sits in $HOME, so agent-session-start refused it as agent_session.home_unconfirmed. The app reads that code as "needs a folder on that machine to start in". The nightly signed-in capture showed this on a fresh machine (hq run 41224623701).
2. Trust. The machine's own ~/work would be refused next with agent_session.untrusted_folder. acpmux's auto-trust is off by default (agents.trust.autoTrust), so nothing trusts it. Leo's VM reached this step after the owner gate.

Neither step depends on the image: every image puts a fresh terminal in $HOME.

What changes

The changes are in cmux-tui (Rust), and they ship to machines through the app's own update of the machine's cmux-tui (#29497).

They apply only on the caller's own Cloud VM. That means the machine kind gate reads a Cloud VM (a team VM included) and the caller's vm_kind is exactly owner, the Cloud API's answer for the machine's creator.

• agent-session-start: a start in an unconfirmed home folder starts in the machine's work folder instead ($HOME/work, made if missing).
• Trust: acpmux's trust answer for exactly $HOME/work reads trusted, with decided and auto: "cloud_work", mirroring how acpmux answers a folder cmux made. This applies at the start and in agent-session-trust's read, so the app's page asks nothing either.
• What still wins: the person's "Don't trust" (an acpmux decision) and an agent's own untrusted level.
• Unchanged: any other folder on that machine, a home folder the person chose (Use Home Folder), any machine that isn't a Cloud VM, and any caller without the owner word.

Tests

a_first_chat_on_the_callers_own_cloud_vm_starts_in_its_trusted_work_folder (cmux-tui tests/cli/agent_session_start.rs):

• On an owner VM, and on a team VM with the creator's word:
  • the trust read for ~/work answers trusted / cloud_work;
  • without the owner word it is refused;
  • a start at $HOME starts, and makes ~/work;
  • another folder still answers untrusted_folder.
• The person's "Don't trust" on ~/work still refuses.
• A machine that isn't a Cloud VM still answers home_unconfirmed for its home.

Risk

This decides folder trust for one folder on one kind of machine: the work folder of the caller's own Cloud VM, which is a disposable sandbox the person owns. The daemon already lets any agent family run there (#28613). It records nothing in acpmux; the person's own answers still override it.

Agent session: agent session

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Fixes a creator's first chat on their own Cloud VM so it starts in the machine's work folder with no trust question.

On a fresh Cloud machine, a new chat with no folder of the person's own starts in the workspace's first terminal folder ($HOME), which agent-session-start refused as agent_session.home_unconfirmed; the machine's own ~/work was refused next as agent_session.untrusted_folder because acpmux's auto-trust is off by default.

Changes

• On the caller's own Cloud VM, an unconfirmed home folder becomes $HOME/work, made if missing, and that folder reads trusted with auto: "cloud_work" at start and in the trust page, so no question is asked.
• On a team VM, a start passes the folder and its trust, then asks for an agent that asks before acting (agent_session.not_asking).
• A person's "Don't trust" and an agent's own untrusted level still win.
• Any other folder, a home folder the person chose, any non-Cloud VM, and callers without the owner word keep today's rules.

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

[teamleaderleo]

Owned by an agent session · session

[github-actions]

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

Review 7a7a2ac: 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=pr29556 -f ref=lane/cloud-owner-first-chat-work-folder -f platform=macos -f backend_mode=local

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4123304565901 (8769d23ba2)

[blacksmith-sh]

Found 3 test failures on Blacksmith runners:

Failures

Test	View Logs
tab: tabGroup.addTab is not a top-level row/tab: tabGroup.addTab is not a top-level row	View Logs
tab: tabGroup.create is not a top-level row/tab: tabGroup.create is not a top-level row	View Logs
tab: tabGroup.removeTab is not a top-level row/ tab: tabGroup.removeTab is not a top-level row	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[teamleaderleo]

Review (codex, router-review): SHIP at 7a7a2ac

Reviewer: codex gpt-6.1-sol xhigh, fast tier.

Follow-ups: 1. Each lands as an issue in this repo that links this receipt; the lane that opened the PR fixes it forward.

SHIP at 7a7a2ac
Visual verdict: no images; Leo tries the build

1. [P2] [follow-up] Return the redirected folder in trust refusals — agent_session_start.rs:296. When ~/work has a saved “Don’t trust” decision, a start at $HOME redirects there and returns untrusted_folder without the effective cwd. The app consequently labels the refusal with the original $HOME (AgentTabs+RemoteStart.swift:98). Its Trust action then fails with home_unconfirmed instead of clearing the work folder’s refusal. Return and consume the effective cwd for this recovery path.

Rust tests were not run: no Rust toolchain is installed.

Follow-ups:

• Finding 1: Make trust recovery target the redirected ~/work folder.

[teamleaderleo]

Review (codex, router-review): SHIP at e4f1815

Reviewer: codex gpt-6-astra high, fast tier.

SHIP at e4f1815

Visual verdict: no images; Leo tries the build.

No correctness findings.

Follow-ups: none

[teamleaderleo]

Review (codex, router-review): SHIP at eaa7f1d

Reviewer: codex gpt-6.1-sol xhigh, fast tier.

SHIP at eaa7f1d

Visual verdict: no images; Leo tries the build

No correctness findings. Focused tests could not run because Rust tooling is unavailable in the review box.

Follow-ups: none