feat(tools): add TinyFish cloud browser provider

[simantak-dabhade]

Summary

Adds TinyFish as a cloud browser provider alongside Browserbase, Browser Use, and Firecrawl. All browser tools route through TinyFish's cloud browser via CDP when selected.

TinyFish provides low-latency cloud browsers with built-in stealth and proxies. Sessions are created via a simple POST request that returns a CDP websocket URL — Hermes connects to it and drives the browser as normal.

Changes

• tools/browser_providers/tinyfish.py — TinyFishBrowserProvider implementing CloudBrowserProvider ABC
• tools/browser_tool.py — register under "tinyfish" key in _PROVIDER_REGISTRY
• hermes_cli/tools_config.py — add TinyFish to the onboarding provider picker
• hermes_cli/config.py — add TINYFISH_API_KEY, TINYFISH_API_URL, TINYFISH_BROWSER_TIMEOUT; bump config version 12 → 13
• hermes_cli/nous_subscription.py — add tinyfish to browser label mapping and feature state resolver
• website/docs/reference/environment-variables.md — document the three new env vars
• website/docs/user-guide/features/browser.md — add TinyFish setup section
• tests/tools/test_browser_camofox_state.py — bump expected config version to 13

Setup

# Add to ~/.hermes/.env
TINYFISH_API_KEY=your_key_here

Get your API key at agent.tinyfish.ai/api-keys. Then select TinyFish as your browser provider:

hermes setup tools
# → Browser Automation → TinyFish

Optional settings:

# Inactivity timeout in seconds (default: 300, silently capped to your plan maximum)
TINYFISH_BROWSER_TIMEOUT=600

# Override API URL for staging/dev
TINYFISH_API_URL=https://staging.api.browser.tinyfish.ai

Implementation notes

• No close endpoint — TinyFish sessions auto-expire on inactivity timeout. close_session() and emergency_cleanup() are intentional no-ops (not laziness — there's genuinely no delete endpoint).
• Auth header — uses X-API-Key rather than Authorization: Bearer, unlike the other providers.
• Managed gateway ready — resolve_managed_tool_gateway("tinyfish") is wired up in _get_config_or_none() so the Nous Portal path works in a future pass without a code change.
• Explicit opt-in only — TinyFish is not added to the auto-detection fallback chain (Browser Use → Browserbase). Users select it explicitly via config or hermes setup tools.

Test plan

• hermes setup tools → TinyFish appears in provider picker with tagline "Low latency browser with stealth & proxies"
• Selecting TinyFish sets browser.cloud_provider: tinyfish in ~/.hermes/config.yaml
• TINYFISH_API_KEY set → is_configured() returns True; unset → False
• hermes → ask agent to navigate to a URL → TinyFish session created, CDP URL returned, browser connects
• Existing Browserbase / Browser Use / Firecrawl / Local / Camofox paths unaffected
• pytest tests/tools/test_browser_camofox_state.py passes with config version 13

[simantak-dabhade]

Hey @alt-glitch @rob-maron — gentle nudge on this one when you have a minute 🙏

This PR adds TinyFish as a cloud browser provider, closely following the pattern from #5628 (Firecrawl) and #5750 (Browser Use) — same file surface, same registry wiring, same env-var + docs structure.

Just rebased onto latest main and resolved the _config_version conflict (bumped to 19). CI is green, no outstanding issues.

Happy to address any feedback. Thanks!

[simantak-dabhade]

Looping in @teknium1 as well in case @alt-glitch and @rob-maron are heads-down on other things — no worries if not, just want to make sure this doesn't fall off the radar.

PR is still rebased clean and mergeable. Happy to address anything. 🙏