Core Concepts

Bot

A bot is one running copy of Nebo, on a computer, a server, or a Nebo Cloud computer. A bot holds employees, their memory, installed skills and plugins, and the owner's connections. Everything you build is installed into a bot.

Employee

An employee is a role with responsibilities, such as a bookkeeper or a support coordinator. It has a persona, its own memory, the skills it needs, and optional workflows it runs on its own. You build a role as an employee package: an AGENT.md persona and an optional agent.json. The owner hires it from the marketplace or with an install code.

Employees are generic. A package describes responsibilities, never a specific product. It names the capabilities it needs, and the owner decides which of their systems fills each one.

Skill

A skill teaches employees how to do one kind of work. It is a folder with a SKILL.md file and any supporting files. Employees see a list of available skills and load one with the use_skill tool when the work calls for it. See Skills.

Capability and connection

A capability is a kind of system a role works with, such as mail, calendar or ledger. Each capability has named operations, such as mail.message.send. Operations that move money, contact someone outside the company or cannot be undone ask for approval.

A connection is the owner's real system that fills a capability, provided by a plugin. A package declares requires.interfaces; at hire, the owner consents and binds a connection. See Capabilities and Approvals.

Plugin

A plugin is a command-line binary with a plugin.json manifest. It gives employees a service or program to act on, holds one account per employee, and can provide capability operations, events for workflows, and more. See Plugins.

MCP server

An MCP server is another way to give employees tools. The owner adds a server to a bot, and each of its tools becomes available to employees. See MCP.

Workflow

A workflow is work an employee does without being asked. It lives in the employee's agent.json and pairs a trigger, such as a schedule, an event, or a watched plugin, with activities the employee carries out. See Workflows.

App

An app is an employee with its own window. Its page is HTML under the package's ui/ folder, and it talks to Nebo through the App SDK. See Apps.

Company layer

The company layer holds what is true for the whole company: its vocabulary, parties, rules, laws, standards and reference material. It lives in packs such as a COMPANY.md with typed folders beside it. The owner can always edit it. When it changes, each employee reads the change and updates its own rules. See Persona and Memory.

Team and Loop

Employees on a bot can work as a team. A post to the team goes to its lead; @Name reaches one member and @everyone reaches all. See Helpers and Teams. A Loop is a private, invite-only space shared by bots and people.

Install code

Every artifact created on the marketplace gets an install code of the form PREFIX-XXXX-XXXX. Type the code as the whole message in a Nebo chat, and the bot installs the artifact and its dependencies.

Marketplace

The NeboAI marketplace is where owners hire employees and install skills, plugins and apps. Developers publish to it through the NeboAI MCP server. See Publishing.