> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/settings/ai-settings/overview-of-ai-features.md).

# Overview of AI Features

## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) Overview

DevOps includes built-in AI features that streamline two common development tasks: generating code documentation and creating Salesforce test classes. These features reduce manual effort, improve code readability, and accelerate test coverage across your projects. This overview briefly explains each AI feature and the benefits of connecting your own AI model to DevOps.

{% hint style="info" %}

#### Default AI Limitations

By default, Flosum provides a free shared DeepSeek AI model for DevOps through DeepSeek’s API. Because it is shared across tenants, performance and availability depend on system load and token capacity. During heavy usage, you may see higher latency or temporary errors. To avoid this, you can add your own custom AI model. See the following article.

* [Adding a Custom AI Model](/devops/settings/ai-settings/adding-a-custom-ai-model.md)
  {% endhint %}

### Custom AI Model

If you plan to rely on DevOps AI features, we recommend you connect your own cloud-hosted or self-hosted AI model to avoid issues caused by Flosum’s shared AI resources. Using your own model can improve performance, reduce latency, and help prevent temporary errors during heavy usage. A self-hosted model can also provide stronger information security than cloud AI providers. Depending on the provider and model you choose, you may see improvements in speed and reliability. DevOps supports connecting to models that use an OpenAI-compatible API endpoint, including DeepSeek and OpenAI models. To learn how to add a custom AI model, see the following article.

* [Adding a Custom AI Model](/devops/settings/ai-settings/adding-a-custom-ai-model.md)

### AI Test Class Creator

The AI Test Class Creator automatically generates Salesforce test classes for selected code components in DevOps. It helps accelerate test coverage by generating a baseline test class that you can review and commit to the branch. To learn how to use the AI Test Class Creator, see the following article.

### AI Code Documenter

The AI Code Documenter automatically adds comments to code components in DevOps. It helps teams document code by generating readable, structured comments that you can review and commit back to the branch. To learn how to use the AI Code Documenter, see the following article.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flosum.com/devops/settings/ai-settings/overview-of-ai-features.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
