Projects, agents, and channels

It's easy to conflate these, so here's how they relate:

• A project is a workspace — think of it as one client, product, or use case.
• Inside a project, a knowledge base holds the documents that back every agent in that project.
• An agent is one assistant persona: a model, instructions, and a connection to the project's knowledge base. A project can have several agents with different instructions drawing on the same knowledge base — for example, a terse internal agent and a friendlier customer-facing one.
• A channel is a delivery mechanism for one agent — Telegram, WhatsApp, or a website widget. The same agent can be reachable through multiple channels at once.

In short: project → knowledge base → (shared by) agents → channels. Changing an agent's instructions doesn't touch the knowledge base; changing the knowledge base affects every agent that uses it.