Profile
Back to NewsBack
GitHub Trending 7 min
Reader Mode
zeenie-ai/OpenCompany: Self-improving AI Employees turning LLM tokens into work and dollars.

zeenie-ai/OpenCompany: Self-improving AI Employees turning LLM tokens into work and dollars.

8 hours ago
OpenCompany banner

OpenCompany

npm version License: MIT Discord Ask DeepWiki

Self-improving AI employees, running on your own computer.

OpenCompany is an open-source operating system for AI employees. You hire an employee for a job, a Builder, a Grower, a Chief of Staff, connect it to your email, calendar, messages, code, and the rest of your tools, and press Start. It works in the background, on your machine, for as long as you want. And it gets better at the job the longer it works.

An AI employee is not one chatbot. It is a small team: a lead who understands the job, and a few specialist agents who each do one part of it well. The lead hands out the work, checks the results, and reports back to you. You build the team by dragging the pieces onto a canvas and connecting them. No code.

Bring your own API keys, or run models locally for free. No subscription. No usage limits.

Read the docs →

Quick Start

Download the app for your computer and install it (these links always point at the latest release):

Nothing else to install. On first launch the app sets itself up (a one-time download, a minute or two) and opens the canvas. Click the key icon in the toolbar to connect your first AI provider. Three example employees are already on the canvas; open one to see how it is put together.

The builds are not code-signed yet, so macOS asks you to allow the app under System Settings > Privacy & Security, and Windows SmartScreen needs "More info > Run anyway".

Terminal install (servers and headless machines)

curl -fsSL https://opencompany.sh/install.sh | bash    # macOS / Linux
iwr -useb https://opencompany.sh/install.ps1 | iex      # Windows PowerShell
company start

The script installs bun, Python and uv when they are missing, then the @zeenie-ai/opencompany package. Open http://localhost:5678. Data lives in ~/.opencompany, shared with the desktop app. See SETUP.md.

Run from source (contributors)

git clone https://github.com/zeenie-ai/OpenCompany.git
cd OpenCompany
bun run build
bun run dev

Needs bun 1.4+ and Python 3.12. See SETUP.md, SCRIPTS.md and CONTRIBUTING.md.

See it in action

Hiring your first employee, end to end ↓

https://github.com/user-attachments/assets/a5a5583f-bb5f-4d27-a387-8522c556e89e

An employee adding the tools it needs, mid-task ↓

https://github.com/user-attachments/assets/035a2293-0837-4969-8b9d-8d680e023b89

A lead running its team ↓

https://github.com/user-attachments/assets/3d25e9a3-f7b9-4760-8b9a-6de1e5a19cad

How It Works

How OpenCompany Works</a>

  1. Hire. Drop an AI Employee onto the canvas. That is the lead.
  2. Build the team. Connect a few specialist agents to it and give each one the tools for its part of the job: email, browser, code, messaging, payments, and so on.
  3. Start. The team runs in the background and wakes up when something happens: a new email, a customer message, a scheduled time.
  4. Review. Watch it work on the canvas, read what it remembers, and change how it does things by editing its skills in plain text.
Default workflows that ship with OpenCompany</a>

The Employees

Each of these is a team you can assemble from the pieces in the box. Rename them, swap the specialists, or invent your own.

Builder — builds and ships things. Writes and runs code, keeps dev servers alive, opens pull requests, deploys, and manages your cloud. The team: a lead, a coder, and a release specialist with GitHub, Vercel, Cloudflare, and Google Cloud.

Grower — grows the company. Publishes to your channels, keeps your community alive, and watches the market. The team: a lead, a publisher for X, WhatsApp channels, Telegram, and Discord, and an analyst with social-media data and web search. Runs on a schedule so the cadence holds without you.

Chief of Staff — runs your day. Reads and answers mail, keeps the calendar, files, sheets, tasks, and contacts in order, and hands you a summary each morning. The team: a lead and workspace specialists for Google Workspace and Microsoft 365. Wakes on every new email.

Front Desk — answers customers. Replies on WhatsApp, WhatsApp Business, Telegram, and Discord, in the customer's language and in voice if you like, and escalates what it cannot resolve. The team: a lead, a support specialist, and a language specialist.

Researcher — finds things out. Browses, searches, scrapes, reads documents and images, and files what it learned into a knowledge base the whole company can ask. The team: a lead, a scout with a browser and search, and a librarian who indexes.

Treasurer — handles payments. Runs payment operations through Stripe and reacts the moment a payment event happens. The team: a lead and a payments specialist.

How They Get Better

  • They remember. An employee keeps facts, preferences, and decisions in a memory you can open and edit.
  • They pick up where they left off. Every new message, task, or scheduled run continues the same conversation instead of starting from zero. When the conversation gets long, the employee writes itself a summary and carries on from it.
  • They add tools when they need them. Mid-task, an employee can look at its own team, add a tool, attach a skill, or bring in another specialist, and the change stays.
  • They check their own work. The lead reviews every result from the team and sends it back if it is not right, before it ever reaches you.
  • You coach them. Skills are short plain-text playbooks. Edit one and the employee follows it on its next turn.
Nothing here is a black box. What an employee learns lives in its memory, its notes, its skills, and the pieces on its canvas, and you can read or change all of it. OpenCompany never retrains a model.

What Is in the Box

  • Connections to Gmail, Google Calendar, Drive, Sheets, Tasks, Contacts, Microsoft 365, any email account, WhatsApp, WhatsApp Business, Telegram, Discord, X, Stripe, GitHub, Vercel, Cloudflare, Google Cloud, your Android phone, a browser, web search, scrapers, and a knowledge base: 148 tools in all.
  • Models from OpenAI, Anthropic, Google, xAI, DeepSeek, Kimi, Mistral, Groq, Cerebras, Sarvam, and OpenRouter, or run local models with Ollama and LM Studio for free.
  • Speech and translation, so employees can listen, talk, and work in other languages.
  • 78 skills that ship ready to use, and a place to drop your own.
  • Built to keep running. Employees survive restarts, pause and resume from the canvas, and catch up on missed schedules. Your API keys are stored encrypted on your machine. Add a login for shared or cloud use; one command deploys to Google Cloud.
  • A canvas you will want to look at, with 12 visual themes.

For Developers

Adding a tool, a model provider, a skill, or an integration is one plugin folder on the backend; the interface renders it automatically.

  • CONTRIBUTING.md — codebase map, architecture diagrams, contribution recipes
  • server/nodes/README.md — 5-minute plugin recipe
  • docs-internal/ — architecture deep dives
  • CLAUDE.md — project memory for AI-assisted contributions
  • Hosted docs: https://docs.opencompany.sh/
  • DeepWiki: https://deepwiki.com/zeenie-ai/OpenCompany

Contributing

Issues and pull requests are welcome. CONTRIBUTING.md has the fork/branch/PR workflow, the repository map, and recipes for adding a node, LLM provider, or skill.

One note on scope: connector and provider lists are kept deliberately narrow. The Apify node runs any actor through its custom option, the TikHub node calls any of its endpoints through call, and agents reach any OpenAI-compatible endpoint through the existing provider path — so a new first-class preset needs a reason beyond "my service could be in the dropdown too."

Community

Discord — the fastest way to get help, request features, and follow design discussions.

License

MIT — © 2026 OpenCompany contributors.

Chat with me