Get it running
Paste this into the AI that runs on your computer. It does the install, checks it works, and tells you what to type first. If anything fails, paste the error back to it.
Paste into Claude Code
Install loomio (https://github.com/loomio/loomio) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Claude Code, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Make a loomio-deploy directory on the server and download docker-compose.yml, env_template, create_env.sh and update.sh from the repo's deploy/ folder with curl, as the self-hosting guide shows; do not clone the whole repo. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Point an A record for the hostname at the server, an MX record to the same hostname for reply-by-email, and a CNAME for hocuspocus.<hostname> for live editing; open ports 25, 80 and 443 before you start. Run ./create_env.sh <hostname> <admin email> to write .env with generated secrets, then edit the SMTP_ variables by hand; until they are right Loomio sends no mail, so nobody can confirm a sign-in. Initialise the database with docker compose up -d db then docker compose run --rm app rake db:setup, then start everything with docker compose up -d and watch docker compose logs -f. A 503 on the first visit usually means the Rails app is still starting behind nginx; wait a minute and reload. After the first sign-in and email confirmation, grant admin with docker compose run --rm app rails runner 'User.last.update!(is_admin: true)' and check /admin loads. Read deploy/UPGRADING.md before any minor or major upgrade. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Put one live decision to the team. If anything fails, show me the exact error and fix it before going on.
Paste into Kimi
Install loomio (https://github.com/loomio/loomio) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Kimi, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Make a loomio-deploy directory on the server and download docker-compose.yml, env_template, create_env.sh and update.sh from the repo's deploy/ folder with curl, as the self-hosting guide shows; do not clone the whole repo. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Point an A record for the hostname at the server, an MX record to the same hostname for reply-by-email, and a CNAME for hocuspocus.<hostname> for live editing; open ports 25, 80 and 443 before you start. Run ./create_env.sh <hostname> <admin email> to write .env with generated secrets, then edit the SMTP_ variables by hand; until they are right Loomio sends no mail, so nobody can confirm a sign-in. Initialise the database with docker compose up -d db then docker compose run --rm app rake db:setup, then start everything with docker compose up -d and watch docker compose logs -f. A 503 on the first visit usually means the Rails app is still starting behind nginx; wait a minute and reload. After the first sign-in and email confirmation, grant admin with docker compose run --rm app rails runner 'User.last.update!(is_admin: true)' and check /admin loads. Read deploy/UPGRADING.md before any minor or major upgrade. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Put one live decision to the team. If anything fails, show me the exact error and fix it before going on.
Paste into Gemini CLI
Install loomio (https://github.com/loomio/loomio) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Gemini CLI, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Make a loomio-deploy directory on the server and download docker-compose.yml, env_template, create_env.sh and update.sh from the repo's deploy/ folder with curl, as the self-hosting guide shows; do not clone the whole repo. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Point an A record for the hostname at the server, an MX record to the same hostname for reply-by-email, and a CNAME for hocuspocus.<hostname> for live editing; open ports 25, 80 and 443 before you start. Run ./create_env.sh <hostname> <admin email> to write .env with generated secrets, then edit the SMTP_ variables by hand; until they are right Loomio sends no mail, so nobody can confirm a sign-in. Initialise the database with docker compose up -d db then docker compose run --rm app rake db:setup, then start everything with docker compose up -d and watch docker compose logs -f. A 503 on the first visit usually means the Rails app is still starting behind nginx; wait a minute and reload. After the first sign-in and email confirmation, grant admin with docker compose run --rm app rails runner 'User.last.update!(is_admin: true)' and check /admin loads. Read deploy/UPGRADING.md before any minor or major upgrade. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Put one live decision to the team. If anything fails, show me the exact error and fix it before going on.
Paste into Codex
Install loomio (https://github.com/loomio/loomio) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Codex, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Make a loomio-deploy directory on the server and download docker-compose.yml, env_template, create_env.sh and update.sh from the repo's deploy/ folder with curl, as the self-hosting guide shows; do not clone the whole repo. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Point an A record for the hostname at the server, an MX record to the same hostname for reply-by-email, and a CNAME for hocuspocus.<hostname> for live editing; open ports 25, 80 and 443 before you start. Run ./create_env.sh <hostname> <admin email> to write .env with generated secrets, then edit the SMTP_ variables by hand; until they are right Loomio sends no mail, so nobody can confirm a sign-in. Initialise the database with docker compose up -d db then docker compose run --rm app rake db:setup, then start everything with docker compose up -d and watch docker compose logs -f. A 503 on the first visit usually means the Rails app is still starting behind nginx; wait a minute and reload. After the first sign-in and email confirmation, grant admin with docker compose run --rm app rails runner 'User.last.update!(is_admin: true)' and check /admin loads. Read deploy/UPGRADING.md before any minor or major upgrade. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Put one live decision to the team. If anything fails, show me the exact error and fix it before going on.
What to point it at first
1
Put one live decision to the team
Open a group, start a thread with the context in the first post, and raise a proposal your team actually needs to settle this week, with a closing date, so the first run carries a real outcome instead of a demo.
2
Write the outcome back
When the proposal closes, record the outcome in plain words next to the votes and the reasons; good output is a record someone new could read cold and understand what was decided and why.
3
Test the email path before you trust it
Send yourself an invitation and reply to a notification by email; check the invite arrives, the reply appears in the thread, and nothing lands in spam, because most setup problems live in mail.
What it must never do unattended
- It argues. You decide.
- Never let an agent cast a vote or close a proposal on anyone's behalf.
Who made it
loomio/loomio on GitHub, under the AGPL-3.0 licence. 2,598 stars, checked 11 September 2026. Last change 11 September 2026. We did not write it; we checked it, and wrote this page so you can use it.