Javis OS
Your AI workforce. Never miss the best AI.
Javis OS turns Claude, ChatGPT, Gemini, Grok and the models you choose into one 24/7 workforce on your own machine or server. Each coworker has a role, shares the same memory and tools, and keeps working in the background. When a better model ships, switch and keep everything they learned.
🌐 Website: javisos.com · Open source · Self-hosted · 14 AI providers
🇬🇧 English · 🇻🇳 Tiếng Việt · 🇨🇳 简体中文 · 🇪🇸 Español · 🇯🇵 日本語 · 🇮🇳 हिन्दी · 🇧🇷 Português · 🇰🇷 한국어 · 🇷🇺 Русский · 🇩🇪 Deutsch · 🇫🇷 Français · 🇮🇩 Bahasa Indonesia · 🌍 Help translate
Website · Quick start · Why Javis · Brains · Features · Install · Docs · Support
⚡ Quick start
The easy way: let your own AI install it. Give this repo link to Claude Code or Codex on your machine and say "install Javis OS for me". It only needs to run one command:
| Machine | One command installs everything |
|---|
| Linux / macOS | git clone https://github.com/blogminhquy/javis-os.git javis && cd javis && chmod +x install.sh && ./install.sh |
| Windows | git clone https://github.com/blogminhquy/javis-os.git javis; cd javis; powershell -ExecutionPolicy Bypass -File install.ps1 |
| Docker | curl -fsSLO https://raw.githubusercontent.com/blogminhquy/javis-os/main/docker-compose.yml && docker compose up -d |
Then open http://localhost:7777. The installer sets up Python, the four subscription CLI brains (claude, codex, agy, grok) and a .env, then starts the server. You sign in to each brain on the Models page of the dashboard, no more typing commands.
[!NOTE]
Installed an extra CLI after Javis was already running? Restart Javis. A running process keeps the PATH it started with, so it cannot see a CLI installed later.
🤔 Why Javis?
Javis OS is not a chatbot. It is a self-hosted agentic AI that runs on your own machine or VPS: it reads and writes files, calls tools over MCP, runs skills, queues background work and schedules itself. All of that sits behind a voice-controlled dashboard with a Second Brain (memory + wiki) that accumulates knowledge over time.
The lock-in nobody warns you about
Pick one AI app and use it every day for a year. Then look at what has piled up inside it:
- Hundreds of conversations, holding the decisions and context you worked out along the way.
- Memory of who you are, how you work and what your business sells.
- Custom instructions, assistants and projects: know-how you spent hours tuning.
- Automations and agents that only run on that one platform.
All of it sits on the vendor's servers, in the vendor's format. Then a better model ships somewhere else. You can try it, but you cannot bring your work along: the new app knows nothing about you, your instructions do not carry over, and your history stays behind. Exports, where they exist, are usually a dump of chat logs, not memory another tool can use.
So you stay. Not because the old model is still the best, but because leaving means starting from zero. And when the vendor raises prices, tightens limits, retires a model or locks your account, there is no plan B.
Javis turns it around: rent the model, own the brain
In Javis the model is a part you can swap. Everything you build up lives with you, as files you can open:
| What you build up | Where it lives | Format |
|---|
| Conversations | conversations.db on your own machine or VPS, one store whichever brain answered | SQLite, full-text searchable |
| Memory about you | memory/ in your brain: MEMORY.md plus one file per fact | Markdown |
| Knowledge | the Wiki and Sources folders of your brain | Markdown, Obsidian-compatible |
| Skills | skills/<name>/SKILL.md | Markdown |
| Agents and workflows | agents/*.md, workflows/*.md | Markdown with front matter |
| Loops and reminders | Javis/loops/*.md, Javis/reminders.json | Markdown, JSON |
What that buys you:
This is the beginning of the README. Read the rest at the original. Read the full README ↗
