Ask about a blog post or article without copying it in
Paste the article URL directly into the chat and ask your question; the persona reads the page and answers based on the actual text.
Paste a link into any free chat tool on the site and the persona actually reads that page before replying. It pulls the clean text from the page and uses it to answer, so you do not have to copy and paste the content yourself. Each anonymous session gets a handful of free reads before it asks you to sign up for more.
When a visitor pastes a URL into one of the free, no-signup chat tools, the persona fetches that page and reads it before responding. There is no separate button or command: just drop a link in the message and the reply reflects what is actually on the page.
The fetch happens at zero marginal cost using a pure-Python extraction engine that strips a page down to its clean article text, discarding navigation, ads, and boilerplate. The only cost is the LLM tokens needed to read that extracted text, so the feature stays available on the free, anonymous tier without a credit card.
Each anonymous session gets 5 free page reads, tracked separately from the 5 free chat messages the session gets overall, in the same 30-day window. A read only counts against that cap when the page is actually fetched and produces usable text; a blocked or empty page costs the visitor nothing. Once the cap is reached, the persona tells the visitor plainly that they have hit the limit for this session and that signing up unlocks unlimited page reads on a more capable model, while still offering to keep the conversation going if the visitor pastes the key text themselves.
The free reader is deliberately the lightweight half of what the product can actually do. It runs one engine only, a pure-text extractor with no browser behind it, so it reads ordinary articles, blog posts, and docs pages well but cannot render JavaScript. A page that needs its script to run before content appears, a single-page app, a dashboard behind client-side rendering, will often come back empty here. Inside the real product the same idea becomes a four-engine pipeline that adds a headless browser and, for paired desktop users, a real browser fallback, so a signed-up employee can read pages this free tool cannot.
Any http or https link in a visitor's message to a free chat tool triggers a read attempt, the first time that link's content is needed for a reply. Only the first link in a message is used; if a page has no extractable article text, blocks automated readers, or the request fails, it does not count against the session's cap because nothing was actually read.
The fetch itself is bounded on every side: it gives up after 6 seconds, stops downloading a page body past 2MB, and truncates the extracted text at 6,000 characters with a visible truncation notice if a page runs long. None of that is configurable per visitor; it applies to every free app the same way, so one oversized or slow page can never stall a chat turn or blow up the prompt sent to the model.
Anonymous sessions get 5 page reads before the tool stops fetching new links, counted in the same 30-day session window as the 5 free chat messages. Past that point the persona is explicit about the limit rather than silently ignoring the link or pretending to browse it, and it invites the visitor to either sign up for unlimited reads on a more capable model or paste the relevant text directly so the conversation can continue.
Signing up does not just remove the cap. It also switches the visitor's employee from the free reader's single always-on extractor to the product's full web-page-reading tool, which adds a headless browser pass for JavaScript-heavy pages and, for a desktop-paired employee, a fallback through the user's own real browser as a last resort.
This is a single read of one page you name, not a search. The persona never goes looking for a URL on its own and never follows links found inside the fetched page; it only reads the exact address you pasted. If you want it to consider a second page, paste that link in a later message, using another read from the same 5-per-session allowance.
A link in your message becomes real content the persona can reason about
The chat backend scans each incoming message for the first http or https link. If one is found, it is fetched and passed through a content extractor before your persona ever writes a word back, so the reply is grounded in the real page, not a guess about what the link probably says.
Safety is built into the fetch: only public web addresses are allowed, so a link that points at an internal network address, a cloud metadata endpoint, or any other private target is refused automatically. If a page cannot be reached or produces no readable text, the persona says so honestly and asks you to paste the key text instead of pretending to have read it.
The read counter is tracked per anonymous session, not per account, so it resets naturally with a new session. Every fetch failure is handled quietly: it never breaks the conversation, it just falls back to asking for the text directly.
Paste the article URL directly into the chat and ask your question; the persona reads the page and answers based on the actual text.
Share a product page or documentation link in a free tool session to get a summary or specific answer grounded in that page's real content.
Drop in a competitor page, job listing, or pricing page link and ask the persona to evaluate it against what you are looking for, without leaving the chat to read it yourself first.
No. Page reading works in the free, anonymous chat tools with no signup, up to 5 reads per session in a rolling 30-day window. Signing up removes that cap and moves you to a more capable model.
If the site blocks automated readers, the page is empty, or the request fails for any reason, the persona tells you it could not read the link and asks you to paste the key text yourself instead of guessing at the content. A failed read like this does not count against your 5-read cap.
No. Only ordinary public web addresses are fetched. Links that resolve to private, internal, or reserved network addresses are refused before any request is made.
Not reliably. The free reader uses one extraction engine with no browser behind it, so it reads ordinary HTML pages well but cannot execute a page's JavaScript. A site that renders its content client-side may come back empty. The signed-up product tool adds a headless browser specifically to handle that case.
Free App Page Read is part of Things they can do out of the box.
Every AI employee ships with built-in abilities that work out of the box. Search the live web for real-time information, scrape and crawl any website for structured data, and generate images directly in conversation. No plugins to install, no APIs to configure.