sabx

Topics in the source

• SABnzbd CLI
• Common reads
• Changes
• Connection diagnosis

Use sabx for SABnzbd reads and changes. Start with the requested operation; check installation, authentication, or connection settings only when a command fails for that reason. Search references/commands.md for exact flags and less common commands. Prefer --json when another tool will consume the result. Use --profile NAME only when the user selects a non-active profile. Resolve the queue item, history item, category, server, feed, or schedule entry before changing it. Commands that add an NZB, reorder or delete items, clear history, pause or resume processing, change limits, edit feeds/schedules, or enable/disable servers change SABnzbd state. Follow the user's authorization for the concrete change. Do not interpret "clean up" as permission to delete queue items or all history; ask what should be removed if the target is not explicit. After an ambiguous timeout, read back queue/history/server state before retrying a mutation. Never expose the SABnzbd API key in output, logs, commands, or messages. Typical operations: Use the command reference before deletion, RSS, scheduler, server, or configuration changes. If a command reports no configuration, authenticate with the supported c

This is an excerpt. Refer to the complete source and its current requirements.