Skip to content

docs(ai): say what the docs assistant can't do and where to run the Celopedia install #2359

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
GigaHierz merged 3 commits into from
Oct 7, 2026
Merged

docs(ai): say what the docs assistant can't do and where to run the Celopedia install #2359

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
72f443d
docs(ai): say what the docs assistant can't do and where to run the C…
palango Oct 2, 2026
e2a5500
docs(ai): say where to run the Celopedia install and clarify the assi…
palango Oct 2, 2026
b3f9b5c
docs(ai): link the Celo MCP Server at its build/agents path
palango Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions build/agents/celopedia.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,14 +25,14 @@ Go from "what should I build?" to a live app without tab-hopping through docs.

## Install Celopedia

Add it to your coding assistant with one command:
Run this in a terminal, from the root of the project you want to use it in:

```bash
npx skills add celo-org/celopedia-skills
```

<Note>
Restart your coding assistant afterward if it doesn't discover new skills mid-session. Celopedia works with file-based skill environments including Codex, Claude Code, and OpenClaw — see the [GitHub repository](https://github.com/celo-org/celopedia-skills) for tool-specific install notes.
The command has to run in a terminal. The **Ask AI** assistant on these docs can't run it. Celopedia works with file-based skill environments including Codex, Claude Code, and OpenClaw. Claude Code needs an extra step after this command, described in the [repository README](https://github.com/celo-org/celopedia-skills#claude-code). Restart your coding assistant afterward if it doesn't discover new skills mid-session.
</Note>

## Try it
Expand Down
8 changes: 5 additions & 3 deletions build/agents/use-docs-with-ai.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,9 +199,11 @@ Both files are generated from the live site, so they never go stale.

## Ask a question in the docs

Every page has an **Ask AI** button in the bottom-right corner. It answers from the documentation and links the pages it used, so you can check the source rather than take the answer on trust.
Every page has an **Ask AI** button in the bottom-right corner that opens the Celo Docs Assistant. It answers from the documentation and links the pages it used, so you can check the source rather than take the answer on trust.

It searches the same content as the MCP server above, which means answers reflect the docs as currently published — not a model's training data.
The assistant can only search these docs, and it refuses questions unrelated to Celo. It can't see your wallet or account, send transactions, install skills or run commands, and it doesn't read live chain data; for that, use the [Celo MCP Server](/build/agents/mcp/celo-mcp).

The assistant searches the same content as the docs MCP server above, which means answers reflect the docs as currently published — not a model's training data.

If an answer arrives without any links, the assistant offers a **Try a more thorough answer** button, which re-runs the question against a stronger model.

Expand Down Expand Up @@ -242,5 +244,5 @@ You can also skip the menu: **append `.md` to any docs URL** to get the Markdown
</CardGroup>

<Note>
Spotted something wrong on a page? Ask your assistant to use the `submit_feedback` tool — it reports the problem straight to the docs team. You can also [open an issue](https://github.com/celo-org/docs/issues).
Spotted something wrong on a page? Ask your coding assistant (with the docs MCP server connected) to use the `submit_feedback` tool — it reports the problem straight to the docs team. You can also [open an issue](https://github.com/celo-org/docs/issues).
</Note>
Loading