@ Docs

Reference documentation pages directly in your conversations

Type @ and select Docs to attach documentation pages as context. The AI reads the full page content so it can answer questions using up-to-date official docs.

How it works

1. Type @ in the chat input
2. Click Docs to open the documentation browser
3. Search or browse by category, then select a doc
4. The doc appears as a chip in your prompt. When you send the message, its content is fetched and included as context.

This is useful when you want the AI to reference specific API docs, guides, or framework documentation rather than relying on its training data.

Curated Android docs

Firebender ships with 38 curated Android documentation pages covering:

• Jetpack Compose: UI, layouts, state, navigation, animation, modifiers, theming
• Architecture: ViewModel, Room, Hilt, WorkManager, DataStore, Navigation
• Core: Activity lifecycle, Fragments, Coroutines, Flows
• Android SDK: Permissions, Services, Broadcast Receivers, Content Providers, Intents, Notifications, and more
• Testing: Testing overview, Compose testing
• Build: Android Gradle Plugin

These are always available in the @ Docs menu with no setup required.

Add your own docs

Click Add new doc at the bottom of the Docs browser to save a documentation URL by name. Enter a friendly name (e.g. “Our API”) and the URL. The doc is saved as a markdown file and will appear in the @ Docs menu permanently.

Personal docs

Personal docs are stored in ~/.firebender/docs/ as individual .md files with YAML frontmatter. They persist across all projects and IDE restarts.

# ~/.firebender/docs/our-api.md
---
name: Our API
url: https://docs.mycompany.com/api
category: Internal
description: Internal REST API reference
---

Project docs

Project docs live in your repository at .firebender/docs/ and use the same frontmatter format. Commit them to version control so your entire team gets the same documentation references.

# .firebender/docs/design-system.md
---
name: Design System
url: https://design.mycompany.com
category: Design
description: Component library and design tokens
---

The only required frontmatter fields are name and url. The category and description fields are optional but help with search and organization.

Frontmatter reference

Each doc file supports these frontmatter fields:

Field	Required	Description
name	Yes	Display name shown in the @ Docs menu
url	Yes	URL of the documentation page to fetch
category	No	Grouping category (e.g. “API”, “Design”)
description	No	Short description for search and tooltips

Priority and deduplication

When the same URL appears in multiple sources, later sources take priority:

1. Curated docs (built-in, lowest priority)
2. Project docs (.firebender/docs/)
3. Personal docs (~/.firebender/docs/, highest priority)

This means you can override a curated doc’s name or category by creating a project or personal doc with the same URL.