Hire an AI teammate.
Share it with your people. It learns from all of you and builds itself around how you work.
Open source · Dots + Spaces + Lovable, for teams
Runs on the Claude Code or Codex subscription you already pay for.
What makes it a teammate · Quickstart · For developers · Inside a pod · Examples · Docs
What makes it a teammate
Built for real work
- Permissions that hold. Roles per person, access per row, approvals where a person decides. The same rules in the app, in Slack and on WhatsApp.
- Open source. AGPLv3 core, Apache 2.0 SDKs. Run it on your laptop, your server, or Lemma Cloud.
Try Kit’s space yourself, no sign-up: lemma.work.
Quickstart
Lemma Cloud
The same stack, hosted, reachable by teammates and surfaces:
uv tool install lemma-terminal
lemma servers select lemma-cloud
lemma auth login
lemma skills install
lemma pod create support-ops --with-starter # scaffolds a working starter (table + agent) and imports it
lemma chat "what can you do in this pod?"
Your laptop
Download Lemma Desktop, choose Local, and select Install local services.
Lemma owns the local runtime and picks its own ports, so one bootstrap command
reads them back out of Desktop and registers them with the CLI as the local
server.
Run this after Desktop's local setup has finished once:
uv tool install lemma-terminal
curl -fsSL https://raw.githubusercontent.com/lemma-work/lemma-platform/main/install.sh |
bash -s -- --cli-only # registers Desktop's endpoints as the local server
lemma servers select local
lemma auth login
lemma skills install
lemma pod create support-ops --with-starter
Then open the generated support-ops/ directory in the coding agent you already
use and describe the system you want. Full Desktop, Agent Host, and provider
setup lives in Install in depth and
docs/installation.md.
Use uv tool install, not pip. lemma-terminal needs Python 3.14, and
uv tool install provisions that interpreter itself, so whatever python3 is
on your machine does not matter. pip install lemma-terminal on an older
interpreter does not fail — it quietly resolves back to 0.6.2, the last
release that allowed 3.11, and installs a CLI several minors behind the server.
lemma --version reports what you actually have.
If a command did not do what it says here:
| Symptom | What to do |
|---|---|
Server not found: local |
Desktop's local setup has not run, or the bootstrap above was skipped. Run it, then lemma servers show to confirm which server is active. |
| Agents unavailable, or chat answers with a provider error | No AI provider has validated yet. Local Control Center → AI Providers; Ollama or LM Studio if you have no API key. |
| Something works in the app but not in the CLI, or the other way round | lemma doctor — it diagnoses client/server version skew and duplicate installs. |
For developers: a multiplayer, self-improving harness
A harness is everything around the model: the tools it can call, the memory it reads, the state it writes, the loop it runs in, and the boundary it works inside. Coding agents gave you a harness for one person, on one machine, for the length of one session.
Lemma is that harness for a team. Every teammate's space is a pod underneath: the tables, files, agents, workflows, permissions and apps described below. State is shared and permissioned, so many people and many agents work the same records. It keeps running between sessions, on schedules, webhooks, and table events. And it compounds: corrections become standing instructions, sequences become workflows, judgment becomes an agent role. The harness your team uses next month is better than the one you ship today, because using it is what improved it.
Your coding agent builds it. Describe the job to Claude Code, Codex, Cursor, OpenCode, or Antigravity; it writes the whole system as files: the app people open, the tables underneath it, the agents, the workflows, and the permissions. Then it imports and verifies the result t