Commands
app
Manage the local Poly desktop app.
poly app manages the local Poly desktop app. The CLI never talks to the server directly — it connects to the desktop app over a local socket, and the desktop app acts as a daemon that owns the websocket connection, the local cache database, and the OAuth session. Most poly commands need this daemon running; if it isn't, they fail with a hint to run poly app start.
Usage
poly app <SUBCOMMAND>
Subcommands
| Subcommand | Description |
|---|---|
start | Start the Poly app in background (daemon) mode — launches hidden, with no window. |
status | Show whether the app is running and its current state. |
open <FILE_REF> | Open a file or folder in the Poly app UI. |
logs | Show app logs. -f, --follow tails like tail -f; -n, --lines <N> sets how many lines to show (default 200). |
restart | Restart the daemon. |
quit | Quit the app. |
root | Print the local Poly sync root directory path. |
Examples
# Start the app hidden in the background
poly app start
# Check whether the daemon is running
poly app status
# Open a folder in the Poly app UI
poly app open //Home/projects
# Follow the last 50 lines of app logs
poly app logs -f -n 50
# Restart the daemon after a config change
poly app restart
# Jump into the sync root in your shell
cd "$(poly app root)"
Related
auth— log in and out of Poly.- How it Works — the daemon, local cache, and connection model.
- Installation — installing the
polyCLI.