> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/agent/agents.md).

# Specialist Agents

Create a specialist Agent with saved instructions, resources, and model settings.

A specialist Agent keeps the same instructions, skills, documents, and model settings for a repeatable task. Use one when the work should follow a set method.

## Use a supplied Agent

Cogram supplies these Agents to each organization:

* **QA/QC Agent** reviews drawings and specifications for coordination issues.
* **Code Compliance Agent** checks submitted evidence against cited code requirements.
* **RFP Assistant** builds a compliance matrix and drafts from approved firm evidence.
* **Project Record Assistant** supports the built-in RFI, submittal and change order filing Automations.

Open [Agents](https://app.cogram.com/dashboard/agent/agents), select an Agent, and start a chat. Provide the project, purpose, issue or submission date, and required output.

Organization admins and owners can configure the first three supplied Agents. The **Project Record Assistant** is built in and cannot be changed.

## Create a personal Agent

1. Open [Agents](https://app.cogram.com/dashboard/agent/agents) and select **New agent**.
2. Describe the task in the configuration chat, or complete the form directly.
3. Set **Agent name**, **Description**, **Model**, **Reasoning effort**, and **Instructions**.
4. Add any required **Skills** or **Documents**.
5. Select **Save changes**.

The form also lists **Connections** that the Agent may use. A connection is not a new permission: each user still needs access to its data.

## Configure an Agent

Open the Agent and select **Configure**. Its settings control later chats and Automation runs, not completed work.

| Setting              | Purpose                                          |
| -------------------- | ------------------------------------------------ |
| **Description**      | Tells people when to use the Agent               |
| **Model**            | Sets the default model for chats and Automations |
| **Reasoning effort** | Balances response depth, time, and cost          |
| **Connections**      | Lists systems the Agent can use                  |
| **Skills**           | Adds reusable methods                            |
| **Documents**        | Adds standing reference material                 |
| **Instructions**     | Defines the task, method, limits, and output     |

Use the **Automations** tab to see Automations that use this Agent. Use **Activity** to see its runs. See [Library](/agent/agent-library.md) for the **Library** tab and attached resources.

## Share or transfer a personal Agent

The owner can select **Share** and choose **People**, **Groups**, or **Everyone in the organization**. The owner can also transfer ownership to another member.

Sharing an Agent does not share its owner's chats or permissions. Each person uses their own project and connector access. Only the owner can configure or delete a personal Agent.

A shared Agent can use organization skills and documents only. Remove personal Library items before sharing it.

## Organization Agents

Organization admins and owners can turn on **Organization Agent** in the builder. They can also use [Organization Settings → Agents](https://app.cogram.com/dashboard/settings/admin/agents#agents).

An Organization Agent is available to every organization member. Only organization admins and owners can configure or delete it. See [Organization Agents and usage](/organization-administration/agents.md).

## Permissions

| Agent type         | Who can see and use it               | Who can configure, share, or delete it |
| ------------------ | ------------------------------------ | -------------------------------------- |
| Private personal   | Owner                                | Owner                                  |
| Shared personal    | Selected people, groups, or everyone | Owner                                  |
| Organization Agent | Organization members                 | Organization admins and owners         |
| Built-in Agent     | Organization members                 | Cogram                                 |

Chats stay private unless their owner shares them. Sharing an Agent never shares its users' chats.

## Write clear instructions

Define the required inputs, method, evidence, output, and limits. State when the Agent must stop and ask for missing information. For technical review, require exact sheet, page, detail, section, and revision references.

## Delete an Agent

Open its configuration and select **Delete agent**. If an Automation uses the Agent, deletion also removes that Automation. Completed run history and recorded cost remain in usage reporting.

## Troubleshooting

**I cannot configure an Agent**

Only its owner can configure a personal Agent. Only organization admins and owners can configure an Organization Agent. A built-in Agent cannot be configured.

**I cannot share my Agent**

It may use a personal skill or document. Remove the item or ask an admin to create an organization version.

**The Agent cannot find project material**

Select the project as context and confirm that you can open the source in Cogram.

## Next steps

* [Agent](/agent/agent.md)
* [Library](/agent/agent-library.md)
* [Automations](/agent/automations.md)


---

# 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.cogram.com/agent/agents.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.