Permissions and Transfer Workflows
This page covers the newer TUI workflows that make remote and long-running sessions easier to manage: approval modes, local attachments, remote file browsing, and bidirectional transfers.
Permission Modes
Use /permissions to inspect or change approval behavior:
/permissions
/permissions ask
/permissions accept-edits
/permissions full-auto
| Mode | Behavior |
|---|---|
ask | Prompt before bash and file edits (default) |
accept-edits | Auto-approve in-project edits, still ask before shell commands |
full-auto | Auto-approve most actions, with sensitive-path protections still enforced |
You can also set this through config:
/config set permissions.mode accept-edits
When prompted, approvals accept natural responses such as allow / deny (and shortcuts like a / d).
Attach Local Files to Next Message
Queue files from your local TUI machine:
/attach
/attach <path>
/attach list
/attach clear
- Use
/attachwith no arguments to open a local picker. - Queued files are included with your next submitted prompt.
- This is ideal for screenshots, logs, and artifacts you want the daemon-side agent to inspect.
Browse Remote Daemon Files
Use /remote-files to open the daemon-host browser:
/remote-files
Keyboard controls:
Up/Down: navigate entriesSpace: toggle multi-select on filesEnter: open directory or copy selected file(s) locallyBackspace: go to parent directoryEsc: close picker
Copied files are written into your current local working directory.
Bidirectional File Transfer
Use /transfer for explicit local/remote direction:
/transfer remote
/transfer local
/transfer remote: open remote browser and copy file(s) from daemon host to local machine./transfer local: open local picker and upload a file from local machine to daemon host.
This is useful when your daemon runs on a remote box and you need to move files in either direction without leaving muxd.
Spinner and Background Job Visibility
For long-running tasks, you can tune status feedback:
/spinner
/config set theme.spinner mini-dot
The activity line now distinguishes normal tool execution from background shell jobs (bash_background), so you can see when remote work is still active between turns.