Skip to content
Menu
DocsExamplesOpen sourceHow it worksGitHub ↗

AI TEAMMATES FOR ONGOING WORK

Hire a teammate.

Give it a responsibility. Teach it how your team works.
It learns on the job and builds the tools it needs along the way.

USE IT FROMSlackMicrosoft TeamsTelegramWhatsApp
Get startedExplore an example

MEET YOUR TEAMMATE

Open workspace full screen ↗

WHAT SHARED MEANS

Works for everyone on your team.

PPriya09:41in LemmaDoes our policy actually allow the Northfield refund?SSam14:20from WhatsAppNorthfield emailed me too — has that refund actually gone out?REFUND · ORDER 8841Northfield · $420Awaiting Priya’s reviewPolicy checked · reply drafted
Refund not issuedDDev10:02from SlackDid Priya's refund question land? Northfield are waiting on us.AAlex14:25in LemmaI can see the policy check and draft. Priya, this one is ready for your review.

Keep the status, decisions and history in shared records your team can return to.

WORK WITH YOUR TEAMMATE

Works where you work.

Your AI teammates, in the tools you already use.

IN YOUR TEAM’S CHANNELS

Part of the conversation. Part of the team.

Every AI teammate on Lemma can work with your team in Slack and Microsoft Teams. Ask for work, review what’s ready, and follow up in the channels you already use.

SlackMicrosoft Teams
SlackAcme# launch
EXAMPLE CONVERSATIONPRPriya 9:41 AMKit, what needs my attention before Thursday’s launch?Kit TEAMMATEThe landing page and announcement are ready for review. The demo needs three updated shots, and Harbor’s story still needs logo permission.
READY FOR REVIEWThursday launch review2 assets to review · 2 blockersLanding page · Announcement
Message #launch↵

CONFIGURE ACCESS FOR THE JOB

Choose who can see and change the work.

In this example, the support agent can draft replies for open refunds. People review the requests according to their assigned roles.

REFUNDS · 5 OF 88 ROWSNorthfieldValeKiteMorrowBrightpathPPriyaOWNERApproveDDevEDITOREditSSamVIEWERReadSupportTEAMMATEDraft
Within assigned accessOutside assigned access
PriyaOWNERApprove

All five refunds: Northfield, Vale, Kite, Morrow and Brightpath.

DevEDITOREdit

All five refunds: Northfield, Vale, Kite, Morrow and Brightpath.

SamVIEWERRead

All five refunds: Northfield, Vale, Kite, Morrow and Brightpath.

SupportTEAMMATEDraft

Open refunds: Northfield, Vale and Kite.

Closed refunds are outside this example’s access.
Shopify is the connected account in this example. Choose the accounts your own workflow needs.Approval is a configured step in this example, before a refund is issued.

HOW YOUR TEAMMATE RUNS

Choose how your teammate runs.

Choose a hosted model, connect a provider key, or pair a computer running a coding agent. Your teammate’s files and records stay in Lemma when you change its runtime.

YOUR COMPUTER

The coding agent already on your machine, running as this teammate.

Claude CodeCodexCursorOpenCodeTHE COMPUTER NEEDS TO BE ONLINE
YOUR PROVIDER KEY

Connect a provider account for your organization. Usage is billed by that provider.

Your API keyYour choice of modelYOUR PROVIDER’S MODELS AND USAGE LIMITS
LEMMA HOSTED

Use Lemma-hosted models without connecting your own computer or API key. Your account’s usage limits apply.

Managed by LemmaView usage in SettingsNO MACHINE OF YOUR OWN TO KEEP AWAKE

HOW THE WORK FITS TOGETHER

The work stays with your teammate.

Files and records hold the context. Apps help your team use it. Functions and workflows handle repeatable steps, with access and approvals configured for the job.

Look inside. Open any layer to see how it works.

Tables and files

What it remembers

TICKETS · 1,284 ROWS
iduuidprimary keycustomerrelation→ customersamountmoneyindexedstatusenumopen · drafted · closedcreated_attimestampauto
ROW-LEVEL SECURITY · THE CLASSIFIER SEES OPEN TICKETS ONLY
REFUND-POLICY.MD · MARKDOWN MEMORY

## Thresholds

Refunds above $250 require an approver.

Repeat requests inside 30 days escalate to a lead.

Policy lives here — versioned, editable, and read at run time alongside the tables.SEARCHABLE · PERMISSION-SCOPED

Functions

Always the same steps

CHECK_POLICY · DETERMINISTIC
fn check_policy(amount, customer) {
  policy = read("refund-policy.md")
  if amount > policy.threshold
    return { requiresApproval: true }
}
APPLY THE CONFIGURED REFUND POLICY
THE PREDICTABLE HALF
Plain code, end to end. No model in the loop.Validators, state changes and outbound actions live here.Agents call them as tools, so judgment and rules stay separable.
THE HALF YOU DO NOT WANT IMPROVISED

Agents and workflows

What moves the work

CLASSIFIER · AGENT
Can readtickets · customers · refund-policy.mdCan writetickets.statusCannot touchrefunds · api_keys · connectorsToolscheck_policy · search · table.update
EXAMPLE · CONFIGURED AGENT ACCESS
REFUND-REVIEW · WORKFLOW
classifyagentcheck_policyfunctionapprovehumansendfunction
It pauses at approve and resumes on a person’s decision — days later, if that is how long it takes.TRIGGERED BY A TABLE EVENT, SCHEDULE, WEBHOOK OR MESSAGE

Apps and surfaces

Where people meet it

SUPPORT OPS · EXAMPLE APP
TICKETACCOUNTSTATEtkt_418Northfield · $420Needs approvaltkt_417Halden · $38Senttkt_416Ravel · $120Sent
SUPPORT-OPS.LEMMA.WORK · ONE URL FOR THE TEAM
REACH THE TEAMMATE THROUGH OTHER CHANNELSSlackTeamsTelegramWhatsAppEmailThe APIApps and agents work with shared records. Connect a channel so your team can ask for updates from the tools they already use.SHARED RECORDS · CONNECTED CHANNELS

Permissions and connectors

The boundary it all sits on

CONNECTORS · CONNECTED ACCOUNTS
Stripebilling@acme.coissue refundsGmailsupport@acme.coread threads · create draftsShopifyops@acme.coread orders
Connect the accounts your teammate needs for the job. Review the account and permissions before authorizing access.CHOOSE WHICH ACCOUNTS TO CONNECT
ACCESS AND APPROVALS
Choose who can work with your teammate.A consequential step can require a named approver.Review access when you add tools or connect accounts.
SET THE BOUNDARIES FOR THE JOB

OPEN SOURCE, FROM THE START

Your work.
An open foundation.

See how Lemma works. Run it on your own infrastructure. Help shape what it becomes.

Explore the code on GitHub
Self-host Lemma ↗Start contributing ↗
AGPLv3 core · Apache 2.0 SDKs
Playful pink and green 3D teammates assembling colorful building blocks around the GitHub emblem.

What would you hand over first?

Get startedView on GitHub