The agent assembled a comprehensive answer about Linear's purpose, pricing, and positioning, but had to work around a fundamentally inaccessible marketing website. Direct fetches of linear.app's homepage, pricing, features, and docs pages returned JavaScript-heavy HTML that did not render into readable text, forcing the agent to rely entirely on web search results and prior knowledge (83% of fetches) to answer the task. The agent successfully delivered a detailed, accurate response by citing third-party review and comparison articles, but could not extract information directly from Linear's own published pages.

• ›Steps [1], [2], [4], [5], [8], [9] (all direct site fetches) returned truncated, unreadable HTML with no meaningful text content extracted. The agent explicitly noted 'Linear's main website is JavaScript-heavy and didn't render fully for me' in its response.
• ›All substantive information in the final answer came from web search results [7, 10, 11], which returned snippets and links to third-party sources (Everhour, Lifestack, Vendr, Efficient App, Atlassian comparisons, TechInsider). The agent cited these external sources in its References section, not linear.app itself.
• ›The agent had to bridge a large gap: prior knowledge supplied 83% of the fetches, yet the direct site pages yielded nothing readable. This forced a heavy reliance on secondary sources and reconstructed comparisons (e.g., the Jira comparison table was synthesized, not pulled from a Linear page).
• ›Linear's 'Cycles' terminology and specific AI feature details could not be confirmed from the marketing site; the agent acknowledged these as 'confusing or missing info' because it could not access the source material to verify.
• ›The pricing page (step [2]) was fetched but not readable, so pricing details came from third-party pricing aggregators (Lifestack, Vendr, Carly) cited in the final response, not from linear.app/pricing.
• ›The site's navigation structure (features, about, help, docs, pricing URLs) was guessable and reachable, but the content behind those URLs was not machine-readable, making the site appear navigable at the URL level but opaque at the content level.