You can't tell what your agent doesn't know until the code breaks

AI coding agents return outdated code and hallucinate apis — confidently. fugg gives them docs matched to the version in your project, read like files (ls, cat, grep), frozen when published.

$curl -fsSL https://fugg.dev/install | sh
beta — invite-only
your agent
running · tool call
  • stripe/docs
    payments api
  • openai/api
    model api
  • anthropic/docs
    model api
  • vercel/nextjs-live
    react framework
  • react/docs
    ui library
  • tailwindcss/docs
    css framework
  • nodejs/api
    js runtime
  • python/docs
    language
  • typescript/docs
    language
  • go/std
    standard library
  • mdn-web-docs
    web platform
  • apple/swiftui
    apple ui framework
  • postgresql-docs
    database
  • sqlite/docs
    database
  • supabase/docs
    backend platform
  • prisma-docs
    orm
  • drizzle-team/docs
    orm
  • pydantic/docs
    validation
  • django/docs
    web framework
  • laravel-docs
    web framework
  • expo/docs
    react native
  • docker-docs
    containers
  • cloudflare/docs
    edge platform
  • langchain/python
    agent framework
  • vue-docs
    ui framework

…and the long tail, where training data runs dry

  • temporal-docs
    durable workflows
  • duckdb-docs
    embedded analytics
  • clickhouse-docs
    olap database
  • keycloak/javadocs
    identity server
  • backstage-docs
    developer portals
  • tauri-docs
    desktop apps
  • nuxt-docs
    vue framework
  • helm-docs
    k8s packages
  • julia-manual
    language
  • bun-docs
    js runtime
…down to the man pages, javadocs, and SDK corners nobody makes a logo for.

Each of these is the full documentation, rebuilt for agents — cleaned of web clutter, kept current, laid out as a plain file tree. Your agent browses it the way it already browses your repo.

same task, same agent — the only difference is what it reads.

fugg off
add embeddings for the doc chunks
I'll add embeddings with the OpenAI API.
Ran python embed.py
APIRemovedInV1: openai.Embedding is no longer supported in openai>=1.0.0
context used: 30k tokens
fugg on
add embeddings for the doc chunks
Checking the docs for your openai version first.
Ran fugg grep -n 'embeddings' /docs/openai/api/latest/
guides/embeddings.md:42: client.embeddings.create(
Ran fugg sed -n '38,52p' /docs/openai/api/latest/guides/embeddings.md
from openai import OpenAI client = OpenAI() response = client.embeddings.create( model="text-embedding-3-small", input="your text here" )
Ran python embed.py
done — runs on the first try
context used: 3k tokens

read docs the way your agent reads files

Your agent already runs ls, cat, and grep on your code all day. fugg is just more files. No mcp server to configure, no tool catalog loaded into context, nothing new to learn — one line in your agent's instructions and it starts reading. It pulls the section it needs, not the whole site.

the docs page, fetched
<html lang="en">
<script src="…/chunks/main.js" async></script>
<nav aria-label="Main">Docs · Learn · Blog · Sign in</nav>
<aside class="sidebar"> … every page, as links … </aside>
<div class="cookie-banner">We use cookies … <button>Accept</button></div>
<main>
<h1>proxy.js</h1>
<p>API reference for the proxy.js file.</p>
… the rest of the page, inside more markup …
</main>
<footer>Privacy · Terms · Cookies</footer>
the same docs, through fugg
/docs/vercel/nextjs-live/latest/docs/
14/
15/
… 3 more/
app/
api-reference/
file-conventions/· 22 entries
layout.md
page.md
route.md
proxy.md
… 18 more

already tried something?

  • context7 & docs mcps

    they search an index and send your agent whatever ranks best — and the index updates under you. fugg doesn't rank anything: your agent reads a fixed docs tree for the version you name, and the same read returns the same bytes.

  • web search

    the agent skims some page and paraphrases it — you can't tell which page, or for which version. every fugg read carries its address: site, version, file, line range. open the same path and you'll read the same words it did.

  • your own rag pipeline

    chunking, embeddings, re-indexing every release — a pipeline you maintain forever. fugg is just files. nothing to re-index, nothing to re-rank.

FUGGbench Leaderboard

Every entry is a curated, versioned snapshot agents can shell into. FUGGbench scores each corpus on how well it can be navigated, parsed, and grounded by an LLM — not just whether it exists.

preview
SiteScoreStructFreshVersionCold NavScored
92969592842h ago
90959590804h ago
88929584866h ago
86889578823h ago
85909586704h ago
82859580785h ago
78808888707h ago
68609050648h ago

about

fugg is an agent tool that gives your agent shell access to a frozen, versioned set of docs for the library versions you actually use. built by General Frontier.

  • agent-first built for agents to read, not humans to browse
  • plain files, plain commands if your agent can read a file, it can use fugg

get it running

$curl -fsSL https://fugg.dev/install | sh

then fugg sites lists everything that's indexed. one line in your agent's instructions, and it reads for itself.

  • 1 — install

    one command puts the fugg cli on your machine. works with any agent that can run shell commands — claude code, cursor, codex, your own.

  • 2 — tell your agent once

    add one line to your agent's instruction file (CLAUDE.md, AGENTS.md): "check docs with fugg before using an external api." that's the whole integration.

  • 3 — it just reads

    from then on the agent runs fugg grep and fugg cat on its own, the same way it reads your project files. nothing else to configure.