DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run your own Comma instance with Docker Compose with Comma

Start a single-node personal agent on your own machine with one compose command.

Credentials. The model API key you put in .env and the secrets in the config volume must be kept private, and the config volume must not be deleted or regenerated.

Who it is forA privacy-minded individual or small team that wants a personal agent running on infrastructure they control instead of the hosted service.

The problemThe hosted service at comma.surf may not fit your privacy or control needs, so you want the same always-on agent under your own control.

The outcomeA single-node Comma instance running with its Web, Admin, Product API, and Salix dashboard interfaces, reachable on loopback by default.

What you need first

  • Docker Engine with Compose v2.24 or later for self-hosting
  • A model provider account, or a ChatGPT or Claude plan, for real model calls
  • Enough disk space for the first Docker build, which downloads Lean, Elixir, Go, and Node toolchains
  • A Mac with the Comma Mac app for local file and agent work
  • pnpm and make for local development

Steps

  1. Run cp .env.example .env in the repository root.
  2. Set COMMA_OWNER_EMAIL to your email address, and set COMMA_LLM_BASE_URL, COMMA_LLM_MODEL, and COMMA_LLM_API_KEY for your model provider in .env.
  3. Run docker compose up -d --build and wait for the first build to finish.
  4. Open the Comma Web address from the Interfaces table and request a login code with your email.
  5. Read the code in the local inbox at the Mailpit address in the Interfaces table, then sign in.

Prompt for your agent

Clone the AFK-surf/Comma repository and follow its Self-host with Docker Compose section to start a single-node instance for <owner email>. Report the Web, Admin, and Product API addresses from the Interfaces table and any build errors. Verify that the login code arrives in the local inbox before you finish.

Caveat. The README says the local inbox is for loopback use only and that public access needs an HTTPS reverse proxy and a real SMTP server.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page