Glossary
This glossary defines every term Endue uses. Each entry links to the page where the concept is covered properly. A term that appears in the product but not on this page is a documentation bug — please tell us.
Activity
Section titled “Activity”The home screen of the web app: every conversation across every agent, grouped by whether it is waiting on you, running, or done. The place to look when more than one thing is in flight.
Learn more: Activity
A durable identity that does work on your behalf, with its own handle, profile, character, and system prompt. Unlike a chat window you open and discard, an agent persists: it keeps its abilities, its memory, and its history. An agent can only reach what you have bound to it.
Learn more: Core concepts
Agent Builder
Section titled “Agent Builder”The part of the web app where you create and tune agents — identity, system prompt, model, and the skills and connections bound to them.
The name is Agent Builder. “Studio” is not a product name and does not appear in the interface.
Learn more: Agent Builder
Approval
Section titled “Approval”A pause in a run where Endue asks you to confirm before the agent takes an action you cannot take back. Two categories always trigger it: outbound actions that leave your account and reach another person, and destructive actions that delete or overwrite data.
You see the exact action with the exact arguments before deciding. This gate is not configurable. In a routine or any other run nobody is watching, the action is refused rather than left waiting.
Learn more: Approvals · Core concepts
Automatic selection
Section titled “Automatic selection”A setting that has a decision model rate how hard each incoming message is, then answers with the model the agent assigns to that level. In Observe mode it only records the rating and leaves the model unchanged.
Learn more: Choosing a model
Binding
Section titled “Binding”The link between an agent and a capability it is allowed to use. Connections and skills are bound to specific agents — holding a connection in your account does not grant it to every agent you own.
Binding is what keeps an agent’s reach predictable. An agent with three tools behaves more consistently than one with twenty.
Learn more: Connectors overview
“Bring your own key.” Using your own model-provider credentials for an agent’s model calls instead of Endue’s.
Learn more: Bring your own key
Channel
Section titled “Channel”A pairing that lets people reach an agent from outside Endue — a Discord server or a Slack workspace. The opposite direction from a connector, which lets an agent reach a service.
Learn more: Channels
Character
Section titled “Character”The disposition that shapes an agent’s tone and style. Separate from the system prompt, which defines the job rather than the manner.
Connection
Section titled “Connection”An authorized link between your Endue account and an external service — your Gmail account, your Slack workspace, your Notion. A connection is tied to one account at the provider and can be revoked from either side at any time.
Connecting a service is not the same as granting it: a connection must be bound to an agent before that agent can use it.
Learn more: Connectors overview
Connector
Section titled “Connector”The integration that makes a service connectable. Gmail is a connector; your authorized Gmail account is a connection. Endue ships connectors for more than thirty services.
Learn more: Available connectors
Conversation
Section titled “Conversation”A continuous, persistent thread with an agent. It holds the message history the agent reads for context and survives closing the app. Conversations can be grouped into a project when several of them concern the same body of work.
Learn more: Conversations
Credit
Section titled “Credit”The unit the usage dashboard reports weekly model spend in. The dashboard states the ratio it uses.
Learn more: Usage dashboard
Device
Section titled “Device”A computer or browser an agent works on, or an app you use endue on. There are four device products: endue Computer, endue for Chrome, endue for Android, and endue Desktop. Every device has one of two subjects:
- User: a device you signed in to or registered with your account.
- Agent: a device an agent launched on endue cloud to make its own connection.
Devices are listed in the Resources panel, opened from the left sidebar.
Learn more: Devices
Direct connection
Section titled “Direct connection”A link between your agents and a server you run, either a remote MCP server or an HTTP API, set up with its endpoint and headers. Every call asks for approval unless you turn on Always allow for it.
Learn more: Direct connections
A trait that tidies an agent’s memory while it is idle. It merges overlapping memories, corrects stale facts, closes finished commitments, and archives memories that are no longer useful. It also gives each memory a one-line summary and search terms. It runs as a routine at the bedtime you set.
Learn more: Traits
endue Computer
Section titled “endue Computer”The computer an agent keeps files on and runs programs in. The agent starts one on endue cloud the first time it needs it, or you give it your own Linux server or VM instead. Its file area is the agent’s workspace.
Learn more: Devices · Connect your own server or VM
Handle
Section titled “Handle”The short name you use to address an agent. Generated automatically from its name when the agent is created, and stable afterwards.
LLM API
Section titled “LLM API”Calling a model directly from your own code with an Endue API key, in the OpenAI or Anthropic request format, paid from your credits. No agent is involved — for an agent with its prompt and tools, use the Agent API.
Learn more: LLM API
Memory
Section titled “Memory”What an agent retains across conversations — facts about you, your preferences, how you like work done. The agent decides what is worth keeping and recalls it when relevant, so memory is selected rather than dumped into every run.
Memory is inspectable and editable: you can see what an agent stored and delete anything that should not have been kept.
Learn more: Memory
Notification
Section titled “Notification”A message telling you something finished while you were elsewhere: a run replied, a routine completed, failed, or was skipped. Notifications can also arrive as browser notifications when the app is closed. They tell you what happened; you act on it in the conversation they point to.
Learn more: Notifications
Output
Section titled “Output”Something an agent produced that is worth keeping, stored on its own page rather than buried in a conversation. An output is either a file (a document, report, diagram, or dataset) or an app (several files that work together). Outputs are private to you by default and can be shared with a link that grants access to that one output and nothing else.
Learn more: Outputs
Project
Section titled “Project”A grouping of conversations, outputs, and routines that belong to the same body of work. An agent working inside a project sees the project’s context, which is the cheapest way to stop re-explaining background in every conversation.
Learn more: Projects
Reasoning effort
Section titled “Reasoning effort”How much thinking a model does before it answers. Higher effort costs more tokens and takes longer, and pays off on multi-step work where an early wrong turn wastes the rest of the run. Available on models that support it.
Learn more: Choosing a model
Resources
Section titled “Resources”The skills, connectors, and devices an agent can use. The Resources panel in the left sidebar holds the ones on your account. The Resources section of Agent Builder shows what is bound to one agent, together with its built-in tools.
Learn more: Agent Builder
Revision
Section titled “Revision”A saved version of an agent’s system prompt. Prompts are versioned so a change can be reviewed and rolled back — which is what makes prompt iteration safe rather than a gamble.
Learn more: System prompt and revisions
Routine
Section titled “Routine”A task an agent performs on a schedule, running whether or not you have Endue open. What a routine produces waits for you in your workspace. If it needs a decision it asks, and an approval it cannot get is refused rather than left hanging.
Learn more: Routines
One turn of an agent working: read the context, decide, call a tool, read the result, repeat until done or until it needs you. Runs execute on Endue’s servers, so closing the app does not stop the work.
Learn more: Runs · How Endue works
A packaged, repeatable job — a procedure, a checklist, a set of commands — that can be bound to an agent so you do not have to re-explain it. An agent can also request a skill it has not been given, pausing mid-run for you to grant or decline.
Learn more: Skills
Slash command
Section titled “Slash command”A name typed after / in the composer. Built-in commands such as /usage are app features and start no run; the rest come from the skills bound to the agent and tell it which tool to call first.
Learn more: Slash commands
A shared workspace where a team uses the same agents and sees the work they produce.
Steering
Section titled “Steering”Sending a correction to an agent while a run is still in progress. The agent picks it up on its next step, so a correction costs one step rather than the whole run.
Learn more: Steering a run
Surface
Section titled “Surface”One of the places you can use Endue: the web app, the desktop app, mobile, or the command line. All surfaces reach the same agents, conversations, and history — you can start on one and continue on another.
Learn more: Surfaces
System prompt
Section titled “System prompt”The standing instructions an agent reads before every conversation: what it does, what it must never do, and what a good result looks like. Kept under revision history.
Learn more: System prompt and revisions
Third-party skill
Section titled “Third-party skill”A skill imported from a public GitHub or GitLab repository. Only the text of its SKILL.md is imported, and the skill is private to your account.
Learn more: Third-party skills
A single capability an agent can invoke during a run — read a file, search email, create a calendar event, write an output, recall a memory. Tools are what make an agent able to act rather than only advise.
Some tools are built in and always present. Others appear only when a connection or skill is bound to the agent.
Learn more: Built-in tools · Core concepts
Tool call
Section titled “Tool call”One invocation of a tool within a run, visible to you as it happens, along with what it returned.
A switch that turns one behavior of an agent on or off. The traits are Personality, Self-evolving, and Dream. The setting stays where it already lives, and the trait decides whether it is used.
Learn more: Traits
Usage dashboard
Section titled “Usage dashboard”The record of what your agents have spent — tokens over time, broken down by model and by agent — together with how much of your plan allowance is left.
Learn more: Usage dashboard
Workspace
Section titled “Workspace”An agent’s own file area on its endue Computer: the folder it reads, writes, and runs programs in. The word means the folder, not the machine.
Learn more: Workspace
Retired terms
Section titled “Retired terms”These appear in older material. Use the current name.
| Old term | Now called | Notes |
|---|---|---|
| Studio | Agent Builder | Never a product name; do not reintroduce it |
| Abilities, Ability | Resources | The old name of the same panel and Agent Builder section |
| Computer, workspace (meaning the machine) | endue Computer | “Workspace” now means only the agent’s file area |
| Artifact | Output | An output that is a single file. Apps are outputs too |
| Character build, quest, party | — | The RPG framing is retired from product copy |