What is an agent?
An AI coworker with its own instructions, tools, memory, and persistent workspace.
personal agent shared agents assistant team agent avatarOn this page
An agent has a place to workWhat an agent carries between tasksFrom a request to a resultYour agentsShared agentsDelegated workRecognize your agentsConfigure and use the agentAn agent has a place to work
An Opser agent is an AI coworker that can take actions to complete a task. It combines a language model with instructions, tools, memory, and a persistent filesystem. It can investigate information, write and run code, work with business records, create documents, and build apps when those capabilities are enabled.
The chat header shows the agent’s avatar — a friendly sky-blue character — and its name. The agent inspects available data and saves a customer portal plan as portal-plan.md in its persistent workspace.
The model handles reasoning and language. The surrounding Opser runtime supplies the workspace and the actions it can take. Switching models does not turn a different conversation into the same thing as a different agent.
What an agent carries between tasks
| Foundation | How it is used |
|---|---|
| Identity and instructions | Its name, behavior, role knowledge, and standing guidance |
| Business and personal context | Information about your organization and the people it serves |
| Memory | Facts the agent can save and retrieve for future work |
| Persistent files | Source files, scripts, notes, and results kept in that agent's workspace |
| Tools | Actions for reading, calculating, updating, building, and communicating |
| Skills | Instructions for carrying out a kind of work with those tools |
| Connections and access | The external accounts, apps, and records it is authorized to use |
A conversation is one thread of work with the agent. Starting another conversation does not erase its saved files or configured context. It also does not automatically load every old conversation into the new one. Point the agent to the relevant file or source when continuing earlier work.
From a request to a result
An agent can break a task into steps, inspect inputs, choose tools, ask for a missing detail, run a script, and review the output. Some actions require approval. The conversation shows the activity and the result so you can inspect what happened.
For example, an agent can read several source files, calculate a comparison, save a reusable script, and produce a report. If the result belongs in an installed app, it can use that app's supported tools to create or update the record. Read Built-in tools and Code & scripts.
Your agents
You start with a default personal agent and can create additional agents for different kinds of work, such as a product manager, researcher, or blog writer. Each agent has its own workspace, configuration, and connections. Every plan lets you create as many agents as you need.
An agent does not gain access to another person's private files or an unconnected service just because you mention them. Ask it to identify the missing source or permission when it cannot complete a task.
Shared agents
You can keep a specialist agent private or share it with teammates. A shared agent has a defined responsibility, its own configuration and workspace, and a member group. It can serve a team around a process such as coordinating requests or preparing operational reports.
Membership controls who can use it. Its permission grants control its capabilities, and interactive actions also check the initiating person's access where required. Sharing an agent is not a shortcut around record permissions. Review what you put in shared context and files for the intended team audience.
Open Settings → Agents to manage the agents available to you. Creating agents requires permission. Sharing is included on every plan, Free included.
Delegated work
For a longer task, the main agent can delegate a bounded part of the work to a subagent and bring its report back into the conversation. A subagent receives a task brief and selected tools; it is not another permanent shared agent you need to configure.
Delegation does not expand authority. Subagents cannot ask you questions or complete approval-gated actions themselves. The main conversation handles those decisions and brings the results together.
Recognize your agents
Every agent has a saved identity: a name and an avatar built from a shape and a color, with an expressive face. Your default agent starts as “Agent” with a randomly assigned avatar; when creating another agent, you can give it a role-specific identity. The General settings let you rename it and pick another look. A shared agent shows the same identity to everyone.
Three agents, each with its own avatar: the personal Opser agent as a sky-blue rounded character, a shared Support agent with four members as an apricot flower shape, and a shared Reports agent with two members as a mint star shape.
The workspace sidebar lists the agents available to you above Apps, each with its avatar, name, and unread activity. Choose one to open its chat; an empty chat greets you with that agent's avatar, and chat headers show the avatar beside the name. Avatar motion follows your reduced-motion preference.
Configure and use the agent
The selected agent's sidebar holds its work and configuration: Chat, Automations for recurring work, the General, Skills, Approvals, and Integrations configuration areas, and Files for its workspace. The controls available depend on your access.
Continue with conversations and projects, context and memory, or persistent files.