Command line

The OmniGet command line does most of what the app does from a terminal or a script: download and preview media, run batches, drive your agents and companies, read usage and browse the catalog. Some commands work on their own; the agent commands talk to the running desktop app.

Where it is

The command line is a separate package, omniget-cli, next to omniget-mcp. The app does not add it to your PATH; put the binaries in a folder that is on your PATH, or run them with their full path. The Claude Code plugin can also download it for you with /omniget:setup.

The binary is omniget-cli. Its own help calls itself omniget, so the examples in --help read omniget …; type omniget-cli instead, unless you created an alias.

Global options

Option	What it does
--json	Output in JSON format, for scripts.
--proxy <url>	Use a proxy for the request.
--help	Help for any command or subcommand.
--version	The version.

Commands that work on their own

These use OmniGet’s download engine directly and do not need the app open.

Command	What it does
download <url>	Download a video or audio. -q quality height (for example 1080), -o output folder, --audio-only, --subs en,pt subtitle languages, --format mp4 (or mkv, webm).
info <url>	Preview title, formats and size without downloading.
batch <file>	Download every URL in a text file, one per line. -m sets how many run at once (default 3), -o the folder.
import-cookies <file>	Import a cookies.txt file (Netscape format) of your own account. -n names the account, --dry-run previews.
read …	Books and comics: meta (metadata of a file), search (legal catalogs such as Project Gutenberg and Standard Ebooks), opds, to-epub (TXT, Markdown or HTML to EPUB), manga, hash.
claude [account]	Open Claude Code on one of the accounts you added in the app. --list, --add, --default, --pick, --remove.
usage	The five-hour and weekly windows and the spend of each Claude Code and Codex account. --days, --watch <seconds>.

omniget-cli info <url>
omniget-cli download <url> -q 1080 -o ~/Videos
omniget-cli download <url> --audio-only
omniget-cli batch links.txt -m 3

Commands that use the running app

These talk to the desktop app over its local bridge. If the app is closed, the command starts it (set OMNIGET_NO_LAUNCH=1 to stop that).

Command	What it does
agent …	Agents of the app: run a task, loop until a check passes, jobs (list, show or --cancel), status, explain, diff, approvals and approve, integrate or discard a worktree job, budget, report, workflow, loops, agents. See Work.
company …	Companies: list, templates, create, show, team, issues, issue, new, comment, move, wake, inbox, costs, runs, audit, export, import. See Companies.
audit	The LLM audit log: who did what to jobs, questions, grants, tokens and agents. --since (for example 12h), --action, --limit.
agentkit …	The Catalog: search, show, install, uninstall, list, doctor, import, export, profiles.
tg …	Telegram: status, chats, ls, dl (from t.me links), dl-chat, watch (auto-save rules), export. Add --local to run without the app.
wmb …	washmybelly: status, caps, scan, plan, show, execute, restore, receipts. execute and restore are approved in the OmniGet window.
canvas …	Talk to the agents, notes and portals wired to this terminal on the Canvas. omniget-cli canvas help lists the subcommands.
guide [topic]	Short reference texts. guide agents explains how to hand work to your agents.

omniget-cli agent run "Fix the failing test" --workspace .
omniget-cli agent loop "Make the tests pass" --check "npm test"
omniget-cli agent approvals
omniget-cli company inbox
omniget-cli agentkit search <term>

hook also exists, but it is run by the coding tools themselves, not by hand.

Other binaries

Binary	What it is
omniget-mcp	A stdio adapter for MCP clients that cannot use HTTP. It forwards to the app’s MCP endpoint, using OMNIGET_MCP_URL and OMNIGET_MCP_TOKEN. See OmniGet as an MCP server.
omniget-worker	A helper the app starts to inspect and download in a separate process. You do not run it by hand.
omniget-gateway	An optional gateway for reaching your own OmniGet from outside, with its own configuration file that only you can read. For advanced setups only.

Common problems

“command not found”

The package is not on your PATH. Use the full path to omniget-cli, or move it to a folder on your PATH.

The agent commands say the app is not running

They need the desktop app. Open OmniGet, or remove OMNIGET_NO_LAUNCH so the command can start it.

The agent commands are refused

They sign in to the app with a local token that the app creates. If you set OMNIGET_TOKEN yourself, check that it is current.