Harness Maxxing

A self-hosted control room for Claude Code. Many persistent Claude conversations organised by project and topic, plus files, tasks, scheduled jobs, a Telegram bridge and a memory backup - installed on your own server with one command and configured from a guided web onboarding.

Free and fair source (source-available). Install: curl --proto '=https' --tlsv1.2 -fsSL https://get.harness-maxxing.com | bash as root - no key, no account. Details in Install below. News: @HarnessMaxxing on X.

Screenshots

Coming soon: dashboard, sessions (desktop and mobile), files, tasks, crons, onboarding.

Features

• Sessions - project -> topic -> any number of persistent sessions. Columns side by side, live streaming, tool calls as cards, diffs, attachments (drag & drop, paste), message queue (steer, edit, side questions that do not interrupt), plan mode, HUD mode, stop, model per session (showing the model that really answered), cost and context gauge, compact and hand-off, archive, move to another topic, full-text search, command palette, keyboard shortcuts. Sessions list in three layouts with favorites, recent sessions and an emoji per project.
• Memory that organises itself - CLAUDE.md + memory.md at workspace, project and topic level, loaded automatically; shipped skills keep it up to date and compact.
• Files - browse, edit with conflict detection, upload, trash; one viewer for every file and folder (pictures, video with a quality choice, audio, PDF, markdown, CSV tables, HTML pages in a sandbox, archives, fonts, code) with ← / → through a conversation's or a folder's files.
• Starter projects - ready-made projects for your kind of work (online store, affiliate site, content creator, apps, second brain, freelance): topics that already know the job and ask you a few questions.
• Notifications feed - one place for what happens: cron runs, Stripe sales, Shopify orders, GitHub runs, any webhook or script (maxxing feed post); dashboard panel, optional Telegram thread posted by the bot, per-source rules, "Ask Harness" about an event.
• Infra (optional) - every site, database, bucket, domain and server: this server, your other servers (SSH, a Hostinger VPS connects in one click), Cloudflare, Hostinger; statuses, certificate and domain expiry, links domain -> server -> site -> app -> repository; standard recipes to put a site online, create a PostgreSQL database or an S3 bucket (maxxing infra).
• Team (optional) - chats with other Harness users (direct messages, groups, files, polls), server to server through a one-time invitation; Claude summarizes the messages you pick; any message can go to a session.
• Tasks - kanban and list on a plain tasks.json that Claude can edit too.
• Crons - shell commands or Harness prompts on a schedule, run history, Telegram reports.
• Telegram - built-in gateway: one thread per open session, the same sessions as the web UI, photos and files, voice notes, sign-in alerts.
• Voice messages - mic button in every session and Telegram voice notes, transcribed on your server (Whisper, private and free) or by Groq / OpenAI.
• Memory backup - daily push to a private GitHub repository, whitelist, secret scanner, one-click restore, used by the installer to move to a new server.
• Dashboard & extensions - built-in widgets, your own widgets as JSON cards and full pages, stored in your workspace so updates never touch them.
• Claude can run the product - skills to set it up, diagnose it, configure Telegram and backups, create jobs, manage tasks and write extensions.
• Claude Code stays current - the server updates the CLI by itself, only while nothing runs.
• Ready for real work - Node.js + Remotion (motion design videos), HTML -> PDF, ImageMagick, Scrapling (web scraping, JavaScript pages included), and skills for videos, PDFs, images, SEO audits and scraping, installed with the product.
• Import from another agent - a prompt for Hermes, Claude Code or OpenClaw, a zip, a preview: projects, topics, memory and skills arrive without overwriting anything. A trash with restore.
• A workspace that explains and maintains itself - default system project (help from the installed docs, guided updates with workspace upgrade notes, server administration, tasks, subscriptions inventory, extensions), an interactive 4-lesson tutorial, and a weekly update check on Telegram.
• Secure by default - one-time setup link, scrypt password, strict cookies, CSRF header, login throttling, HTTPS via Caddy or Tailscale, never bound to a public interface; the server is hardened at install (firewall with only SSH / 80 / 443 open, fail2ban, automatic security updates).
• English and French interface, dark and light themes, mobile friendly.

Requirements

• A VPS with Ubuntu 24.04 (tested: Ubuntu 22.04, 24.04, 26.04 and Debian 12: apt + systemd), x86_64 or arm64, root access. 2 vCPU, 4 GB RAM, 40 GB disk recommended.
• A Claude subscription (Pro, Max or Ultra, connected with claude setup-token) or an Anthropic API key.
• For HTTPS: a subdomain pointing to the server, DNS only (or use Tailscale / an SSH tunnel).
• Optional: a Telegram bot (BotFather, Threaded Mode on), a Groq key for faster voice.
• A server dedicated to Claude is recommended: sessions run Claude Code with full permissions by default (configurable).

Install

As root on the server (sudo -i first if you are logged in as another user):

curl --proto '=https' --tlsv1.2 -fsSL https://get.harness-maxxing.com | bash

It asks three questions (access mode, domain, restore a backup), clones this public repository (no key, no token), then installs packages, uv, Claude Code, the code, HTTPS with Caddy, the server security (firewall, fail2ban, security updates) and the service in about a minute; the tools (Node.js, Remotion, Scrapling and their shared Chromium) finish in the background. Every third-party download is a pinned version checked against its checksum (server/maxxing/deps.toml, managed with maxxing deps). It ends with a one-time setup link: open it, choose your password and follow the onboarding (language, Claude connection, import from another agent, first project, Telegram, backup).

Unattended: curl --proto '=https' --tlsv1.2 -fsSL https://get.harness-maxxing.com | ACCESS=domain DOMAIN=ui.example.com ASSUME_YES=1 bash. Updates come from this repository (maxxing update, or the Update button in Settings).

Other ways to install:

curl --proto '=https' --tlsv1.2 -fsSL https://get.harness-maxxing.com | REPO=you/your-fork BRANCH=main bash   # from your fork (updates from it)
bash /path/to/harness-maxxing/install.sh       # from a local copy (a clone with web/dist): no download, updates = a newer copy

No key and no account. Companies that need an Enterprise license give their key afterwards in Settings → License (optional): see docs/user/23-license.md. Servers installed with a key before 2.0.0a87 switch to the public git repository by themselves.

An anonymous counter (once a day: a random id, the version, the system and a few health codes; no name, no IP, no content) is on by default; turn it off in Settings → Profile, or with MAXXING_NO_TELEMETRY=1 (or DO_NOT_TRACK=1) in the service environment - see docs/user/23-license.md.

Day-to-day: maxxing status, maxxing doctor, maxxing update. Remove: maxxing uninstall.

Documentation

User documentation is in docs/user/ and inside the app (Settings -> Docs): welcome · installation · onboarding · sessions · memory · crons · telegram · backup · widgets · pages · security · troubleshooting · CLI · files · settings · customizing · import · tools · license · notifications · starter projects.

Developers: docs/dev/PLAN.md (architecture), docs/dev/API.md (HTTP contract), docs/dev/INTERNALS.md.

cd server && uv sync && uv run pytest        # server
cd web && npm ci && npm run build            # web UI (web/dist is committed)

Fair Source

Harness Maxxing is published under the Harness Maxxing Fair Source License, a source-available license (not an OSI open source license): the code is public and free, with a few limits that keep the project sustainable.

Allowed, free of charge

• use it, for any personal or professional purpose of your own;
• read, copy, modify and fork the code;
• redistribute it, changed or not, with the LICENSE and the copyright notice (and saying what you changed);
• an organisation may use it for the internal needs of one legal entity.

**Not al