syq exec
Run a command on a connected receiving machine, with approval on that machine:
syq exec --on @laptop --cwd work/project -- cargo test
See Run commands on your laptop for setup and examples.
syq exec [OPTIONS] --on <@NAME> -- <PROGRAM>...
Arguments
| Argument / option | Meaning |
|---|---|
<PROGRAM>... | Program and literal arguments; use sh -c explicitly for shell syntax |
Options
| Argument / option | Meaning |
|---|---|
--on <@NAME> | Receiving name; requires a live return connection (never falls back to SSH) |
-C, --cwd <DIR> | Working directory on that machine, relative to its receiving directory [default: .] |
Help and version
| Argument / option | Meaning |
|---|---|
-h, --help | Show common usage and options |
--help-all | Show all options and details |
Approve each command locally
Every command requires approval on the receiving machine, even if copies are approved automatically. Review the program, arguments, requesting server, and working directory. If the desktop prompt is missing or truncated, inspect and answer the request from a local terminal:
syq persist receive pending
syq persist receive approve REQUEST_ID
syq persist receive deny REQUEST_ID
Requests expire after five minutes. Commands run with your local user’s
permissions; the receiving --root and copy limits do not contain them.
See Commands on your laptop for the
trust boundary.
Arguments and working directories
Put -- before the program. Everything after it is passed as a literal
argument, including strings starting with --. There is no implicit shell
expansion on the receiving machine. To use shell syntax, request a shell:
syq exec --on @laptop --cwd work/project -- sh -c 'cargo build && ./target/debug/demo'
--cwd DIR (or -C DIR) is relative to the profile’s effective starting directory
(shown by persist receive status). Its default is that directory. Absolute paths and
.. can select elsewhere. The directory must exist. Syq does not expand ~
on the receiving machine; use a relative path or an absolute path instead.
The command inherits the receiving service’s local environment, including
PATH and its desktop session. It does not inherit the server’s environment.
Restart receiving from a terminal in the desired desktop session when those
values change. Stdin is closed and there is no interactive terminal.
Output, completion and cancellation
Stdout and stderr stream back to your terminal, and syq returns the command’s
exit code, or 128 + signal if it was killed by a signal. Setup and connection
failures return nonzero; losing the exit status is an error. Commands are not
retried automatically, and completed file changes are not rolled back.
Interrupting the request, stopping or changing receiving, or losing the
connection forcibly stops the command’s process group. Cleanup handlers do not
run. Remaining children in that group are also stopped when the foreground
program exits. Detached processes and applications launched through macOS
open can survive this cleanup. Commands do not emit copy receipts or copy
automation records.
Execution details
Requests allow up to 256 arguments (16 KiB total) and a 4096-byte working-directory path. Each server connection permits one pending approval and eight active commands.