Summary
Please add first-class cookie management commands to Rodney. PR to follow created with Red/Green TDD and GPT5.4.
Cookie handling is a practical requirement for authenticated browser automation, and the --help / -h output for these commands should be treated as part of the public contract because Rodney is designed for CLI-driven agent use.
Proposed commands
rodney cookie set <name> <value> --domain <domain> [--path <path>] [--secure] [--http-only] [--same-site <mode>]
Set a browser cookie for a domain
rodney cookie list List cookies for the current page URL
rodney cookie get <name> Print a cookie value for the current page URL
rodney cookie delete <name> --domain <domain> [--path <path>]
Delete a browser cookie by domain/path
Command behavior
rodney cookie set
Sets a cookie in the running browser session.
Required inputs:
- cookie name
- cookie value
--domain
Optional inputs:
--path
--secure
--http-only
--same-site <strict|lax|none>
Example:
rodney cookie set session abc123 --domain rodney.example.com
rodney cookie set prefs dark --domain rodney.example.com --path /app --http-only --same-site lax
rodney cookie list
Lists cookies that apply to the current page URL.
Expected output:
- one cookie per line
- readable CLI format
- suitable for shell use
Example:
rodney cookie list
session=abc123
prefs=dark
rodney cookie get
Prints the value for a named cookie that applies to the current page URL.
Expected behavior:
- print only the cookie value on success
- if the cookie is missing, fail cleanly with a non-zero exit status
Example:
rodney cookie get session
abc123
rodney cookie delete
Deletes a named cookie by domain, with optional path.
Expected behavior:
- require
--domain
- default
--path to /
- fail cleanly with a non-zero exit status if the cookie is not found
Example:
rodney cookie delete session --domain rodney.example.com
rodney cookie delete prefs --domain rodney.example.com --path /app
Help text requirement
The new commands should appear in the main rodney --help output in the same concise style as the existing commands. The help text should be sufficient for an agent to discover and use the feature without external explanation.
Why this matters
This fills an important gap for authenticated browser workflows while keeping Rodney in the same shell-friendly, composable style as the rest of the tool.
Summary
Please add first-class cookie management commands to Rodney. PR to follow created with Red/Green TDD and GPT5.4.
Cookie handling is a practical requirement for authenticated browser automation, and the
--help/-houtput for these commands should be treated as part of the public contract because Rodney is designed for CLI-driven agent use.Proposed commands
Command behavior
rodney cookie setSets a cookie in the running browser session.
Required inputs:
--domainOptional inputs:
--path--secure--http-only--same-site <strict|lax|none>Example:
rodney cookie listLists cookies that apply to the current page URL.
Expected output:
Example:
rodney cookie getPrints the value for a named cookie that applies to the current page URL.
Expected behavior:
Example:
rodney cookie deleteDeletes a named cookie by domain, with optional path.
Expected behavior:
--domain--pathto/Example:
Help text requirement
The new commands should appear in the main
rodney --helpoutput in the same concise style as the existing commands. The help text should be sufficient for an agent to discover and use the feature without external explanation.Why this matters
This fills an important gap for authenticated browser workflows while keeping Rodney in the same shell-friendly, composable style as the rest of the tool.