Repo-aware file workflow

Agents propose edits; humans stay in control. Workspaces anchor the hub to real trees on disk so proposals always resolve to something you can open in the editor.

Proposal → review → apply

When an agent attaches a file change to a message, the hub registers a structured proposal. The desktop Pending changes panel shows each item with a diff preview. Approve applies the patch to the workspace; reject discards it and records the decision for the thread.

Slash commands in the loop

Commands such as /list-file-changes, /approve-file, and /reject-file mirror the UI for keyboard-first workflows or remote automation. They share the same backend state as the palette actions.

Workspaces

Workspaces are first-class objects in the hub: add paths, list roots, and route file APIs relative to a chosen workspace. That keeps multi-repo or monorepo layouts explicit instead of silently assuming a single cwd.

Safety properties

Paths are checked for containment within the configured workspace root before reads or writes. Combined with human approval, this is the guardrail between “agent suggested” and “agent mutated production.”