Chisle
The coding-agent plugin that bills 52% of a bare model across 20 live tasks. Terse persona + tool-output compressor + context diet.
翻訳待ち
Open-source Grok Bot alternative. Choose your own model and sandbox.
翻訳待ち
Loading the full README. The saved excerpt is shown below.
Rakazo is an open-source platform for running persistent AI teammates. It is available on the web,
as an Electron desktop app, and through an Expo mobile app. Bring your own model and computer
provider, or run the complete stack locally.
Rakazo is in beta. Learn more at rakazo.com.Read the full README ↗Rakazo is an open source, self-hosted alternative to Grok Bot.
Persistent AI teammates with their own memory, routines, apps, and computer. Run it on your own machine, with your own model.
Use it on the web, desktop, iPhone, and Android.
It is also an alternative to Meta Muse, OpenAI Dots, Instinct, OpenClaw, Hermes Agent, and Claude Duet.
Learn more at rakazo.com.
A browser, terminal, files, and a full desktop. Watch it work, take control to sign in, and hand it back.
Put bots in a group and @mention them. They split the work, check each other, and report back.
Run a bot on a schedule, from an email, or from a webhook, and see every run.
Bots build live dashboards and documents you can open full screen, share, and ask about.
Gmail, Slack, GitHub, Notion, Linear and thousands more, plus your own MCP servers and OpenAPI tools.
Web, desktop, iPhone, iPad, and Android, all talking to the same server.
You need Docker Engine, the Compose plugin, curl, and OpenSSL. No clone or Node install.
mkdir -p rakazo && cd rakazo &&
curl -fsSLO https://raw.githubusercontent.com/elie222/rakazo/main/infra/compose/install-images.sh &&
bash install-images.sh
The installer downloads the Compose files, creates .env with random secrets, and starts Rakazo.
It preserves an existing .env when rerun.
Open http://127.0.0.1:5173, create an account, and connect a model.
Local Docker computers are on by default. Optional remote providers: e2b, novita, daytona, createos, boat, boxd, instabox, or railway
with the matching API key.
Default image tag is edge (main builds, linux/amd64 + linux/arm64). Details and tags:
self-hosting guide.
On restricted networks, override the installer download base (RAKAZO_DOWNLOAD_BASE), skip
existing Compose files (--local / RAKAZO_DOWNLOAD_SKIP_EXISTING), or mirror the bootstrap
script URL — see
Restricted networks / mirror downloads.
For an agent-assisted install, use SETUP_PROMPT.md.
Bots stay on when the backend runs on a server. Use the same installer on a VPS, then connect from the desktop app, the mobile app, or a browser.
bash install-images.sh --prepare-only
# edit .env: SANDBOX_PROVIDER=boat (or e2b / daytona / createos) with its API key, RAKAZO_HOST=your.domain
bash install-images.sh
Put HTTPS in front of port 5173; docs/self-host-production.md
covers the Caddy setup and host hardening. In the desktop app choose Existing instance and enter
the https:// address.
Or deploy on Railway; see the Railway setup guide.
You need Node.js 24.15.0 or newer in the 24.x line, or Node.js 26+; pnpm 12; and Docker. Node.js 25.x is not supported.
git clone https://github.com/elie222/rakazo.git
cd rakazo
cp .env.example .env
Set POSTGRES_PASSWORD and POSTGRES_APP_PASSWORD to two values from openssl rand -hex 16,
then put them in DATABASE_MIGRATION_URL and DATABASE_URL. The app connects as its own
rakazo_app login, which row-level security applies to; migrations run as the owner
(database roles). Set BETTER_AUTH_SECRET, ENCRYPTION_KEY, and SCREEN_PROXY_SECRET to
independent long random values. Docker sandboxes also need a dedicated
SANDBOX_SUPERVISOR_TOKEN. You can also set OPENROUTER_API_KEY, or connect a supported
model provider during onboarding.
For host-side development with Docker Desktop, set SANDBOX_CONTROL_VIA_LOOPBACK=true
in .env. The supervisor discovers Docker Desktop's user socket automatically;
DOCKER_HOST or DOCKER_SOCKET can override it for another Docker runtime.
Managed app catalogs are optional. Set COMPOSIO_API_KEY for Composio, or the
PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET, and PIPEDREAM_PROJECT_ID trio for Pipedream
Connect. Users can add an HTTPS MCP server or OpenAPI JSON document from Integrations without
enabling either managed catalog. Connector credentials are encrypted on the server and are never
returned by the API.
This is the beginning of the README. Read the rest at the original. Read the full README ↗