WebCull CLI Is A Programmable Bookmark Interface
The WebCull CLI lets you, your scripts, and your agent tools inspect and update bookmarks from a terminal. Search and browse your collection, use graph commands to see how saved items relate, and make precise changes without opening the app.
webcull <command> [options]
Install And Run The CLI
Install from npm, authorize WebCull, then run a small command. Agent skills are optional for guided agent workflows.
npm install -g @webcull/cli.
webcull login, then approve the request in your browser with the intended account.
webcull accounts, choose an account hash, then include --account <hash> on authenticated commands.
webcull@webcull/clihttps://api.webcull.com~/.config/webcull/config.jsonRun These Commands First
These commands establish account access, show current limits, and inspect the account without requesting a large result. They are the safest starting point for humans, scripts, and agents.
webcull login
webcull accounts
webcull whoami --account <account-hash>
webcull limits --account <account-hash>
webcull bookmarks count --account <account-hash> --path /
webcull bookmarks tree --account <account-hash> --path / --max-depth 1 --limit 25 --max-chars 8000 --fields id,type,title,modified
Choose The Smallest Command That Answers The Question
Account Tokens And E2EE Passphrases
Browser approval gives each account a CLI access token. Your computer keeps it in protected password storage, not in the CLI settings file. The token expires after seven days, and webcull logout revokes it sooner.
Your E2EE passphrase is separate from the account token. Keep it in a keystore you control and pipe it directly to the CLI with --e2ee-passphrase-stdin when encrypted fields are needed. The CLI derives a key in memory for that command; it saves neither the passphrase nor the key and sends neither to WebCull. Never put the passphrase in command arguments, environment variables, config files, plaintext files, or logs.