network requests command requires --filter even when not filtering

[nathanschram]

Description

The network requests command fails with a validation error if the --filter option is not provided, even when you want to see all requests without filtering.

Environment

• agent-browser version: 0.5.0
• OS: Ubuntu 24.04 (Hetzner VPS)
• Access method: Headless via mosh + tmux
• Node.js: v22.14.0
• Chromium: 143.0.7499.4 (installed via agent-browser install --with-deps)

Steps to Reproduce

1. Open a page and let it load:

   agent-browser open "https://example.com"

2. Try to list network requests without a filter:

   agent-browser network requests

Expected Behavior

Should list all captured network requests (or an empty list if none).

Actual Behavior

Error: Validation error: filter: Expected string, received null

Workaround

Provide an empty filter string:

agent-browser network requests --filter ""

Suggested Fix

The --filter option should be optional with a default value of "" (empty string) or the validation should accept null as a valid value.

[giulio-leone]

The --filter flag is no longer required for network requests. Without a filter, all tracked requests are returned. This is addressed in PR #464 (network response + dump commands).