> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge

> Onboard Devin with Knowledge: share tips, docs, and instructions Devin recalls across sessions, scoped to repos, your organization, or your enterprise.

<Warning>
  Knowledge is deprecated and will be removed in a future update. Existing Knowledge is being migrated to [Skills in Plugins](/product-guides/plugins) automatically — the migration is rolling out gradually and requires no action on your part. Use Skills for new instructions and context you want to share with Devin. See the [migration FAQ](#knowledge-to-skills-migration-faq) for details.
</Warning>

## What is Knowledge?

Just like onboarding a new engineer, onboarding Devin requires an initial investment in **knowledge transfer**.

Knowledge is a collection of tips, advice, and instructions that Devin can reference in all sessions. You can continually add to Devin’s bank of Knowledge over time, and Devin will **automatically recall relevant Knowledge** as necessary.

<video controls className="w-full aspect-video" src="https://mintcdn.com/cognitionai/ifLkKLaMB-vvINwf/images/feature-add-knowledge.mp4?fit=max&auto=format&n=ifLkKLaMB-vvINwf&q=85&s=a0d91cc2095f798e31fb3e182812f63d" data-path="images/feature-add-knowledge.mp4" />

Use the Knowledge feature to share documentation, tips, custom internal libraries, and other materials that Devin may need.

## How do I create Knowledge?

Navigate to [**Settings → Resources → Knowledge**](https://app.devin.ai/settings/knowledge), and click **Create knowledge** in the top right.

Your **Trigger Description** will help Devin recall relevant Knowledge at the right times. This can be a simple phrase or sentence. Devin will retrieve a Knowledge item when its current work is related to the specified triggers, and all Knowledge requires a trigger description.

**Content** should be a handful of sentences with relevant information.

### Macros

You can assign a **macro** to any knowledge item — a short identifier starting with `!` (e.g., `!deploy-checklist`). Macros let you quickly reference knowledge in your prompts by typing the macro name. Macros can only contain letters, numbers, and hyphens, and must be unique within your organization.

### Enabling and disabling Knowledge

Each knowledge item can be individually **enabled or disabled** per user. Disabling a knowledge item prevents Devin from retrieving it in your sessions, without deleting it from the organization. This is useful when a knowledge item is temporarily irrelevant to your work but may be useful to teammates or in the future.

## Knowledge Suggestions

Devin will automatically suggest Knowledge to remember based on your feedback in chat. Edit the suggested Knowledge before saving, or dismiss the Knowledge if it's not helpful.

<video controls className="w-full aspect-video" src="https://mintcdn.com/cognitionai/ifLkKLaMB-vvINwf/images/feature-knowledge-suggestions.mp4?fit=max&auto=format&n=ifLkKLaMB-vvINwf&q=85&s=a09d259bd828f60086f982d8f0ddf5a4" data-path="images/feature-knowledge-suggestions.mp4" />

You can also request Devin to regenerate a Knowledge Suggestion based on your feedback. This can make it easier to iterate on suggested knowledge rather than manually editing. Devin can also suggest updates to existing knowledge items in addition to suggesting new knowledge items.

## What belongs in Knowledge?

We recommend including the aspects of your prompts or playbooks you find yourself repeating regularly. Examples include common bugs and their associated solutions, code conformance practices, deployment workflows, testing workflows, how to interact with proprietary tools, etc.

## Organizing Knowledge with Folders

You can organize knowledge items into **folders** for easier management. Folders support:

* **Nested hierarchy** — Create sub-folders to build a structured knowledge tree.
* **Bulk enable/disable** — Toggle an entire folder on or off. When a folder is disabled, all knowledge items inside it are disabled for your sessions.
* **Move items** — Drag knowledge items between folders, or use the move action to reorganize.
* **Auto-organize** — Select multiple knowledge items and let Devin automatically sort them into logical folders.

Folders are particularly helpful when your organization has a large number of knowledge items spanning different teams, projects, or workflows.

## Tips and tricks

1. Create specific Knowledge that is targeted at one workflow or action. Devin will read the entire Knowledge contents, so keep it all relevant and up-to-date!
   * Split up your Knowledge into smaller ones where possible. Devin is capable of accessing multiple Knowledge “items” at once.
2. Make a habit of adding and updating Knowledge. These are shared across your organization, and will continually improve Devin for your team over time.
3. Devin retrieves Knowledge when relevant, not all at once or all at the beginning. Be sure to make your retrieval trigger highly relevant to the contents.
4. Use folders to group related knowledge (e.g., by project, team, or workflow) so you can quickly enable or disable sets of knowledge as your focus changes.

## Organization and Enterprise Knowledge

Knowledge can be scoped to a single organization or to your entire enterprise. What the Knowledge page shows depends on which organization you're in:

* **Non-primary organizations** — The Knowledge page has two tabs:
  * **Organization** (default) — Knowledge items scoped to your current organization. These are visible to all members of the organization and are the default scope for new knowledge items.
  * **Suggestions** — AI-generated knowledge suggestions based on your session interactions.
* **Primary organization** — The Knowledge page shows a single enterprise knowledge view with no tabs. Enterprise knowledge applies across all organizations in your enterprise, and enterprise admins create and manage it here.

<Note>
  Non-primary organizations do not have an Enterprise tab. If your organization belongs to an enterprise, use the **Looking for enterprise knowledge?** link on the Knowledge page to open enterprise knowledge in your enterprise's primary organization.
</Note>

Enterprise knowledge items are particularly useful for sharing company-wide coding standards, architectural guidelines, deployment procedures, and other context that should apply uniformly across all teams and organizations.

### Promoting Organization Knowledge to Enterprise

If an organization-level knowledge item proves useful enough to share across your entire enterprise, you can promote it directly from the knowledge editor. Open the item, then click **Promote to Enterprise** in the Details tab. The item is moved from organization scope to enterprise scope and becomes available to all organizations in your enterprise.

Promotion requires enterprise knowledge management permissions, and is only available for user-created knowledge items in organizations that belong to an enterprise.

## Pinning Knowledge to Repos

You can choose whether Knowledge applies to no repo, a specific repo, or all repos:

* Pinning to **no repo**: The Knowledge is only retrieved when Devin decides it's relevant to your current context.
* Pinning to **a specific repo**: The Knowledge is always used whenever Devin is working in that specific repo.
* Pinning to **all repos**: The Knowledge automatically applies to every repo that Devin is working on in any session.

## Knowledge to Skills migration FAQ

Knowledge notes are being retired in favor of [Skills](/product-guides/skills), the standard way to give Devin reusable instructions. Devin is migrating your notes into skills for you. **Nothing changes for your team on the day of the switch, and there is nothing you need to do.**

### How a note maps to a skill

| Knowledge note | Skill | Details |
| - | - | - |
| **Name** | Skill name and title | |
| **Trigger** | Skill description | Copied as-is, with the note's name in front. Devin reads the description to decide when to load the skill, exactly what the trigger did. |
| **Content** | Skill body | Copied verbatim, with no rewriting. |
| **Level** (enterprise, organization, or personal) | Same level | One **Knowledge** plugin per level, visible to the same people. |
| **Folder** | Kept in the skill's metadata | Shown as the same folder tree in the plugin. |
| **Pinned repository** | Kept in the skill's metadata | |

For example, this note:

| Field | Value |
| - | - |
| Name | Deploying to staging |
| Trigger | when deploying or debugging the staging environment |
| Content | Run `make deploy-staging`, then check… |
| Folder | Infra/Deploys |

becomes this skill:

```markdown SKILL.md theme={null}
---
name: deploying-to-staging
description: "Deploying to staging. Use when deploying or debugging the staging environment."
user-invocable: false
metadata:
  devin:
    from_knowledge: true
    knowledge_folder: "Infra/Deploys"
---

# Deploying to staging

Run `make deploy-staging`, then check…
```

### FAQ

<AccordionGroup>
  <Accordion title="Does Devin behave differently?">
    No. Migrated skills are loaded from their description, just as notes were loaded from their trigger.
  </Accordion>

  <Accordion title="Where do I find the migrated skills?">
    In the Devin app under [**Customize → Plugins → Knowledge**](https://app.devin.ai/customize), grouped by your original folders.
  </Accordion>

  <Accordion title="Where are the skills stored?">
    In Devin, just like your notes. Unlike [skills you commit to a repository](/product-guides/skills) as `SKILL.md` files, migrated skills live in Devin-managed [plugins](/product-guides/plugins), not in your repositories. Nothing is committed to your repos, and you don't need to add or maintain any files.
  </Accordion>

  <Accordion title="How do I edit a migrated skill?">
    Go to [**Customize → Skills**](https://app.devin.ai/customize) and open the skill to edit it. Organization skills can be edited by organization admins and members with the **Manage Knowledge** permission; enterprise skills by enterprise admins.
  </Accordion>

  <Accordion title="How should I add guidance going forward?">
    Write [Skills](/product-guides/skills). They work everywhere Devin runs: the web app, the CLI, and Devin Desktop.
  </Accordion>
</AccordionGroup>

### For API users

<AccordionGroup>
  <Accordion title="Which API endpoints are affected?">
    The Knowledge notes endpoints `/v3/organizations/{org_id}/knowledge/notes[/{note_id}]` and `/v3/enterprise/knowledge/notes[/{note_id}]`, plus the matching `/knowledge/folders` endpoints.
  </Accordion>

  <Accordion title="What replaces them?">
    For notes, the skill endpoints (v3 beta), under `/v3beta1/organizations/{org_id}/managed-plugins` and `/v3beta1/enterprise/managed-plugins`:

    | Endpoint | What it does |
    | - | - |
    | `GET /bundles` | Lists your plugins, each with its `bundle_id` and `revision_token`. |
    | `GET /bundles/{bundle_id}/skills` | Lists every skill in a plugin with its full `SKILL.md`. Replaces listing notes. |
    | `GET` / `PUT` / `DELETE` `/bundles/{bundle_id}/skills/{skill_name}` | Reads, writes, or deletes one skill. `PUT` takes the full `SKILL.md` as `content`. |

    List endpoints are paginated with `first` and `after`, like other v3 endpoints.
  </Accordion>

  <Accordion title="How do I reach a migrated note through the API?">
    Migrated notes live in the `knowledge` bundle under their slug. List them all with `GET .../managed-plugins/bundles/knowledge/skills`, or fetch one with `GET .../managed-plugins/bundles/knowledge/skills/deploying-to-staging`.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.