Skip to content
agentusehub

Run company departments with persistent self-hosted agents

A self-hosted company OS runs Claude Code and Codex agents per department, with memory, schedules, phone calls via Twilio, and document/video editing.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

A self-hosted company OS runs Claude Code and Codex agents per department, with memory, schedules, phone calls via Twilio, and document/video editing.

Reported experience

  1. What they did

    OtoDock runs the real Claude Code and Codex as agents inside per-session kernel sandboxes, with network isolation on by default. Access is granted per folder or service through MCP tools. A dashboard streams each step and asks for approval on sensitive actions. Agents run on schedules or webhooks, keep editable memory, hold multi-agent meetings, and produce Word, Excel, PowerPoint and PDF files.

  2. How it went

    The README gives no outcome numbers. The author says large parts of OtoDock were built and shipped by agents running on it. Phone calls, which the summary mentions, are listed as shipping next, not yet available.

  3. Worth knowing

    Install is a Docker compose file plus a Postgres password. Each user connects their own Claude or ChatGPT plan, API keys or local models. The license is fair source (FSL), which bars commercial competition.

Example prompts

Try with Claude Code
Set up persistent agents for my [small company or project] with one agent each for [departments, e.g. sales, support, operations], each keeping notes between sessions and running a [daily or weekly] routine. Start by creating the structure and one useful scheduled task per department. Ask me before any agent sends a message, places a call, or edits a shared document.