​
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.

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

​
How do I create Knowledge?

Navigate to the Knowledge tab in the Settings & Library page, and click “Add Knowledge” in the top right.

Devin

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.

​
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.

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.

​
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.

​
Pinning Knowledge to Repos

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

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