nickvasilescu/grokbot-clone

What it is

Grokbot Clone is a self-hostable runtime for always-on AI teammates, run with your own Grok, Orgo and Composio accounts. Each Bot has a name, visual identity, instructions, skills and durable memory, and can work on its own cloud computer: browsing, running shell commands and using a Linux desktop that you can watch or take over. Bots can delegate, start subagents, join group chats, run scheduled routines and handle realtime voice calls.

The server owns the agent loop: it builds context, streams a Grok Responses API output, executes tools, pauses Composio write actions for approval, and continues until the task is complete. Oracle-like infrastructure comes from Orgo VMs (one shared VM per account, up to four active Bot desktops) and Composio provides app catalog, authentication and triggers. Conversations, settings and agent state live in a local SQLite database. It is an independent project, unaffiliated with xAI or Cursor/Anysphere README.

Quick start

1. Install Node.js 22.22 or newer, then clone and install:

git clone https://github.com/nickvasilescu/grokbot-clone.git
cd grokbot-clone
npm ci
cp .env.example .env

2. Fill in .env: XAI_API_KEY, COMPOSIO_API_KEY, ORGO_API_KEY, ORGO_WORKSPACE_ID and SESSION_SECRET. Generate the secret with openssl rand -hex 32. The default text model is grok-4.7; change XAI_MODEL for another compatible model on your account. The example env file includes local URLs, computer size and voice options .env.example.

3. Start the API and frontend in separate terminals:

npm run dev -w server
npm run dev -w web

Open localhost:5173; the frontend proxies API requests to port 8787. Sign in with Google, or use the local email form with DEV_LOGIN=1. Your account starts with a primary Bot; create another, set its role and send it a task. The first computer task provisions an Orgo VM.

For a built version, run npm run build then npm start; the app is served at localhost:8787. Set APP_URL and SERVER_URL to that address or your public HTTPS URL so sign-in redirects land correctly, and disable DEV_LOGIN before exposing the server.

Constraints and status

The project is experimental and has not been security-audited. Bots in one account share an Orgo VM, so isolation between Bots is limited; Composio write approvals do not cover every action a Bot can take via browser or shell. Model calls, app actions and computers use your provider accounts and may incur charges. The included integration suite (node tests/e2e.mjs) calls real providers and needs Google Chrome at /usr/bin/google-chrome; the voice harness contains machine-specific paths and needs adapting. Code is MIT-licensed, while third-party artwork and trademarks keep their owners' rights license notices. Architecture and integration details are in the architecture guide, Orgo guide and Grok/Composio guide.

HotRepo's take

The repository recorded 104 stars and 63 forks in its 2026-11-11 TypeScript new-project snapshot, with 4 stars and 2 forks gained over a roughly 96-minute window. The fork-to-star ratio stands out, suggesting people are copying or modifying the runtime rather than only starring it, which fits a self-hosted clone meant to be taken apart. The sample is a single short window, so it does not establish a trend; the architecture docs and MIT license are the durable signals here.