Your Hollow workspace from the terminal. Create tasks, write notes, work with files and check monitors without leaving the command line, or call it from your scripts.
curl -fsSL https://api.projecthollow.com/cli/install.sh | shApple silicon (arm64) Macs. The binary goes in ~/.hollow/bin, and one line that loads it is added to your shell profile so a new terminal finds hollow.
curl -fsSL https://api.projecthollow.com/cli/install.sh | shARM64 (aarch64) Linux. The binary goes in ~/.hollow/bin, and one line that loads it is added to your shell profile so a new terminal finds hollow.
Then, in a new terminal
hollow login # sign inhollow whoami # check who you areIntel Macs, x86-64 Linux and Windows do not have a published build yet.
Each group below is a set of commands. The output shown is an example with made-up names and ids; yours shows your own.
Capture a task, see what is open, tick it off and leave a comment on it. Tasks can be named by id or by key, such as ME-14.
task
hollow task create "Review the release notes" --priority high --due-date 2026-11-12Created task: ME-14 [id: t_9f3k2, list: inbox]hollow task list --query "status:open priority:high"Personal [ME] [space: personal_u1] Inbox [list: inbox] (Inbox): 1 task ME-14 "Review the release notes" [id: t_9f3k2, status: To do, priority: high, due: 2026-11-12]hollow task comment add ME-14 "Reviewed, two small fixes needed"Commented on ME-14 [comment: c_41ab]hollow task complete ME-14Completed task: ME-14Write a note from Markdown, including text piped in from another command, then find it again by searching.
note, canvas, table, notebook, folder
hollow note create "Release checklist" --markdown-file checklist.md --notebook WorkCreated note: n_7c1d2 "Release checklist"git log --oneline -5 | hollow note create "Recent commits" --markdown-file -Created note: n_8e4f0 "Recent commits"hollow note search "release""Release checklist" [n_7c1d2, Work] ...tag the build, update the changelog, tell support...Browse Hollow Files, upload and download, and see how much storage you have used. Uploads resume if the connection drops.
files
hollow files upload ./q3-report.pdf /ReportsUploaded "q3-report.pdf" (1.2 MB, id: f_2b8a1) to /Reportshollow files ls /Reportsfile 1.2 MB 2026-11-09 10:42 q3-report.pdf [id: f_2b8a1]hollow files download /Reports/q3-report.pdf --output ./copy.pdfDownloaded "q3-report.pdf" (1.2 MB) to ./copy.pdfWatch a site or service, and see and act on the alerts it raises. Logs and metrics can be sent from scripts.
monitor, alert, alert-rule, channel, maintenance, log, metric, space
hollow monitor create "Marketing site" http https://example.com --interval 5Created monitor: m_5d7e1hollow monitor listm_5d7e1 up http every 5m "Marketing site" https://example.comhollow alert list --state opena_3c9b0 open high "Marketing site is down"hollow alert ack a_3c9b0Acknowledged alert: a_3c9b0Create Git repositories in Hollow and clone them. After one setup step, plain git clone, pull and push sign in for you.
repos
hollow repos create site-notes --initialiseCreated repo: acme/site-notes clone it with: hollow repos clone acme/site-noteshollow repos setup-gitList your automations, trigger one and check how its runs went.
cascade
hollow cascade list"Nightly digest" [id: cs_1a2b3, enabled: true, steps: 4]hollow cascade run cs_1a2b3Triggered run: r_88d0f [running]hollow cascade runs cs_1a2b3 --limit 3[r_88d0f] status: succeededRun a Hollow Code agent session from your terminal on the current folder. It asks before it changes a file or runs a command.
code
hollow code run "Explain what this project does"hollow code projectsportal, hook, queueresearchlogin, whoami, logout, usage, configdocs, update, completion, pingAdd --json to a command that returns data for output a script can read, or --jq with an expression to filter it (this needs jq installed).
hollow login prints a short code and opens your browser to approve it. Check that the code matches the one in your terminal before you approve, and choose which products the key can reach. Use hollow login --no-browser to print the address instead and approve on any device.
hollow whoami hollow whoami --live hollow logout
whoami shows who you are and what the key can reach, and --live checks it with the server. logout clears the key from your computer and revokes it on the server. You need a Hollow account to sign in.
For CI and other places without a browser, create a key in Hollow under Settings, Developer Keys, then give it to the CLI in one of two ways. A HOLLOW_API_KEY environment variable takes precedence over the saved key.
hollow config set --api-key hlw_sk_... # or, for one shell or job export HOLLOW_API_KEY=hlw_sk_...
hollow --version hollow update --check hollow update
hollow update --check only reports whether a newer release exists. hollow update installs the latest release in place, after checking its signature, and never installs an older one. The installer checks every download against a SHA-256 checksum list too.
To install a particular release, or to leave your shell profile alone, pass options to the installer after sh -s --.
curl -fsSL https://api.projecthollow.com/cli/install.sh | sh -s -- --version vX.Y.Z curl -fsSL https://api.projecthollow.com/cli/install.sh | sh -s -- --no-modify-path
Uninstalling removes the binary and the profile line the installer added. Your login and settings in ~/.hollow are kept.
curl -fsSL https://api.projecthollow.com/cli/install.sh | sh -s -- --uninstall
Running the install command again is safe: it does not repeat the profile line.
The full list of commands and flags is built into the CLI, so it always matches the version you have. Reference pages for notes and canvases are built in too.
hollow --help hollow task --help hollow task create --help hollow docs hollow completion zsh
hollow docs lists the built-in reference pages, and hollow completion prints a completion script for bash, zsh or fish. The CLI uses the same public API as everything else, so the API reference describes what sits behind each command.