bun.sh
success
Claude Code
intent
What does bun.sh do and who is it for? Explain it back to me.
12steps
76.6sduration
$0.1793cost
137,021tokens
20 steps8 reasoning steps5 searches
home
docs
docs
search
docs
search
docs
search
docs
search
docs
search
100%
on-site discovery
86%
reliability
71%
link following
path origin
- previous resource71%
- prior knowledge29%
insight
The agent assembled a comprehensive explanation of Bun by combining the homepage fetch, a key blog post about Anthropic's acquisition, and extensive web search results on comparisons and use cases. However, the site itself did not provide a dedicated pricing page (404 error in step [3]), forcing the agent to rely on prior knowledge and external sources to confirm Bun's free, MIT-licensed model. The agent successfully answered all four questions (what it does, who it's for, pricing, differentiation) but had to work around incomplete onsite documentation to do so.
- ›Step [1] (homepage) established that Bun is 'a fast all-in-one JavaScript runtime' with bundler, transpiler, task runner, and npm client built-in, but did not contain detailed feature breakdowns, pricing, or comparative analysis.
- ›Step [10] and [13] (Anthropic acquisition blog post) revealed critical context: Bun was recently acquired by Anthropic (Dec 2025) but remains free and MIT-licensed under the same team. This was the only onsite source that directly addressed the business model question.
- ›The agent could not find pricing information on bun.sh itself (step [3] returned 404); the final answer about 'completely free and open-source' was inferred from the acquisition post's statement that licensing didn't change, plus prior knowledge and external blog sources.
- ›Comparative details (4x faster startup, 30x faster package installation, 90%+ Node.js compatibility, vs. Deno) came entirely from external sources (web search results in steps [8], [11], [18]), not from the official site.
- ›The site lacks prominent documentation on: exact Node.js compatibility lists, migration paths for existing projects, enterprise support offerings post-acquisition, and real-world application performance data. The agent had to acknowledge these gaps explicitly.
- ›Navigation was straightforward for homepage and docs (steps [1], [2], [6]), but the site does not surface pricing, business model, or comparative positioning as first-class navigable resources—forcing the agent to guess or search externally.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →