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

> ## Agent Instructions
> The docs are served at https://docs.devias.io. Every path in these docs is relative to that root: /llms.txt is https://docs.devias.io/llms.txt.
> Devias is an open-source platform that works as an operating system for a business: a core (records, views, workflows, agents, permissions) with installable modules.
> Pages are typed by folder. concepts/ explains what things are, guides/ gives procedures, reference/ is exhaustive (SDK, CLI, HTTP API), operate/ covers hosting. Use /start/glossary for exact terms.
> Every id in a module (module, object, field, view, action, workflow, step, connection, variable, event, policy) is a uuid. Generate them with `devias id <count>`. Never invent dotted or readable ids.
> Run `devias plan` and read its output before `devias apply`. Apply only what the plan says.
> The OpenAPI document, including the routes of the modules in the reference setup, is at /reference/api/openapi.json.
> Devias is young and changes quickly. If a page and the source repository (github.com/devias-io/devias) disagree, the repository is right.

# Use the assistant

> How to use agents in the studio. Covers opening the assistant, what to ask, how an approval card works, and where agents and skills are managed. Agents need an AI provider key and act with the role of the person who asked.

The **assistant** is the default agent of a workspace. It opens in a panel beside the current page and does work through the same actions the studio uses. It needs an AI provider key, set once: see [Turn on agents](https://docs.devias.io/quickstart.md#turn-on-agents).

## Ask the assistant

`⌘J` opens the assistant. Requests are written in plain words, for example "create a new invoice for Northwind for consultancy hours" or "how many deals are in the pipeline?". The assistant shows each step it takes, such as the records it found. Typing `@` mentions a record.

## Approve what an agent changes

Agents look things up freely and make everyday edits, such as creating or updating a record, without asking. A tool that does something bigger, such as deleting records, importing a file, sending a notification or changing the data model, stops and shows an **approval card**.

1. Read the card. It says what the agent wants to do, with the values it plans to use.
2. Choose **Approve** to let it go ahead, or **Reject** to stop it.

The card stays in the conversation as a record of the decision. Which tools ask first is set per agent: see [Tools and approvals](https://docs.devias.io/guides/agents/tools-and-approvals.md).

## Manage agents and skills

* **Agents** in the sidebar lists the agents of the workspace and the agents that modules brought. Create, edit and configure them as described in [Define an agent](https://docs.devias.io/guides/agents/define-an-agent.md).
* **Skills** in the sidebar lists skills, with when each one applies. Skills from a module show which module. See [Skills](https://docs.devias.io/guides/agents/skills.md).

An agent acts as the person who asked, with that person's role, and its tool list narrows that further.

## Related

* [Agents](https://docs.devias.io/concepts/agents.md): how tools, approvals and permissions fit together.
* [Tasks](https://docs.devias.io/guides/studio/tasks.md): give a task to an agent.


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