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)

scheduling
Searching Database…

191 ·GitHub
Oto-dock
What is this?OtoDock is a self-hosted platform for a company's AI agents: your team builds them on Claude Code, Codex or local models, and they work in chats, on schedules, over the phone and on your own machines.
Is this a hosted service, or do I run it myself?You run it on your own server: agents live there in isolated sandboxes and everyone works with them through a web dashboard. You can also pair Mac, Windows or Linux machines so agents can use them directly.
How do I get it running?On a Linux server with Docker (x86-64 or arm64, 4 GB RAM minimum), create a folder and run the installer script in it: it writes a .env, pulls a release-pinned docker-compose.yml and starts the stack. A setup wizard then creates your owner account and installs a first Personal Assistant.
Do I need an Anthropic API key?No. Claude Code runs on your Anthropic subscription and Codex on your ChatGPT subscription, with each user connecting their own; local models on your own hardware work too, and you pick the engine per agent, switchable per chat.
Any install pitfalls?The install script does fresh installs only — it stops rather than touch an existing one. If users browse to the server by name or IP, set DASHBOARDPUBLICURL in the generated .env, and TRUSTEDPROXY too when behind a reverse proxy.
How does it keep agents from doing damage?Each server-side agent runs in a kernel sandbox with always-on network isolation: private ranges, your LAN and cloud metadata endpoints are unreachable. Credentials are encrypted at rest and injected per session, and SSO, 2FA and per-user cost budgets come standard.
What does the fair-source license mean for my company?It is the Functional Source License v1.1 (FSL-1.1-Apache-2.0): use, modify and redistribute it for anything except competing with OtoDock, and each version becomes Apache 2.0 two years after release. Self-hosting is free for up to 5 users; larger teams license by seats.
What can the agents do out of the box?A lot ships in the platform: agents create and edit Word, Excel, PowerPoint and PDF files in chat, generate and edit images, cut video with captions and music, transcribe audio, browse the live web, hold meetings, delegate to each other and make phone calls. A community catalog adds ready-made agents, tools and skills — GitHub, Notion, Home Assistant, Nextcloud, Prometheus, UniFi and Uptime Kuma among them — installable in one click.
What is an agent made of?Six editable parts: a Persona (plain-language instructions), Memory that persists across chats, a Workspace folder where everyday work lands, Knowledge (reference documents), Skills it has learned, and the Tools it is allowed to use.
Can an agent work directly on my laptop or workstation?Yes. Pair a macOS, Linux or Windows machine with a one-line install: it keeps a single outbound connection to your server, so no open ports are needed, its files stay in sync, and the same agent with all its tools runs there with full access. If the machine goes offline, the server takes over.
Why did the author build this?It started with Claude Code: Dimitris Mourtzis wanted to use it beyond the terminal and connect it to his services, so he built the platform around that idea. Large parts of OtoDock were built, tested and shipped by agents running on OtoDock itself.
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