What an AI agent is (and what sets it apart from a chat)

Anyone who has used a language model knows the chat: you write, you read the answer, you write again. The initiative is always yours. An AI agent flips the pattern: it receives a goal, enters a loop (observe, decide, act, verify) and keeps going until the job is done or until it meets something that needs a human decision.

Two things define it: autonomy in choosing actions and an explicit stop condition. Without the first it is a chat; without the second it is a process that never ends.

That is why an enterprise agentic system is not “a chat with more tools”. It needs a perimeter where the agent can act without asking permission at every step, tools to read from and write to company systems, a memory that survives long jobs, independent checks and a way to involve the right person when needed. AIDeskPro brings all of these pieces together.

Chat, RAG or agent?

Chat. One question, one answer. Great for writing, summarising, translating, reasoning about a text you hand it.

RAG (document indexes). The chat searches your documents before answering. Great for finding information in company knowledge, manuals, policies.

Agent. It receives a mandate and delivers a finished result: a proposal in PDF, an evaluation table, an updated website, a completed form. It uses the chat to reason, the indexes to research, databases and external services to act.

In AIDeskPro the three levels live in the same tool: you start with the chat, build the indexes, and when a task requires hours of repeatable work you hand it to an agent.

How an agent works in AIDeskPro Everything

An agent is defined once as a Configuration and used as often as needed through an Execution. Between the two sit a sandbox, a set of tools, a memory and a console.

Isolated sandbox

Every execution runs in an isolated environment with its own filesystem and workspace. Inside it the agent can create files, run programs and reorganise everything without asking for confirmation: a mistake is a file to discard, not an incident in your systems. It is the perimeter that makes real autonomy possible.

Tools and MCP connectors

A configuration’s Resources come in four kinds: document Indexes (transcripts, proposals, contracts, manuals), relational or analytical Databases connected via MCP, external MCP servers (tender registries, professional databases, company APIs) and specialised Sub Agents. Plus web search and image generation, enabled with one click.

Memory, phases and checks

A long job is split into phases, each with a goal, a check and a write to memory. Memory is a folder in the sandbox: plan, progress, notes and log. This way the agent resumes after an interruption, hands over between phases and leaves a trace of every decision.

Reusable configuration

Name, model, role and instructions, integrated functions, reference files, resources, expected outputs. Written once, launched every time with a different starting command. Resources can be fixed in the configuration or requested at execution. Configurations can be exported, imported and cloned.

Console and workspace

While the agent works, the Console shows every step: commands run, files written, searches, the questions it asks you. In the Workspace you browse the sandbox, open the files produced in an editor, fix them, download them or upload new ones. You can pause, resume and stop.

The human in the loop

Some information is written nowhere: the maximum discount, this quarter’s priorities. The agent asks you, concentrating questions at the start and coming back only when a check reveals an ambiguity. The human in the loop is not a brake, it is a source.

A concrete example

A sales agent has three indexes: the transcripts of the calls with the customer, previous proposals, the service catalogue. The mandate: “prepare the proposal for this customer”.

The agent frames the context, asks the salesperson what the documents do not say (maximum discount, start dates), reads every transcript in full segment by segment, matches each requirement to a catalogue service at list price, and drafts the proposal in the company format. A check at every phase: no requirement without a match, no price outside the catalogue. The salesperson downloads it from the workspace, reads it and sends it.

Read how we build an agent, step by step →

AIDeskPro agent console: steps taken, workspace and preview of the file produced

What agents do, in practice

Use cases we have built with AIDeskPro Everything, for ourselves and for our customers. The website you are reading is updated by an AIDeskPro CMS agent.

Sales proposals

From call transcripts, emails and proposal history to a proposal ready to send, in your format and with your catalogue prices. With the brand guide in the indexes, the layout and tone of voice are yours.

CV screening

The agent extracts the required skills from the job posting, reads the candidates’ CVs and produces an evaluation with a match percentage for each. The same pattern applies to supplier offer selection.

Tenders and calls

Connected via MCP to a tender registry, the agent searches for the calls that match your criteria, extracts the requirements from the specifications and prepares the documentary basis of the response from tenders already won.

Certifications and assessments

Filling in questionnaires and forms for certifications (ISO and similar), security checklists, supplier assessments, formalising policies and procedures, drawing on company documentation already indexed.

Content and CMS

An agent that writes a post, lays it out and publishes it. Or one that updates an entire website, as the CMS agent of this site does. With image generation enabled, it produces the visuals too.

Reports from databases

Connected to a company database (CRM, orders, price lists) via MCP JDBC, the agent queries the data, cross-references it with the documents in the indexes and produces reports, comparisons and tables ready for a meeting.

Autonomy inside a perimeter: governance and security

An agent that acts on its own raises different questions from a chat: where it works, what it can touch, who can use it, how much it costs, what happened. AIDeskPro answers each one.

  • Where it works. In an isolated sandbox, in the cloud project dedicated to your company, in Europe (Google Cloud or Scaleway, Milan included). Or on your servers, with the on-premise versions.
  • Where the data goes. Default models use European endpoints with zero data retention and do not train on your content. Models with global endpoints are labelled “NO EU” and are chosen only explicitly.
  • What it can touch. Only the resources you assign: those indexes, that database, that external service. Nothing else.
  • Who can use it. Each configuration is private, read-only or public, and is shared with individual users or groups. Access is via SSO (Azure AD, Google) or managed credentials.
  • Which models. Administrators decide which LLMs are available to which groups, from the model permissions section.
  • How much it costs. Daily cost dashboard, filterable by user label, with spending thresholds and alerts.
  • What happened. The console keeps every step of every execution; the agent’s memory records plan, progress and decisions. It is the traceability you also need to document the use of AI in your company.
AIDeskPro Everything: architecture of the agentic version

Included in every plan

Everything is not a separate module: it is part of every AIDeskPro plan. Only the number of concurrent executions changes.

Business

3 concurrent agents, up to 5 users. EU cloud in a dedicated project.
Most popular

Advanced

5 concurrent agents, up to 30 users. EU cloud in a dedicated project.

Premium

10 concurrent agents, up to 50 users. EU cloud in a dedicated project.

Enterprise

Unlimited agents and users, SLA, custom SSO, dedicated cloud or on-premise.

Where to start

1. Chat and indexes

Start with the platform: the best LLMs, company documents in shared indexes, working groups. It is the foundation agents work on. Tutorial →

2. The first agent

With the standard configuration and a starting command you launch the first job in minutes: a summary, a search, a document. Watch the console, open the result in the workspace.

3. Agents on your systems

Connect databases and external services via MCP, add sub agents for checks, share configurations with departments. For this step Open Gate works alongside you. Contact us →

Frequently asked questions about AI agents

The questions companies evaluating an agentic system ask us most often: what changes compared to a chat, where the data goes, what happens when something goes wrong, how much it costs.

If yours is missing, write to us: sales@opengate.biz .

Want to see an agent at work on your documents?

Bring us a real case: a proposal to write, a selection to make, a tender to analyse. We configure it together and run it in a demo.