Skip to content
Kuvai

Glossary

AI agent

An AI agent is software that perceives its environment, decides what to do, and takes action toward a goal — often over multiple steps — by using tools and reasoning with a language model. Unlike a chatbot, it can act, not just answer.

An AI agent is software that perceives its environment, decides what to do, and takes action toward a goal — often autonomously and over multiple steps — by using tools, calling APIs, and reasoning with a language model. Unlike a chatbot that only generates text in reply to a prompt, an agent can act on the world: it can search, read, write to systems, and chain steps together to complete a task rather than just answer a question. For the distinctions people search for most, see AI agent vs assistant vs copilot and agentic AI vs AI agents.

Key characteristics

  • Goal-directed — it works toward an objective you set, rather than producing a single one-off response.
  • Perceives and acts — it takes in information (a prompt, a document, an event) and can take actions in external systems, not just emit text.
  • Uses tools — it calls APIs, runs searches, reads data, or operates connected applications to get things done.
  • Reasons over multiple steps — it can plan a sequence of actions and adapt based on what each step returns.
  • Operates with some autonomy — it can run with limited human input, within whatever access and guardrails it is given.
  • Maintains state — many agents keep memory of prior steps or sessions to inform what they do next.

Example

A customer-support AI agent receives an incoming ticket, reads the customer's order history from a connected CRM, checks a returns policy document, decides whether the request qualifies for a refund, and either drafts a reply or escalates to a human — completing several reasoning and tool-use steps from a single trigger, rather than just answering one typed question.

How it relates to Kuvai

"AI agent" describes the underlying software pattern — perceive, decide, act. Kuvai packages that pattern as an AI teammate built around your business: a named colleague that owns a defined job, is grounded in your own documents and Company Context, and uses tools you connect and then explicitly assign to it. Rather than configuring a generic agent from scratch, you give the teammate a name and a job title and Kuvai writes its persona, standing job and standing instructions. Because trust matters when software can act, a Kuvai teammate works on "you decide how far it goes": ask for drafts and you get drafts, work it starts on its own never makes destructive or out-of-lane changes without checking with you first, and every reply shows its steps.

Frequently asked questions

Is an AI agent the same as a chatbot?

No. A chatbot generates text in response to what you type and stops there. An AI agent can take action toward a goal — it uses tools, calls APIs, reads and writes to systems, and chains multiple steps together to complete a task. A chatbot answers; an agent does the work, within the access it is given.

How is an AI agent different from a large language model?

A large language model (LLM) is the reasoning engine that generates and understands text. An AI agent is the system built around an LLM that adds goals, tools, memory, and the ability to act — it uses the model to decide what to do, then carries out those actions. A Kuvai teammate is that kind of system, grounded in your own documents so it works from your business rather than generic knowledge.

What are examples of AI agents?

Common examples include a research agent that searches the web and compiles a brief, a coding agent that writes and tests code, a support agent that triages and drafts replies to tickets, and an email assistant that reads forwarded messages, checks them against your documents, and prepares a response. The last one is what Mia, Kuvai's Personal Assistant, does with forwarded email.

Are AI agents safe to give access to business systems?

They can be, when access is scoped and actions are governed. A well-designed agent connects to tools only through explicit sign-in (such as OAuth), stays within a defined scope of work, drafts sensitive actions for human review rather than firing them automatically, and shows what it did. The risk comes from ungoverned autonomy, so the safeguards matter as much as the capabilities.

AI agent: common questions

Is an AI agent the same as a chatbot?

No. A chatbot generates text in response to what you type and stops there. An AI agent can take action toward a goal — it uses tools, calls APIs, reads and writes to systems, and chains multiple steps together to complete a task. A chatbot answers; an agent does the work and can act in the world, within the permissions it is given. Kuvai reframes this pattern as an AI teammate that goes as far as you ask and shows every step it takes.

How is an AI agent different from a large language model?

A large language model (LLM) is the reasoning engine that generates and understands text. An AI agent is the system built around an LLM that adds goals, tools, memory, and the ability to act — it uses the model to decide what to do, then carries out those actions. The model is the brain; the agent puts it to use. A Kuvai teammate is that system, grounded in your own documents so it works from your business rather than generic knowledge.

What are examples of AI agents?

Common examples include a research agent that searches the web and compiles a brief, a coding agent that writes and tests code, a support agent that triages and drafts replies to tickets, and an inbox agent that reads incoming email, checks it against your documents, and prepares a response. Each one perceives a situation, decides on steps, and acts using connected tools — the inbox example is what a Kuvai teammate does from forwarded mail.

Are AI agents safe to give access to business systems?

They can be, when access is scoped and actions are governed. A well-designed agent connects to tools only via explicit approval (such as OAuth), stays within a defined scope of work, drafts sensitive actions for human review rather than firing them automatically, and logs every action with its reason. The risk comes from ungoverned autonomy — so the safeguards matter as much as the capabilities, which is why a Kuvai teammate only works in the tools you connect and assign, checks with you before destructive or out-of-lane changes in work it starts on its own, and keeps your data scoped to you.

Your team is one teammate away.

Describe the job. Kuvai builds the teammate. You decide how far it goes.