MINDS-COWORK PLATFORM

Minds Platform is dedicated to building a general-purpose AI designed for knowledge workers — creators, strategists, and operators — and individuals seeking AI systems they can truly control to help them get work done, with full flexibility to extend and deploy anywhere (VPC, on-prem, or cloud).

USE CASES

For every knowledge worker

• Automate any repetitive multi-step task that involves reading and writing (reports, monitoring, workflows)
• Build internal AI tools/artifacts without engineering and deploy to your team (apps, decks, docs, analyses)

---

GET STARTED

Desktop App:

Simplest way to use this is the latest build App, available on web or desktop:

• web: Click here to register/login the Minds-cowork app, packaged and ready for you in one click.

• macOS: Click here to download the Minds-cowork for MacOS.

• Windows: Click here to download the Minds-cowork for Windows.

Build from source:

1. Clone the repository

git clone --recurse-submodules https://github.com/mindsdb/minds-platform.git
cd minds-platform

2. Install dependencies

make setup

3. Run

Mode	Command
Desktop app (Electron) with hot reload	make dev or make watch
Web app in browser with hot reload	make dev-web
Production build	make build
Package for macOS	make dist-mac
Package for Windows	make dist-win
Build macOS .app from local uncommitted source	make pack-local
Wipe all local installs + data (fresh start)	make flush

Reset to a clean slate: make flush uninstalls the local runtime (the cowork-server uv tool and the backend/*/.venvs) and deletes app state in ~/.anton (provider keys) and ~/.cowork (database, hermes, projects). Use it to test the from-scratch install flow or recover from a broken install. ⚠️ This deletes your conversations and saved keys. It prompts for confirmation; pass FORCE=1 to skip it. The next make setup or app launch reinstalls everything.

Working on feature branches (submodules)

This repo is a superproject that pins each module (frontend, backend/core_api, backend/core_agent, backend/data-vault) to a commit. To work on module branches without polluting git status or fighting over pins:

1. Pick your branches in a gitignored dev.env (copy the template):

cp dev.env.example dev.env      # then set REF=feat/my-thing (or per-module API_REF=…)

2. make follows it — one knob, both run paths:

Command	What it does
make use	check out your dev.env refs across all submodules
make dev / make watch	run the Electron app with live reload against local source
make dev-web	run the web SPA with live reload against local source
make server + make app	(re)install the desktop server from the configured branch, then launch
make server-local + make app-local	install the desktop server from local uncommitted source, then launch
make pack-local	build the macOS .app from local uncommitted source (no push needed)
make refs	show which refs the next run will use
make baseline	reset submodules to the pinned commits
make pin	record the current submodule commits as the superproject's pins (one deliberate commit)

Submodules are configured with ignore = all, so your branch work never shows up as superproject changes — the parent git status stays clean. Pins move only via make pin. See CLAUDE.md for the full workflow.

---

DEPLOY ANYWHERE

Minds Platform is designed for flexible deployment across:

• Cloud
• VPC
• On-Prem
• Air-Gapped Environments
• Hybrid Infrastructure

Maintain full control over your infrastructure, models, permissions, and data.

🫴 Help and support

Stuck on a query? Found a bug? We’re here to help.

Ask a question	Join our Slack Community.
Report a bug	Open a GitHub Issue. Please include reproduction steps!
Get commercial support	Contact the MindsDB Team for enterprise SLAs and custom solutions.

Security Note: If you find a security vulnerability, please do not open a public issue. Refer to our security policy for reporting instructions.

🤝 Contribute to Minds Platform

Minds Platform is open source and contributions are welcome! You can submit code changes through pull requests or by opening issues to report bugs, suggest new features, or enhancements.

How to contribute

• Read the contribution guide to get set up.
• Browse open issues.
• Join the #contributors channel in Slack.
• Explore community rewards and programs.

📚 Resources

• Documentation
• Blog
• Events
• Community Slack
• Brand guidelines
• Contact form