# Eggent documentation > Eggent is an AI employee with their own computer. This is everything it can do and how to use it — in the cloud, in Telegram and on your own server. Every page below is plain Markdown. The same page as HTML lives at the same address without `.md` (for example /docs/chats/). The Russian version of every page has the same slug under /r/docs/. Everything in one file: https://eggent.ai/docs/llms-full.txt ## Getting started - [Eggent documentation](https://eggent.ai/docs/index.md): Eggent is an AI employee with their own computer. This is everything it can do and how to use it — in the cloud, in Telegram and on your own server. - [Core concepts](https://eggent.ai/docs/concepts.md): The parts Eggent is made of — workspace, orchestrator, projects, chats, skills, memory, context, schedules and models — and how they fit together. - [Sign up for Eggent Cloud](https://eggent.ai/docs/cloud-signup.md): How to create your workspace in Eggent Cloud from the website or from the Telegram bot, what the trial includes, and where to find your Eggent afterwards. - [First steps](https://eggent.ai/docs/first-steps.md): What to do in the first half hour — launch a ready-made skill, give it a real task — and a few habits that make Eggent work better. ## Working with the agent - [Chats](https://eggent.ai/docs/chats.md): How to work in a conversation with the agent — start a chat, attach files, stop the work or steer it as it goes, answer the agent's questions and pick the mode that saves tokens. - [Projects and the orchestrator](https://eggent.ai/docs/projects.md): Why work is split into projects, how to create and switch them, what projects and the orchestrator share, and how the agent finds the right project by itself. - [Task board](https://eggent.ai/docs/board.md): Hand work to the agent as cards. Each card is carried out in a conversation of its own, one after another; cards can wait for each other, and the board tells you when one needs you. - [What the agent can do](https://eggent.ai/docs/capabilities.md): The tools an Eggent agent has — a terminal, Python with document libraries, the web, files, helpers, images, Telegram, schedules — and what it cannot do. - [The agent's browser](https://eggent.ai/docs/browser.md): In Eggent Cloud the agent has a real browser on a machine of its own. It opens sites, clicks, fills in forms and scrolls, while you watch in the Browser panel and take control whenever you need to, for instance to sign in to an account yourself. - [Files](https://eggent.ai/docs/files.md): Where workspace files live, how to upload them (whole folders included), open, download and delete them, see a web page as it looks and change its words, save a file as PDF, how every change is kept as a version you can compare and restore, what the limits are, and how the agent shows files in its answers. - [Working in a company](https://eggent.ai/docs/company.md): A company is a group of workspaces, one per person, run by an administrator. Its people write to each other, share files with each other to read, comment on or change, and send versions of files for approval in order - with their agents' help. - [Voice](https://eggent.ai/docs/voice.md): How to dictate a task in the web app and send voice messages in Telegram, and who turns the speech into text — Eggent AI, a provider of your own, or Whisper on the workspace's server. - [Images](https://eggent.ai/docs/images.md): How to ask the agent to draw an image or edit one of yours — from a sample, in the right aspect ratio and quality — and what it costs. ## Setting up the agent - [Models](https://eggent.ai/docs/models.md): Which model answers for the agent, how to change it for the whole workspace or one project, what Eggent AI is, how to connect your own key from any provider and how to switch back. - [Context](https://eggent.ai/docs/context.md): The standing instructions the agent receives with every message — what to put in them, where to edit them and why to keep them short. - [Memory](https://eggent.ai/docs/memory.md): How the agent remembers facts between chats — the notebook it searches, the short notes and skills it learns by itself, how to ask it to remember or forget, and where to see and edit all of it. - [Skills](https://eggent.ai/docs/skills.md): What a skill is, how the agent picks the right one, how to install a ready-made skill, upload one from a file, delete one, launch one by hand, write your own — and what a skill is made of. - [Skill catalog](https://eggent.ai/docs/skill-catalog.md): Every quick-start card in Eggent Cloud — what each one does, what to bring to it, where it works and what you get at the end. - [MCP](https://eggent.ai/docs/mcp.md): How to connect external services to the agent over the Model Context Protocol — by asking the agent or editing .mcp.json by hand, which kinds of servers exist and how to keep their keys. ## Automation and integrations - [Schedules](https://eggent.ai/docs/schedules.md): How to hand the agent recurring work — daily digests, posts, checks — how to change or cancel a task, where the results go and what to know about time and reliability. - [Telegram](https://eggent.ai/docs/telegram.md): How to work with Eggent from Telegram — through the cloud's shared bot or your own bot, how to let colleagues in, what you can send, and how the agent writes to you and posts to channels. - [The agent's email](https://eggent.ai/docs/email.md): Every Eggent Cloud agent has an email address of its own. How it writes to you, what happens to letters sent to it, how a letter to somebody else waits for your yes, and how to set up sending on your own server. - [Google](https://eggent.ai/docs/google.md): Connect your Google account in Eggent Cloud and the agent makes real Google Docs, Sheets and Slides in your Drive. What it can reach, what waits for your yes, and how to put an event into your calendar. - [HTTP API for integrations](https://eggent.ai/docs/external-api.md): How to connect Eggent to your site, CRM, bot or automation — get a token, send a message, pass a file, stream the answer and keep the conversation between calls. ## Eggent Cloud - [Plans and balance](https://eggent.ai/docs/plans.md): How Eggent Cloud billing works — the trial, plans, Eggent AI credits, disk space, what happens when something runs out, and where to see it all. - [Eggent Business](https://eggent.ai/docs/business.md): Eggent Business is a company in Eggent Cloud. Everyone gets an agent in a workspace of their own, while a shared balance with monthly limits, teams, folders, messages, shared files and approvals sit with the administrator. What is included, how it is paid for and how to get it. - [Files on your computer](https://eggent.ai/docs/file-sync.md): How to keep your cloud Eggent's projects folder on your computer as an ordinary folder, synced both ways with Syncthing. - [Sleep and wake](https://eggent.ai/docs/sleep.md): Why a cloud workspace goes to sleep when it is not used, how it wakes up, how long that takes and what happens to schedules and Telegram while it sleeps. - [Sign-in, security and support](https://eggent.ai/docs/account.md): How to sign in to a cloud workspace, change your login, password, language and theme, how data is isolated, what to do with keys and passwords, and how to reach support. ## Mac app - [Eggent for Mac](https://eggent.ai/docs/desktop-app.md): The Eggent app for Mac: what it is, how to download it and open it the first time (it is not signed yet), where its files live, and how to update or remove it. - [The app and your cloud workspace](https://eggent.ai/docs/desktop-cloud.md): Connect the Eggent app to your cloud workspace so the Mac and the cloud are one agent: what is kept in step, what stays on each side, and how a chat can run on either. - [Working on your own subscription](https://eggent.ai/docs/desktop-programs.md): In the Eggent app for Mac a project can run on Claude Code or Codex, already installed on your computer, using your own subscription instead of an Eggent model. Experimental. ## Self-hosting - [Installing on your own server](https://eggent.ai/docs/self-host-install.md): How to run the Eggent open core on your own machine or VPS — the one-command installer, the published Docker image, building from source and the first launch. - [Configuring your server](https://eggent.ai/docs/self-host-config.md): Environment variables of the Eggent open core, a reverse proxy with HTTPS for a VPS, the Telegram webhook, an egress proxy and security rules. - [Upgrades and backups](https://eggent.ai/docs/self-host-maintenance.md): How to upgrade the Eggent open core, back up the data folder, check the server's health, read logs and move Eggent to another machine. - [Eggent Enterprise](https://eggent.ai/docs/enterprise.md): Eggent Enterprise is all of Eggent on your own servers. People's workspaces, the company console, the model gateway, file sync and a Telegram bot inside your infrastructure. What we install, what you need and how it differs from the free install. ## Reference - [Agent tools](https://eggent.ai/docs/agent-tools.md): The full reference of tools an Eggent agent has — what each is for, its main parameters and the requests that lead to it. Useful to people and to the agent itself. - [HTTP API reference](https://eggent.ai/docs/http-api.md): Every Eggent HTTP address — which are open to integrations with a token, which need a web sign-in, and what they accept and return. - [Workspace layout](https://eggent.ai/docs/workspace-layout.md): The folders and files an Eggent workspace is made of — projects, the orchestrator, chats, attachments, settings, schedules — and which of them you may edit by hand. - [Common problems](https://eggent.ai/docs/troubleshooting.md): What to do when the agent does not answer, cannot see a file, uses the wrong model, the Telegram bot is silent, a schedule did not run, an upload fails or the first message is slow. - [For agents](https://eggent.ai/docs/for-agents.md): How a language model or an agent should read these docs — machine-readable pages, llms.txt, stable addresses, and which pages answer which questions about Eggent.