Quickstart

Getting started

Getting going is two moves: build an employee that does the work, and give your customers a portal to reach it. Neither needs a developer to start.

1 · Build an employee

An employee is defined by a mandate, a model, and a set of abilities. You can set it up in the console, or drive it with your own agent over MCP — the primitives are the same.

• Write its mandate — its standing instructions: who it is and what it's responsible for.
• Pick a model — and, if it generates media, an image / video model.
• Turn on abilities & skills — web search, code execution, MCP integrations, and reusable skill packs. Switch off any tool you don't want it to have.
• Publish — it goes live.

Over MCP that's roughly:

set_mandate → set_model → set_skills → publish_employee

2 · Connect a channel

Put the employee where your customers already are. Connect one channel and it's live there:

• Slack, WeChat / WeCom, Discord, or an embeddable web widget.

3 · Give customers a portal

Your customers sign in to a branded portal — their orders, files, deliverables, and a thread with your team. Two ways to get one:

• From the template — create it in the console, set your brand and domain, and publish. The console handles the build, deploy, analytics, and custom domain.
• Bring your own — build the portal on your own stack with the publishable key and the @holaboss/client SDK. See Bring your own portal.

Where to go next

• How it works — the mental model behind the two sides.
• Bring your own portal — the customer-facing app, end to end.
• SDK reference — the client that powers the portal and chat.