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

# Agents

Agents let you create reusable AI helpers with a defined purpose and model. Each one runs with your rules, specific tools, integrations and knowledge.

To create a custom agent, head to the navigation tab **Agents →** click **Create agent.** You can also see this [video walk-through](#video-walk-through) with an example use case.&#x20;

{% stepper %}
{% step %}

### Create an agent

It'll be easier to navigate if you give your agent a proper name and a description.\
*Note: you can create as many agents as you'd like: different tasks, use cases, etc.*&#x20;
{% endstep %}

{% step %}

### Execution

Choose how to trigger your agent. Currently, we support **prompt-based triggers**, which let you chat with the agent or run now.

**What does “Run Now” mean?**\
Use it when the agent can follow instructions immediately.\
*Example:* A Sprint Architect agent that checks JIRA and summarizes sprint health can run now automatically.
{% endstep %}

{% step %}

### Model

Choose the model your agent will use to process prompts. You can change it at any time.\
Model fallback behavior follows your organization’s settings (i.e., if one model fails, another will be used).

:bulb:*Pro tip*:  *if you want to get the best outcomes from agents, use the models our AI engineers recommend. You can access the recommended models from the model picker in the agent creation form.*
{% endstep %}

{% step %}

### Creativity

AI models generate text by predicting the next word based on probabilities. You can control how strictly the model follows your **context** and how much it draws on **outside knowledge**, which affects the novelty and length of the output.

*Grounded*: strictly context, concise and safe; *Guided*: mostly context with selective knowledge; *Balanced*: mix of context and outside knowledge; *Analytical*: context-focused, uncovers patterns; *Creative*: freely explores new ideas.
{% endstep %}

{% step %}

### Instructions

Describe how your assistant should follow prompts, generate responses, and maintain tone. You can enter up to 32,000 characters to set style, rules, and behavior. Note, that longer instructions tend to generate longer response.

:bulb:*Pro tip*:  LLMs understand Markdown — use headings, lists, and formatting to clearly communicate your instructions.
{% endstep %}

{% step %}

### Capabilities

If needed, enable web search to include real-time results from the internet.\
Enrich your agent with knowledge base - add files from an existing [Project](broken://pages/knXmSeV8uuKFbvn1HN1q), like brand guidelines, tone of voice, or reference documents to give your assistant extra context.\
This lets it provide sourced answers using your own materials. Knowledge can be updated or removed anytime.
{% endstep %}

{% step %}

### Integrations

Empower your agent with [integrations](https://docs.nexos.ai/gateway-api/integrations.md) and allow connect to popular platforms like Microsoft 365, SharePoint, Jira, Confluence, Slack and many more. Your agent can fetch information, view files, and read messages. These integrations let your agent provide context-aware answers and insights from your connected systems.\
Note: if you want to use integrations, select a model that supports them.
{% endstep %}
{% endstepper %}

Once saved, you can start chatting with your agent right away. It will appear in the agents list under the Agents menu, and you can access all your agents via the **Chat** model dropdown.

### **Agent Sharing**

Share agents with your team to collaborate more easily and standardize workflows across your organization. Turn a personal agent into a team asset by sharing it, including scheduled agents, with a user, a team, or the whole organization in one action.

#### Share an agent with a user or team

{% stepper %}
{% step %}
Click **Agents** on the left side menu
{% endstep %}

{% step %}
**Find the Agent** you want to share and click on three dots icon and click share.
{% endstep %}

{% step %}
**Share dialog opens up**&#x20;
{% endstep %}

{% step %}
**Choose who gets access –** **Invite people or teams**, enter an email or team name.&#x20;
{% endstep %}

{% step %}
**Set a permission level –** Choose **View** or **Edit**. &#x20;
{% endstep %}

{% step %}
**Share –** Click **Share**. Recipients are notified in their activity feed.
{% endstep %}
{% endstepper %}

<figure><img src="https://4112003433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcOhapgXnoeDvgGQ8Jm4%2Fuploads%2F5njoGkwIikaT7TTx1HR4%2Fimage.png?alt=media&amp;token=779d884b-93c2-4af5-8911-aa7a61aa1ed4" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** if the agent uses a knowledge base, it is shared together with the agent, so recipients get full answers right away. If a knowledge base is not shared automatically, the share dialog shows a prompt.
{% endhint %}

#### Share with the whole organization

{% stepper %}
{% step %}
**Open access settings** In the share dialog, open **Who can access** and select your organization.
{% endstep %}

{% step %}
**Confirm** Click **Share with everyone**.
{% endstep %}

{% step %}
**Notify members (optional)** Select **Notify all members** to alert everyone at once.
{% endstep %}
{% endstepper %}

<figure><img src="https://4112003433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcOhapgXnoeDvgGQ8Jm4%2Fuploads%2FsT8LggNjyo2e8MHn9Oqo%2Fimage.png?alt=media&amp;token=75309f33-2fa8-4715-8cef-792d0f22fb81" alt=""><figcaption></figcaption></figure>

#### Permission levels

| Permission | What the person can do                 |
| ---------- | -------------------------------------- |
| View       | Use the agent                          |
| Edit       | Use, configure, and re-share the agent |

{% hint style="info" %}
Each time an agent is shared onward, the grant records who made it, so access stays traceable.
{% endhint %}

#### See who has access

Open the share dialog to see the **People with access** list.

* Search for any person or team.
* See each entry's permission level.
* See who shared the agent with them: the owner or the person who granted access.

<figure><img src="https://4112003433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcOhapgXnoeDvgGQ8Jm4%2Fuploads%2FDSl3Qu0ckZz0BMLtSpLh%2FScreenshot%202026-11-18%20at%2012.46.36.png?alt=media&amp;token=4668164d-543c-4190-81c8-023b08ff2a12" alt=""><figcaption></figcaption></figure>

#### Scheduled agents

Scheduled agents keep running after you share them. They run on the owner's integrations, with the attached knowledge bases.

#### Admin controls

Team and workspace owners can share and revoke any agent within their scope. This lets admins roll out a proven use case without waiting for the original owner.

{% hint style="info" %}
💡**Pro tip:** share agents that already work well, such as a weekly reporter or a competitor scout, with **View** access to the whole organization. Give **Edit** only to people who need to adjust or re-share them.
{% endhint %}

### Video walk-through

{% embed url="<https://www.youtube.com/watch?v=uogFpbEhRbA>" %}


---

# 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.nexos.ai/workspace/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.
