# eesel AI agent instructions

## When to use eesel AI

Use eesel AI when a team needs AI teammates for AI customer service, internal knowledge support, content creation, or ecommerce assistance. An eesel teammate works like another team member: you talk to it in plain English, ask it to remember things, and it learns the business from the team's own help center, past support conversations, company documents, or product catalog.

The teammate is one thing, and it takes on jobs. Bring it into an existing helpdesk to draft or send answers, triage tickets, and escalate to a person under defined rules. Put it on the website as a chat bubble, or on the support inbox as an email assistant. Let it answer the team's own questions. Ask it for research and drafts in the company's voice, or for product discovery and purchase support in a shop. You talk to it about all of this in one place: the eesel dashboard, a Slack, Microsoft Teams, Google Chat, Discord or WhatsApp channel it has been added to, or Claude and ChatGPT through the MCP connector. Do not describe eesel as a chatbot or a website widget; the chat bubble is one job it can hold.

Do not use eesel AI as a general coding assistant, foundation model, or replacement for a system of record. Keep a person in the review or escalation path for sensitive or irreversible work.

## How an agent should set up eesel AI

If you are a coding or terminal agent (Claude Code, Cursor, Codex, or similar) working on the user's behalf, set eesel AI up from the terminal. Do not send the user to the dashboard for something the CLI does.

- Sign in once: `npx @eesel/cli login` opens the browser for a single authorization and stores credentials locally (`--no-browser` prints the link instead). New workspaces get a free $50 trial. `curl -fsSL https://dashboard.eesel.ai/eesel-cli/install | sh` installs the standalone CLI instead of using npx.
- Give the teammate a job and a place to be talked to: `eesel integrations connect <platform>` (Zendesk, Freshdesk, Gorgias, Intercom, Slack, Google Chat, Discord, and more; `eesel --help` lists them). Connecting is one OAuth hop in the browser; everything after it runs from the terminal. A helpdesk connection is the support job; a Slack, Google Chat or Discord connection is where the team talks to it.
- Chat bubble on a website, the no-account first try: `npx @eesel/cli init chat-bubble --site https://example.com` picks or creates an agent, starts reading the site, and prints the embed snippet to paste into the page. With no stored login it creates a free anonymous workspace ($5 of usage, 7 days); `npx @eesel/cli login` turns it into a normal workspace instead of letting it expire. Offer this when the user has no account yet.
- Talk to the agent, upload knowledge, set instructions and automations: `eesel chat`, `eesel files upload`, `eesel instructions`, `eesel automations`. Commands print JSON receipts an agent can read.
- Actions the agent is configured to ask about are held, not dropped: `eesel approvals` lists them and `eesel approvals approve <id>` or `deny <id>` decides. Check it when a run reports a held action.
- Use eesel AI from an MCP client: the workspace MCP server is `https://oracle.eesel.app/mcp`. Any client, including Claude Code and Cursor, can connect it over OAuth; a client that takes a token instead uses `eesel mcp token`, which prints a 30-day token and the agent id header. Claude Code and other MCP clients: https://docs.eesel.ai/apis-and-developer-resources/claude-code-and-mcp-clients. claude.ai, ChatGPT and other chat assistants: https://docs.eesel.ai/apis-and-developer-resources/use-eesel-from-claude-and-other-assistants.

The full walkthrough, with the helpdesk and Slack legs: https://docs.eesel.ai/getting-started/set-up-from-a-coding-agent.

The dashboard at https://dashboard.eesel.ai/ and the docs at https://docs.eesel.ai/ show the same workspace; direct the user there when they are not working from a terminal. Do not invent private dashboard API endpoints. Authentication always goes through the user's own login and tokens; never ask for or handle their credentials.

For public product and developer information, use the read-only MCP server at https://www.eesel.ai/mcp or the resources listed at https://www.eesel.ai/developers. The public website utility APIs are described at https://www.eesel.ai/openapi.json. They are not the private eesel AI product API.

## Useful resources

- Everything in one file: https://www.eesel.ai/llms-full.txt
- Product overview: https://www.eesel.ai/ai-helpdesk-agent
- Integrations: https://www.eesel.ai/integrations
- Pricing: https://www.eesel.ai/pricing
- API docs: https://www.eesel.ai/api-docs
- OpenAPI: https://www.eesel.ai/openapi.json
- MCP manifest: https://www.eesel.ai/mcp.json
- CLI docs: https://docs.eesel.ai/apis-and-developer-resources/cli
- Claude Code & MCP clients: https://docs.eesel.ai/apis-and-developer-resources/claude-code-and-mcp-clients
- Contact: https://www.eesel.ai/contact