Add --headed, --no-solve-captchas and --no-file-storage

[giordano-lucas]

Follow-up to #60. That PR made the true defaults visible; this makes them actionable.

Three session-start options default to true server-side, which left their flags shaped as opt-ins for something already on. Passing --headless or --solve-captchas changed nothing, and turning either off meant a double negative.

notte sessions start --headed              # was --headless=false
notte sessions start --no-solve-captchas   # was --solve-captchas=false
notte sessions start --no-file-storage     # was --use-file-storage=false

Naming

One rule: use the word the ecosystem already has, otherwise prefix with --no-.

--headed is Playwright's (playwright test --headed), and Notte's users mostly arrive from Playwright or Puppeteer, so it's the one they'll guess. The other two have no comparable term.

--no- rather than --disable- for a reason specific to this command: Chromium's own flags are --disable-*, and sessions start forwards them verbatim through --chrome-args. Distinct prefixes keep the layers legible —

notte sessions start --no-file-storage --chrome-args="--disable-gpu"

— one Notte flag, one browser flag, no ambiguity about which is which. --no- is also what git, docker, npm and curl use.

The originals are deliberately not deprecated

Pinning a value explicitly is legitimate defensive scripting. A caller who needs a headless session shouldn't have to trust that the server default stays true — that's precisely the failure mode #58 and #60 dealt with. Deprecating would also print a warning on the single most common invocation in our own docs (sessions start --headless appears eight times across the skills).

Passing both spellings at once is an error rather than letting precedence quietly pick a winner:

$ notte sessions start --headed --headless
Error: --headed and --headless set the same option; pass only one

Omitting them still sends nothing

The most important property, and the one with a dedicated test: when the new flags are absent, nothing is written to the request body, so the server default applies. Sending an explicit value would re-freeze today's default into the client — the bug #58 fixed.

Verification

Against the live API:

Command	Result
--headed	headless: false
--no-file-storage	use_file_storage: false
--no-solve-captchas	solve_captchas: false
(no flags)	all three true — unchanged
--headed --headless	rejected

• New sessionstart_optout_test.go: absent flags leave the body untouched, each flag inverts its counterpart (including --headed=false → headless=true), conflicting pairs are rejected, and the originals stay registered, visible and undeprecated
• go build, go vet, gofmt -l clean; go test ./internal/... — all 10 packages pass
• New flags live in sessionstart_optout.go, not the generated file, so make generate won't clobber them

Follow-up

notte-skills documents --headless=false and claims it's "not available on remote/CI environments" — but a cloud session accepts it and reports headless: false, so that claim looks wrong. I'll update the skills to use --headed and fix that claim once this lands.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

The PR adds explicit opt-out spellings for three session-start options and moves conflicting-flag validation ahead of session replacement side effects.

• Adds --headed, --no-solve-captchas, and --no-file-storage.
• Rejects conflicting original and opt-out spellings in PreRunE.
• Adds unit coverage for inversion, omission, conflict handling, and original-flag compatibility.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains; conflicting flags are now rejected by the actual session-start command before replacement of the current session begins.

Important Files Changed

Filename	Overview
internal/cmd/sessions.go	Wires session-start validation into PreRunE, ensuring conflicting flags are rejected before the current session can be stopped.
internal/cmd/sessionstart_optout.go	Registers the three opt-out flags, maps them to inverse request values, and validates conflicts with original flags.
internal/cmd/sessionstart_optout_test.go	Adds focused unit tests covering unset request fields, inversion semantics, conflicts, early validation, and continued support for original flags.

_{Reviews (2): Last reviewed commit: "fix: validate session-start flag conflic..." | Re-trigger Greptile}

[giordano-lucas]

@greptile new review