searchts

searchts

A keyless web unlocker and reader for AI agents. (Off the record: "search this shit".)

It reads the page, or it tells your agent plainly that it can't.

When Claude, Cursor, Codex or another agent fetches a URL, it regularly comes back with junk: a 403 bot wall, an empty JavaScript shell, a truncated AI-chat share link, or a login screen that the model happily summarizes as if it were the article. searchts is the reader your agent calls instead. It is open source (MIT), free, needs no API key, refuses paid residential proxies by default, and runs as an MCP server, a CLI or a Python library.

[CI] [PyPI] [Python] [Downloads] [License: MIT]

[A Claude agent's fetch hits a 403 bot wall, so it routes through searchts, reads the page, and answers the question]
▶ Watch the full 1-minute demo

One-line agent install

Add searchts to Claude Code, Cursor or any MCP client in one command. No API key:

claude mcp add searchts -- uvx --from "searchts[mcp]" searchts mcp serve

Keep it globally and add the stealth browser, which the hardest rungs use:

pipx install "searchts[mcp]" && searchts install --browserclaude mcp add searchts -- searchts mcp serve

Install covers uvx, pipx, venv and the browser extra. The CLI, the MCP server and the Python library all call the same read path.

Three things your agent's built-in fetch can't do

1. Decode full ChatGPT, Claude, Gemini, Grok, Poe, DeepSeek, Perplexity and Copilot share links

A shared conversation never sits in the initial page HTML as plain text. A raw fetch gets a JavaScript shell; a renderer can still cut the chat off mid-thread. searchts read recognizes share URLs and decodes each provider's own data channel into complete, role-labeled Markdown, keyless and without logging in:

searchts read https://chatgpt.com/share/...        # turbo-stream payload in the page (no browser)searchts read https://claude.ai/share/...          # keyless snapshot API behind Cloudflare (no browser)searchts read https://gemini.google.com/share/...  # keyless batchexecute RPC (no browser)searchts read https://chat.deepseek.com/share/...  # stealth render, auto-scrolls past list virtualization

Eight providers: ChatGPT (both /share/<uuid> and the newer /s/<prefix>_<id> short links), Claude, Gemini, Grok, Poe, DeepSeek, Perplexity and Copilot. The first five need no browser. The last three reuse the stealth tier, scroll until the page height stops changing, open the folds, then read.

2. Escalate past bot walls, or fail loudly instead of hallucinating on a login screen

Every searchts read walks a three-tier open-source unlocker and remembers which rung worked per domain:

• curl_cffi impersonates a real Chrome TLS/JA3 and HTTP/2 fingerprint. Fast, local, private.
• Jina Reader (r.jina.ai) renders JavaScript when the page only fills in after it runs. Default on; SEARCHTS_NO_JINA=1 keeps the URL off Jina's servers.
• patchright is a lazy stealth Chromium, started only when the cheaper tiers fail.
• --human opens a real browser when only a person can clear the page.

searchts read https://some-js-heavy-or-fingerprinted-site.com --scrub# Tier 1 (curl_cffi) -> 403 | Tier 2 (Jina) -> clean Markdown returned, injection scrubbed
searchts read https://www.linkedin.com/in/someone/# Signed out: fails loudly with the exact tier and login-wall reason, stdout empty.# With a kept login: the profile, and its Experience and Education, as one page.
searchts read https://www.linkedin.com/company/acme/posts/# Company pages and their posts read natively; a rate limit says so instead of "expired".

--scrub strips invisible and bidi characters and flags prompt-injection indicators before untrusted text reaches your model.

A login you hand over is different from a login searchts guesses. In 0.15.0, local reuse is opt-in and fenced to the one host in the command: --cookies-from-browser <browser> --yes, --cookies <path>, or --cdp-port <port>. Without one of those, a wall is an error, not an article.

3. Transcribe videos and grab fingerprint-gated design assets

searchts transcribe https://youtu.be/...                     # YouTube, TikTok, Instagram Reels, Redditsearchts transcribe https://www.instagram.com/reel/... --cookies-from-browser chromesearchts grab https://stripe.com --kinds images,fonts,svg --read --out ./stripe-kit

Transcription is subtitles-first, then yt-dlp audio plus Whisper when there are no captions. grab extracts a page's images, icons, CSS, fonts, SVGs and color palette through the same unlocker, so it works on fingerprint-gated CDNs, not just open ones.

Native web search

A built-in fetch does not search. searchts search is keyless DuckDuckGo by default, with reciprocal rank fusion across SearXNG, Exa, Brave, and Tavily. A snippet is not the page. Read each URL.

searchts search "open source vector db"

Why it exists

I built searchts because Claude kept running into walls when I asked it to read the web for me. The trigger was a Devpost hackathon page and its terms: the page wasn't even walled, and Claude still couldn't read it.

The first versions, which I built with Claude, failed the other way. When they couldn't get a page, they handed back whatever they got, and the agent summarised a loading screen as if it were the article. So searchts has one rule above the rest: return the real page, or fail loudly and say why. It never hands your agent a fake read.

How searchts compares

searchts grew out of Agent-Reach's channel/doctor scaffolding, then replaced the read/search core with an escalating unlocker, share-link decoders and an MCP server.

What it does

• Reads pages your agent's own fetch can't: browser-fingerprint checks, JavaScript-only pages and some bot walls
• Fails loudly when the read is not the real page (a login the user did not hand over, a puzzle that needs a person, a block that is the address) and says which tier failed and why
• Reads complete ChatGPT / Claude / Gemini / Grok / Poe / DeepSeek / Perplexity / Copilot shared conversations
• Works with Claude, Codex, and MCP agents
• Extracts clean Markdown, ready to feed a model
• Says when a page has more than it returned (a next page, a feed, folded text) and rebuilds search results and feeds the extractor mangles
• Searches the web without API keys (DuckDuckGo, plus SearXNG, Exa, Brave, and Tavily). A snippet is not the page
• Downloads a page's assets (images, fonts, palette)
• Transcribes videos, subtitles-first
• Names images, video, and embeds in the page. searchts get <url> fetches one of those URLs through the same ladder
• On a player page, returns the captions, or fails and names searchts transcribe for the audio

When a read names a next step

search prints a list of URLs and a line that says the snippet is not the page. Read each URL.

A player page (a YouTube watch URL, a TikTok video, an Instagram reel, a v.redd.it file, or an X post that has a video) comes back as the captions, or fails with empty stdout and names searchts transcribe for the audio. An X post with no video is still a read of the page. Captions need no key. Audio is the transcribe command, not a second reader.

searchts transcribe https://youtu.be/...                     # audio, when read found no captionssearchts transcribe https://www.instagram.com/reel/... --cookies-from-browser chromesearchts get https://example.com/logo.svg -o logo.svg        # one file a read namedsearchts grab https://stripe.com --kinds images,fonts,svg --read --out ./stripe-kit

Local transcription ships with whisper.cpp. The default quantized small model is about 190 MB and downloads only when a transcription reaches audio and you approve it: a terminal asks once, while an agent gets a structured consent result with the model size, source, cache path and exact --yes retry. Cached models work offline. Select small, turbo or base with --model, the whisper_model config key, or SEARCHTS_WHISPER_MODEL; --hint supplies names or other words to the decoder, and --translate opts into English output (not supported by turbo). Use searchts transcribe --list-models to inspect the cache and searchts transcribe --remove-model small --yes to remove a cached model after approval. faster-whisper remains an explicit migration fallback with --provider local-fw while it is installed. The published pywhispercpp wheels are CPU builds on Linux and Windows: CPython 3.10-3.14 wheels cover Linux x64/arm64, Windows x64 and macOS arm64; Windows arm64 and macOS x64 have no wheel. The macOS arm64 wheel ships whisper.cpp's Metal backend with an embedded metallib, so an Apple Silicon install can run on the GPU; the Linux and Windows wheels ship no GPU backend, so Vulkan and CUDA wheels are still a follow-up.

grab saves the set of files when the files are the deliverable. It uses the same unlocker, so a fingerprint-gated CDN is the same ladder as a read.

Why the package is free

The package you install is free and keyless. The fetch and the browser run on your machine, from your connection. It does not bundle a residential proxy. Jina Reader, the one hosted rung, is free and can be turned off. That is not a promise that every hard page is free forever. A read that needs an exit we operate is a different product, not a default of this package. The scorecard is what this build actually read, not a list of walls that can never be passed.

The unlocker

searchts reads any URL through an escalating ladder and stops at the first tier that returns real content:

1. curl_cffi: a fetch that impersonates a real Chrome's TLS/JA3 and HTTP2 fingerprint. Beats user-agent and fingerprint filters. Fast, local, private.
2. Jina Reader: a JavaScript-rendering relay (r.jina.ai), for pages that only fill in content after running JS. Default on — the target URL is sent to Jina's servers on this rung. Opt out with SEARCHTS_NO_JINA=1 or config jina: false (local curl + stealth only).
3. stealth browser: an undetected headless Chromium (patchright), launched lazily only when the cheaper tiers fail, for live JS / Cloudflare managed challenges.

If no tier comes back with real content, an optional human-in-the-loop step opens a real browser so you can clear the page once and continue. That covers interactive CAPTCHAs and soft walls alike: a login page served as HTTP 200 is not a challenge, but it is still a page only a human gets past. Block detection is phrase-based (not vendor-name based), so legitimate pages that merely embed a bot-sensor script are not falsely rejected. Content is extracted to clean Markdown with trafilatura.

What it won't do. It will not pretend a wall page is the article. A login the user did not hand over still fails, with the reason. Local reuse shipped in 0.15.0, only when you hand searchts a session for the one site in the command (--cookies-from-browser <browser> --yes, --cookies <path>, or --cdp-port <port>). Firefox-based Zen profiles are read-only SQLite; Chromium browsers such as Vivaldi are opened on a loopback CDP port with a throwaway profile copy, which searchts deletes afterwards. No Chrome installation or PATH entry is required to use Vivaldi. Signing in on a remote browser is not built (F27). A DataDome device-check is not a permanent failure: the stealth browser is supposed to let that script finish, and to take a simple click (continue, a checkbox, a press-and-hold that is one action). A puzzle that asks a person to recognize images still stops. The package will not route you through a paid residential proxy by default. A release never claims a site reads until it does. datadome.co is still a fail on the current scorecard. That is a measurement, not a rule.

AI-chat share links

Share links from AI chat apps are a special kind of hard: the conversation never appears in the page HTML as extractable text, so a raw fetch returns an empty shell, and a renderer can still cut it off mid-chat. searchts read recognizes these URLs and decodes each provider's own data channel instead, returning the complete conversation as role-labeled Markdown — keyless, no login:

The first five need no browser. The last three are JavaScript shells with nothing in the initial HTML, so those reuse the stealth tier: wait for the conversation to render, auto-scroll until the page height stops changing (list virtualization will otherwise truncate a long chat), then expand the collapsed sections before reading. The benchmark currently covers the five that read without a browser; the three that need one are not in it yet.

ChatGPT issues two shapes: /share/<uuid> for a whole conversation, and the newer /s/<prefix>_<id> short links for a single shared turn (t_ thread, m_ message, dr_ deep research, cd_ Codex). Both are read.

Each provider is a drop-in plugin module (searchts/share_extractors/); if a provider changes its format, extraction falls back to the normal unlocker ladder instead of failing.

Does it actually work?

Rather than take our word for it, searchts ships a reproducible two-suite benchmark: it runs the unlocker over two page sets and reports how many it read — keyless — and which tier carried each.

• Smoke — a small public page set (control, open docs, AI-chat share links). A regression canary, not evidence about hard bot-walls.
• Walled — real vendors that restrict bots (Reddit, LinkedIn login wall, a Cloudflare/DataDome-class site, X, Booking). A short body under the unlocker's minimum-content threshold is a fail, not a pass; expected walled failures are reported honestly, not papered over with 100%.

The last committed run read 12/12 Smoke and 2/7 Walled. The walled number is the point: five real walls are reported as failures instead of hidden behind a fake 100%.

These two are reported separately on purpose — the smoke number is not "does it work on walls." See benchmarks/README.md.

python -m benchmarks.run                       # both suites, print a scorecardpython -m benchmarks.run --suite walled       # the real walled pass rate onlypython -m benchmarks.run --out docs/          # write docs/scorecard.md + results.json

Latest run: docs/scorecard.md. Add your own targets — see benchmarks/README.md.

The numbers only mean something from a residential connection: a datacenter IP (or a VPN that reshapes your TLS fingerprint) blocks the fast curl_cffi tier more than a real user sees.

Install

Keep it (global isolated CLI, MCP extra included):

pipx install "searchts[mcp]"

Try it without installing (one-shot, copy-paste):

uvx --from "searchts[mcp]" searchts <verb>

venv / packaging only (not the recommended path for the CLI):

python -m venv .venvsource .venv/bin/activate   # Windows: .venv\Scripts\activatepip install "searchts[mcp]"

A plain install already includes the stealth browser library (patchright), browser cookies, the MCP server, a bundled ffmpeg and the JavaScript runtime YouTube needs (deno, through yt-dlp[deno]). Nothing needs a system install. The [mcp], [browser] and [cookies] extras still resolve, as empty aliases, so existing specs keep working.

First-pass setup. One list with sizes, one approval, and every item checked by default: Chromium for the stealth browser (~170 MB), twitter-cli for X (~39 MB), rdt-cli for Reddit (~15 MB), mcporter (~77 MB, needs Node.js) and gh for GitHub (~13 MB). LinkedIn reads natively once a login is kept, so linkedin-scraper-mcp is now an optional fallback (feed and write/inbox tools, ~214 MB) that --only linkedin installs. The local Whisper model is listed with its size and asked for the first time you transcribe locally. Site logins aren't part of this approval; each site asks when a read needs one.

searchts install                                 # a terminal asks once; type ids to unchecksearchts install --yes --skip mcporter,gh        # agents: no prompt, nothing outside the listsearchts install --only linkedin                 # the optional LinkedIn fallback and mcportersearchts install --dry-run --json                # the list as searchts.setup.v1, changes nothing

Without a terminal and without --yes, nothing on the list is installed; the list and the exact approve command are printed instead. Only the stealth browser: searchts install --browser.

Update the copy that is running (searchts upgrade is the same command):

searchts update

Windows: quote URLs (PowerShell and cmd)

In PowerShell an unquoted & starts a background job, and in cmd.exe it ends the command. Either way the URL reaches searchts cut before the first &, so the read asks for the wrong page. Put the whole URL in quotes:

searchts read "https://www.reddit.com/r/LocalLLaMA/comments/abc/title/?solution=xyz&js_challenge=1"searchts read 'https://www.reddit.com/r/LocalLLaMA/hot/?sort=new&t=day'

PowerShell accepts single or double quotes; cmd.exe uses double quotes. If a read sees a dangling ?, & or value-less query key, it prints a one-line hint to quote the URL. It does not change the read.

Update checks, and the agent note

At most once every 24 hours, searchts asks GitHub for the latest release of capad-xyz/searchts (GET https://api.github.com/repos/capad-xyz/searchts/releases/latest). The one request carries a searchts/<version> User-Agent and nothing about you or your machine. The answer is cached in ~/.searchts/update-check.json for 24 hours; a failed check is silent.

When that release is newer:

• searchts read --json, searchts grab --json and searchts doctor --json add a top-level update_available object, {"current": "...", "latest": "...", "command": "searchts update"}. It is absent when there is nothing newer, so existing parsers see no new key. searchts search --json keeps stdout a bare array and prints {"update_available": {...}} as one JSON line on stderr.
• Successful MCP tool results (not Error: ... strings) carry the same object, plus at most once per 24 hours one line telling the agent to tell you. The stamp lives in ~/.searchts/update-notice.json.
• A terminal run still gets the existing stderr nudge.

Nothing is installed, downloaded, or changed automatically. Run searchts update yourself. SEARCHTS_NO_UPDATE_CHECK=1 turns off the check, the note and the stderr nudge.

Quickstart

read is the command. search finds URLs to read. transcribe and get are what a read names when the page's words are spoken or its files were not in the text.

searchts read https://en.wikipedia.org/wiki/Ada_Lovelace   # the page as Markdown, or a plain failuresearchts search "open source vector db"    # native multi-provider web search, keyless by defaultsearchts transcribe https://youtu.be/...   # the audio, when a read found no captionssearchts get https://example.com/logo.png  # one file a read namedsearchts grab https://example.com          # the set of files, when the files are the deliverablesearchts doctor                            # see what is configured and working

read flags: --json, --backend <tier>, --human (hand off a CAPTCHA or login wall to a real browser), --scrub (redact injection), --pages <n> (follow the next page, curl only, max 5), --items <n> (keep following until this many list rows, and scroll the feed when that is the only way it grows), --resume <token> (continue after the rows a previous items read already returned), --wait-on-429 (retry the rung that got http-429; off by default), --ignore-cooldown (read during a host's 429 cooldown), --expand (open the folds: closed <details> and buttons labelled read/show/see more; never a link, a form or a sign-in, and a "continue reading" paywall is named rather than opened), --proxy <url> (route through a proxy; --proxy-trusted lets a remote proxy operator see the Cookie header). Logged-in reads, all opt-in and for the one site in the command: --cookies-from-browser <browser> with --yes (copy that site's cookies for this session), --cookies <path> (a searchts-owned cookie file), --cdp-port <port> (cookies from your localhost debugger port).

Asking for more is capped by your ceilings, and searchts cannot ask past them: SEARCHTS_MAX_PAGES (default 5), SEARCHTS_MAX_ITEMS (default 300), SEARCHTS_MAX_EXPAND_CLICKS (default 8). A scroll also stops on SEARCHTS_MORE_SECONDS (default 60) and SEARCHTS_MORE_EMPTY_STEPS (default 2); SEARCHTS_MORE_STEP_MS (default 1200) is the gap between steps. Set them in the environment or in a more: block in ~/.searchts/config.yaml (seconds, empty_steps, step_ms; env wins). A resumed read uses the same ceilings. A request above the ceiling is clamped, not silently reduced, and the note lands on the text you read: [items: asked for 900, the ceiling is 300]. A kept login lowers --items to SEARCHTS_MAX_ITEMS_SIGNED_IN (default 50), and that clamp note says signed-in items. An http-429 from a direct request stops the ladder and cools that host (SEARCHTS_429_COOLDOWN, default 300 seconds, 1800 at most, 0 off). The next read is refused until then; --ignore-cooldown reads anyway and --wait-on-429 waits and retries that rung (off by default, one wait when a kept login was sent, never a way past a LinkedIn stop). A scroll that hears 429, including a resumed cursor replay, records that same cooldown and stops; on LinkedIn it also sets the LinkedIn stop. LinkedIn itself stops for 24 hours after a 429, a 999, a too-many-pages page, a checkpoint or a forced logout, and until you clear an account restriction. Page loads are one at a time, at least 20 seconds apart: SEARCHTS_LINKEDIN_LOADS_PER_MINUTE (2), SEARCHTS_LINKEDIN_LOADS_PER_HOUR (20), SEARCHTS_LINKEDIN_LOADS_PER_DAY (100, and 0 turns the daily cap off). SEARCHTS_LINKEDIN_FEED_GAP_MINUTES (default 30) is the gap between LinkedIn feed reads; it is defined here and enforced by a later change. --expand stays a yes/no; how far it goes is your ceiling, not a flag. Lists that only grow by scrolling and folds that need JavaScript both need the browser: searchts install --browser. The scroll opens its own browser, which carries no proxy and no cookies, so a read that carries either does not scroll and says so. Those three ceilings are also every cap on a Reddit read: a post card, a comment and a search result are all rows, so SEARCHTS_MAX_ITEMS is the only number that decides how many come back, and anything left out is printed as a number rather than dropped. login verbs: searchts login keep <url> --cookies-from-browser zen --yes (or vivaldi) copies only that site's cookies into the searchts store; a later plain searchts read <url> uses the saved login. searchts login signin <url> opens a clean sign-in window; add --yes to keep its cookies. searchts login list shows each kept site's live cookie count, its browser or signin source, and when it expires (an upper bound, not a promise). searchts login sweep deletes expired cookies offline now; searchts also sweeps on every command start and prints a receipt for what it removed. It never installs a cron, launchd or Task Scheduler entry. searchts login check <site> [--url <signed-in-page>] reads one signed-in-only page directly with the saved cookies and exits 0 logged in, 1 logged out, 2 unknown; a captcha or block is unknown, and a public page never counts as logged in. login kill <url> removes searchts's copy; your own browser is untouched unless you pass --also-browser. login purge-scratch removes scratch copies. searchts login resume <site> clears that site's 429 cooldown, and for LinkedIn the 24 hour stop or the restriction stop. It sends no request. A checkpoint or forced logout still needs a sign-in by hand, then login keep.

A kept browser login can be re-copied when it is within 24 hours of expiry or a read hits a login wall. That happens only with your recorded yes for that site, or --yes in that run, or a terminal prompt; otherwise searchts says it skipped the copy and why. A login kept with login signin has no browser source to re-copy, so it only gets a hint to run login signin again. Every automatic action prints a receipt row (site, browser or signin, action, count, reason), and searchts read --json carries the same facts in cookie_actions. Cookie values are never printed or logged. search flags: -n <count>, --json, --provider <name>. Content goes to stdout (pipeable); status to stderr. grab flags: --out <dir>, --kinds <images,icons,css,fonts,svg,inline_svg>, --scripts, --read (also save page.md), --max <n>, --tokens <n> (radius, shadow, and spacing values; default 24, ceiling 200), --json. read --media <n> caps inline media kept from the page. install --channels twitter,reddit,opencli,linkedin names optional integrations, install --system-deps (alias --apply) opts in to system changes, and install --env local|server|auto picks the target. uninstall --keep-config leaves the config directory in place, skill install --dir <dir> writes the slash command elsewhere, and check-update, setup, watch, and version are the remaining verbs. searchts help --json is the machine-readable catalog; docs/cli.md has every flag, default and example.

Use it from your AI agent

Add searchts to your agent in one line - as an MCP server, or as a Claude Code slash command:

[Installing searchts as an MCP server with claude mcp add, or as a Claude Code slash command with searchts skill install]

Two ways, both one command:

# 1) MCP: always-on read_url + web_search + fetch_asset + grab_site + get_status + transcribe + login_status / login_signin / login_check / login_kill# Try / no install / Claude cannot see PATH:claude mcp add searchts -- uvx --from "searchts[mcp]" searchts mcp serve# Keep (after pipx install "searchts[mcp]"):#   claude mcp add searchts -- searchts mcp serve# Desktop / Cursor / the other local agents: `searchts mcp install`# writes the stdio server into each client already on the machine.# First read: Wikipedia shows more than example.com, which is one short paragraph.
# 2) Skill: /searchts in Claude Code, plus SKILL.md for Claude and OpenCodesearchts skill install        # ~/.claude/commands/searchts.md and the SKILL.md bundle

See the MCP server reference for all ten tools (read_url, web_search, fetch_asset, grab_site, get_status, transcribe, login_status, login_signin, login_check, login_kill), their inputs and outputs, and when to use each.

Features

• Escalating open-source unlocker: curl_cffi, then Jina Reader, then a stealth browser.
• Multi-provider search with rank fusion: DuckDuckGo (keyless default), plus SearXNG, Exa, Brave, and Tavily when configured; results merged with reciprocal rank fusion and de-duplicated.
• Video transcription: yt-dlp audio plus Whisper for YouTube, TikTok, Instagram, and Reddit videos.
• Asset + design grabber: searchts grab <url> downloads a page's images/icons/css/fonts and extracts a color palette plus the fonts in use; searchts get <url> pulls a single asset. Both go through the same escalating unlock ladder, so they work on fingerprint-gated CDNs, not just open ones.
• Prompt-injection scrubbing: strips invisible/bidi characters, flags injection indicators, optional redaction, so untrusted page content is safer to feed a model.
• Per-domain backend memory: remembers which tier worked per domain and tries it first (SEARCHTS_NO_MEMORY=1 to disable).
• Jina opt-out: the JS-render relay is on by default; SEARCHTS_NO_JINA=1 (or jina: false in ~/.searchts config) skips it so URLs never hit r.jina.ai.
• Surfaces: a CLI, an MCP server (read_url, web_search, fetch_asset, grab_site, get_status, transcribe, login_status, login_signin, login_check, login_kill), and a Python library.

Use as a library

from searchts import unlockerr = unlocker.fetch("https://example.com")print(r.backend, r.status, r.text)
from searchts.search import searchfor hit in search("open source vector db", max_results=5):    print(hit.title, hit.url)

How it works, and its limits

• The free package runs from your own connection at personal volume. It does not ship a proxy pool.
• A script check, including one simple click, is work for the stealth browser. A puzzle that needs a person, and a login the user did not hand over, still stop. --human is for those. A block that is only the address is a separate layer. It is not this fix, and it is not a reason to call DataDome impossible.
• Reddit is one known-host file on the same ring, not a bypass. Listings, threads, profiles and search read as cards; --items follows Reddit's own next-post cursor and --expand opens its "more replies" controls, so the browser tier stays required and there is still no claim that every Reddit URL reads. Which rung answers at all depends on the browser profile: Reddit decides whether to serve its "Prove your humanity" check from the profile's standing, not from the address, so a freshly created profile is challenged page after page while a warm one (the persistent ~/.searchts/browser-profile) is not — on this box the first runs of a new profile were refused on every tier and the same commands read a few minutes later. A scratch HOME throws that profile away, so a throwaway CI or test box measures only the cold answer. When a page is a wall it says which one: private, banned, quarantined, over-18, gone, archived, rather than handing back the nav bar.
• Some platforms (notably Instagram, and YouTube in 2026) may need your browser cookies or fail intermittently; that is platform-side.
• Anti-bot systems evolve; this is an arms race and the techniques may need occasional updates. Respect each site's terms of service and use responsibly.

Configuration

Search works with no keys (DuckDuckGo). Everything else is optional, via searchts configure or a .env (see .env.example):

• Search providers: Exa, Brave, Tavily API keys, or a self-hosted SEARXNG_URL, for more and better results.
• Transcription: a Groq or OpenAI (Whisper) key. ffmpeg and yt-dlp ship with searchts (an ffmpeg on PATH is used first). Login-gated video: searchts transcribe URL --cookies-from-browser chrome (opt-in; read has its own opt-ins, see the read flags above).
• GitHub token for higher rate limits.

Run searchts doctor to check what is configured and working.

Optional integrations

The core is read / search / transcribe. Every searchts read goes through unlocker.fetch — there is no per-platform router. searchts doctor only probes whether optional CLIs (gh, twitter-cli, opencli, mcporter) are on PATH and authenticated. Presence is not a claim that searchts reads those sites through those CLIs.

Roadmap

The open work is PLAN.md. ROADMAP.md is the direction, not the task list. What already shipped is docs/plan-shipped.md.

Credits

searchts builds on and extends Agent-Reach (MIT), reusing its channel, installer, and diagnostics architecture. The escalating open-source unlocker, multi-provider search with rank fusion, prompt-injection scrubbing, per-domain backend memory, the human-in-the-loop CAPTCHA flow, the video transcript channels, the read_url / web_search MCP tools, and the read / search CLI commands are additions in searchts. Thanks to the original authors.

License

MIT. See LICENSE. Original portions Copyright (c) 2025 Agent Eyes; modifications and additions Copyright (c) 2026 capad-xyz.

Built by capad. Questions or feedback: open an issue or email [email protected].

Fun fact: "searchts" doesn't officially abbreviate anything. Off the record, it stands for "search this shit".