Resources
Resources are read-only content that Claude Code can access. Create reference materials, documentation snippets, or any context that your AI assistant can retrieve when needed.
Overview
Resources provide a way to store static content that the AI can read but not modify. Unlike commands (which are prompts) or skills (which are instructions), resources are reference materials the AI can consult.
Common use cases include:
- API documentation — Store API specs or endpoint references
- Code snippets — Reference implementations or patterns
- Configuration templates — Standard config files or schemas
- Style guides — Writing or coding style documentation
- Project context — Architecture decisions or project-specific info
Creating a Resource
To create a new resource:
- Navigate to your workspace
- Click the Resources tab
- Click New Resource
- Fill in the resource details:
- Type —
Document(markdown content) orURL(an external page). Chosen at creation and cannot be changed afterward. - Name — The resource name in kebab-case (e.g.,
api-reference) - Description — A brief description of what this resource contains
- Content (document) — the markdown body, authored on the next screen; or URL (url) — a public
http(s)page the agent can reach.
- Type —
- Click Create
Resource types
A resource is one of two types, picked when you create it (the type is then locked):
- Document — embedded markdown content (up to 10,000 characters), authored on a dedicated editor page. File icon.
- URL — an external web page delivered as a link rather than embedded text. Globe icon. When Claude Code reads the resource it gets a short heads-up plus the URL, and fetches the page itself with its web-fetch tool if it has one available — nothing is asked of the agent. The URL must be a public
http(s)page the agent can reach (no auth-gated or internal pages).
Use a URL resource to point Claude at living docs (a changelog, an API reference, a status page) without copying their content into the workspace.
Accessing Resources
Resources are available in Claude Code as read-only content. The AI can access resources by name to retrieve their content.
Claude Code can list your available resources and read their contents on demand. This is different from commands (prompts) and skills (instructions).
Enabling & Disabling Resources
Resources can be enabled or disabled:
- Open the resource card menu (three dots)
- Click Enable or Disable
- Disabled resources appear dimmed and won't be accessible in Claude Code
Favorites
Mark frequently used resources as favorites for quick access:
- Go to the Resources page
- Find the resource you want to favorite
- Click the star icon on the resource card
Favorited resources appear at the top of your resources list, making them easy to find. Click the star icon again to remove a resource from your favorites.
Favorites are personal to your account. Other workspace members won't see your favorites, and you won't see theirs.
Exporting Resources
Resources can be exported as JSON files for backup or sharing:
- Open the resource card menu (three dots)
- Click Export as JSON
- The resource will be downloaded as a JSON file
The exported JSON format:
{
"name": "api-reference",
"description": "REST API endpoint documentation",
"content": "## Users API\n\nGET /users - List all users\nPOST /users - Create a user\n..."
}
Importing Resources
Import resources from JSON files:
- Click the Import button next to "New Resource"
- Drag and drop a JSON file or click to browse
- The system validates the JSON structure
- Preview shows resource name and description
- Click Import Resource to create it
Note: If a resource with the same name exists, it will be auto-renamed (e.g., "api-reference" → "api-reference-2").
Content Limits
Resources have the following content limits:
| Field | Limit |
|---|---|
| Name | 30 characters |
| Description | 200 characters |
| Content | 10,000 characters |
Pricing
Resources are charged each time they are read in Claude Code.
Free billing accounts are not charged for resources. See Billing Account Tiers for more information.
| Item | Cost |
|---|---|
| Per resource read | 0.2 credits |
See Billing & Credits for more details on credit management and purchasing.
Workspace Limits
The number of resources per workspace depends on your billing account tier. See Workspace Item Limits for details.
Resources vs Commands
Understanding when to use resources versus commands:
| Feature | Resources | Commands |
|---|---|---|
| Purpose | Reference content the AI reads | Prompts that trigger AI actions |
| Type | Reference (read-only) | Prompts (executable) |
| Arguments | No | Yes (up to 3) |
| Use case | Documentation, context | Actions, workflows |