oto-dock README

The project's README from github.com/OtoDock/oto-dock. As one markdown file: README.md.

OtoDock

OtoDock — Collaborative Agents

The agentic company OS.

The brains of your company, built on Claude Code & Codex, working on your Anthropic and OpenAI subscriptions.

License: FSL-1.1-Apache-2.0 Version CI Docs Website

Docs · Install · Features · Discussions


Self-hosted · Multi-tenant by design · Fair source
Runs on  Claude Code · Codex · your API keys · local models


Seven faces of the OtoDock dashboard: the company map, an agent's dashboard, an Excel file in the chat, an artifact, the tools page, a meeting and the terminal

Dashboard highlights. The two-minute video tells the whole story.

If OtoDock is useful to you, a star on this repository helps other people find it.

Why OtoDock

OtoDock acts as the brain of your company. You create powerful agents that connect to the tools your company runs on, work in departments, delegate to each other, and keep working on their own when no one is watching. It is multi-tenant by design. Many people work with the same agents, and there are four modes that decide how an agent is shared and where its work lands. You work with your agents on your self-hosted dashboard, or you can even give them a phone line and talk to them. All of it runs on your own Anthropic and OpenAI subscriptions, and on local models.

Build your own AI agents

Every agent gets a name and a job, like a Personal Assistant, a System Admin or a Marketing Manager, and runs on your server. An agent is made of six parts, and you can edit every one of them.

An agent with its six parts around it: persona, memory, workspace, knowledge, skills and tools

Four ways to share one agent

Every agent has a mode that decides how people share it.

Mode What it means
Personal only A private workspace for each person.
Personal + shared A private workspace for each person as the default, and a shared one for the team.
Shared + personal A shared team workspace as the default for everyday work, plus a private one per person.
Shared only Everyone shares one history and one workspace.

Everyone gets the right seat

Admins add each person to the agents they need.

Three platform roles Three roles on every agent
An Admin runs the platform. A Manager has full control of the agent.
A Creator creates agents. An Editor edits the shared files.
A Member uses the agents they are given. A Viewer chats and reads the shared files.

Claude Code or Codex. Your subscription.

Claude Code runs on your Anthropic subscription, and Codex runs on your ChatGPT subscription. Every user connects their own subscription. Local models on your own hardware work as well. You pick the engine per agent, and you can switch it per chat.

Claude Code and Codex plugged into one agent, each with a your-subscription tag

They work while you are away

Agents run on any schedule, when a webhook event fires, or once at a time you choose. They work in your workspace, where their reports, files and updates land, and they notify you when something needs you. Notifications come in four severities, from a quiet chime to a persistent danger alarm. Every run is a full chat you can open, read and continue, so no one has to be watching.

Three triggers feeding an agent that works in the workspace and sends notifications

Give an agent a phone number

Agents answer and place phone calls. Bring your own Twilio account, or connect the Asterisk or FreePBX server you already run.

An agent with a phone number, taking incoming and outgoing calls over Twilio or Asterisk and FreePBX

Runs on your server. Works on your machines.

By default, all your agents run on your server, in an isolated sandbox, with one dashboard controlling all of them. You can also pair a laptop, a workstation or a PC running macOS, Linux or Windows with a one-line install. The machine keeps a single outbound connection to your server, so it needs no open ports, and its files stay in sync. The same agent then runs on that machine with full access to it, and you work with it from the same dashboard, anywhere. If the machine goes offline, your server takes over.

Your server with its agents, linked to a paired laptop, workstation and PC

Your own cloud of agents.

The two-minute video

https://github.com/user-attachments/assets/2d829ee3-2d4c-4001-8b40-73c2eb90c661

This entire video was directed, captured and edited by an OtoDock agent. Watch it in full quality on otodock.io.

The company, running

The 3D company map: the Engineering, Marketing and Independent stages with their agents and the delegation lines between them The CEO agent's dashboard: the company graph and the day's numbers, kept fresh by the agent
Departments. Organize your agents into departments, decide who can delegate to whom, or put them in a meeting together. Live dashboards. Every agent gets live dashboards, so you can manage them effortlessly.
The home agent's control panel: alarm, climate, scenes and light sliders, run by the agent An Excel workbook opened and edited inside the chat, sheets and charts included
Endless tools. Your agents are digital employees. They connect to endless tools, from your calendar to your smart home. Documents. They edit Excel, Word and PowerPoint files right in the chat.
An interactive party budget built by the agent, rendered inside the chat The CEO agent opening a meeting with the developer agent, its work streaming live in the chat
Artifacts. Agents answer with live, interactive UI, rendered right in the chat. Meetings. Specialist agents discuss a topic together and converge on an answer, live in the dashboard.
A Claude Code terminal running inside the dashboard with the agent's tools loaded Your server and the paired machines it runs agents on
Terminal. The Claude Code or Codex terminal opens in the dashboard, with the agent's tools already loaded. Remote machines. The same agent, with all its tools and its synced workspace, runs on any machine you pair with one command, and it can use everything on that machine.

Locked down by default

Agents are powerful, so OtoDock assumes they can't be trusted. Every server-side agent runs inside a kernel sandbox with always-on network isolation, and you grant access one service at a time.

Read the security model →

Everything included

One platform, the whole toolkit.

See all features at otodock.io/features.

Quick start

A Linux server with Docker is all you need (x86-64 or arm64, 4 GB RAM minimum, see the sizing guide). Create a folder for the install, then run the script in it:

mkdir otodock && cd otodock
curl -fsSLO https://raw.githubusercontent.com/OtoDock/oto-dock/main/scripts/install.sh
bash install.sh

The installer checks Docker, writes a .env with a generated database password, handles the Ubuntu 24.04+ host step automatically when the host needs it, downloads the release-pinned docker-compose.yml plus the phone-service overlay, and starts the stack. Everything lands in the folder you run it from. The script performs fresh installs only, and stops rather than touch an existing install.

If your users browse to the server by name or IP, set DASHBOARD_PUBLIC_URL in the generated .env. Behind a reverse proxy, also set TRUSTED_PROXY to your proxy's IP (reverse proxy & HTTPS). Every optional knob is documented in the Configuration reference, and the installation guide also covers building from source, bare-metal development, and running behind a reverse proxy with HTTPS.

The first five minutes

Open http://localhost:8400 and the setup wizard greets you. Create the owner account, and OtoDock installs the Personal Assistant for you, with the tools it needs. Connect your Claude or ChatGPT subscription under Setup, AI Engines, and the banner that reminds you goes away. Open the Personal Assistant from the Agents page and send it your first message. Its reply streams in live, with every tool call and every file it creates (First run). From there you add agents from the community catalog or build your own, and you add the people who will work with them.

How it fits together

 dashboard/   React dashboard — chat, agents, tasks, files, admin
 proxy/       Platform core (FastAPI) — sessions, security, scheduling,
              the agent sandbox, and the WebSocket hub the dashboard talks to
 mcps/        MCP tool servers: OtoDock's custom set (files, memory, tasks,
              meetings, notifications, …) + community mirrors
 audio/       Speech package — STT / TTS / voice activity, provider-agnostic
 phone/       Telephony daemon — live calls over Twilio or FreePBX/Asterisk
 satellite/   Remote-machine agent — pairs your own hardware to the platform
 scripts/     Install, compose, backup/restore, and maintainer tooling

Agents run as Claude Code / Codex processes inside per-session kernel sandboxes, talk to their tools over MCP, and stream every step back to the dashboard. PostgreSQL holds the platform state.

Community

Contributions are welcome: see CONTRIBUTING.md. Security reports: SECURITY.md.

License

OtoDock is fair source: licensed under the Functional Source License, v1.1, with Apache 2.0 future grant (FSL-1.1-Apache-2.0). You can use, run, modify, and redistribute it for anything except competing with OtoDock commercially — and each version automatically becomes plain Apache 2.0 two years after its release.

Self-hosting is free for up to 5 users. Growing teams license by seats. Same software, signed key, no feature gates on your data or your agents.

A note from the author

OtoDock started with Claude Code. I wanted to use it beyond the terminal and connect it to my services. So I built the platform around that idea. It has since become the place where my own agents work: large parts of OtoDock were built, tested, and shipped by agents running on OtoDock.

It's fair source so you can run it the same way for your company, and you can share your builds in the discussions.

— Dimitris Mourtzis

oto-dock (OtoDock/oto-dock)

Searching Database…

191 ·GitHub
Oto-dock
Что это такое?OtoDock — это self-hosted платформа для AI-агентов компании: ваша команда создаёт их на Claude Code, Codex или локальных моделях, а работают они в чатах, по расписанию, по телефону и на ваших собственных машинах.
Это облачный сервис, или мне нужно разворачивать его самому?Вы запускаете его на своём сервере: агенты живут там в изолированных песочницах, и все работают с ними через веб-панель. Можно также привязать машины с Mac, Windows или Linux, чтобы агенты могли работать с ними напрямую.
Как его запустить?На Linux-сервере с Docker (x86-64 или arm64, минимум 4 ГБ оперативной памяти) создайте папку и запустите в ней скрипт установщика: он создаст .env, скачает docker-compose.yml с зафиксированной версией релиза и поднимет весь стек. Затем мастер настройки создаст ваш аккаунт владельца и установит первого Персонального ассистента.
Мне нужен API-ключ Anthropic?Нет. Claude Code работает на вашей подписке Anthropic, Codex — на подписке ChatGPT, и каждый пользователь подключает свою; подходят и локальные модели на вашем железе. Движок выбирается для каждого агента отдельно и меняется в любом чате.
Есть ли подводные камни при установке?Скрипт установки делает только чистую установку — при обнаружении существующей он остановится и ничего не тронет. Если пользователи заходят на сервер по имени или IP, задайте DASHBOARDPUBLICURL в созданном .env, а если сервер стоит за обратным прокси — ещё и TRUSTEDPROXY.
Как там устроена защита от того, чтобы агенты натворили бед?Каждый серверный агент работает в kernel-песочнице с постоянно включённой сетевой изоляцией: приватные диапазоны адресов, ваша локальная сеть и облачные метаданные недоступны. Учётные данные шифруются на диске и передаются на сессию, а SSO, 2FA и лимиты расходов на каждого пользователя встроены по умолчанию.
Что fair-source лицензия значит для моей компании?Это Functional Source License v1.1 (FSL-1.1-Apache-2.0): можно использовать, менять и распространять её для чего угодно, кроме создания конкурента OtoDock, а через два года после выпуска каждая версия переходит под Apache 2.0. Self-hosting бесплатен для команд до 5 пользователей; командам побольше нужна лицензия по числу мест.
Что агенты умеют сразу после установки?В платформу уже встроено многое: агенты создают и редактируют файлы Word, Excel, PowerPoint и PDF прямо в чате, генерируют и правят изображения, монтируют видео с субтитрами и музыкой, расшифровывают аудио, ходят по живому интернету, проводят встречи, передают задачи друг другу и звонят по телефону. Каталог от сообщества добавляет готовых агентов, инструменты и навыки — GitHub, Notion, Home Assistant, Nextcloud, Prometheus, UniFi и Uptime Kuma среди них — в один клик.
Из чего состоит агент?Из шести редактируемых частей: Персона (инструкции простым языком), Память, которая сохраняется между чатами, папка Рабочее пространство, куда попадает повседневная работа, Знания (справочные документы), Навыки, которым он научился, и Инструменты, которые ему разрешено использовать.
Может ли агент работать прямо на моём ноутбуке или рабочей станции?Да. Привяжите машину с macOS, Linux или Windows одной командой: она держит единственное исходящее соединение с вашим сервером, поэтому открытые порты не нужны, её файлы остаются синхронизированными, и тот же агент со всеми инструментами работает там с полным доступом. Если машина уходит в оффлайн, сервер берёт работу на себя.
Зачем автор это создал?Всё началось с Claude Code: Димитрис Мурцис хотел использовать его за пределами терминала и подключить к своим сервисам, поэтому и построил платформу вокруг этой идеи. Значительная часть OtoDock была создана, протестирована и выпущена агентами, работавшими на самом OtoDock.
What are similar projects?ruflo, open-multi-agent, AionUi, hermes-agent, suna, brigade, Observal, Raven
Which topics is it in?fair-source, voip, scheduling, agent-tools, vps, homelab, fastapi, collaboration, chat, memory, sandbox, local-llm
Creator
OtoDock
Size
46 MB
Stars
191
Updated
CommitOct 14Releasev1.8.1Oct 14
Age
3mo
Commits · 90 Days