What lmctl does
lmctl gives native AI provider CLIs a shared local teamfile, names for members, and a chat path for handoffs. The team prompt and durable memory are the organizing layer.
Provider sessions are treated as disposable caches. Project knowledge lives in durable-memory files, so useful context can survive compaction, restarts, and provider changes.
Tutorials
Install & first run
Install lmctl, confirm the CLI, and run your first local checks.
Baby steps
Start with the low-commitment path: list sessions, name them, and route a review.
First workflow job
Older walkthrough for the image-qa path while the teamfile-first docs are being reconciled.
QA suite
Use ai-test chapters to drive repeatable manual checks through workflows.
Operating teams
Inspect team state, send prompts, read sessions, and track follow-up from the CLI.
Manuals / Reference
CLI / API reference
Lookup current commands for status, teams, sessions, chat, tail, seed, refresh, and local APIs.
Workflows & archetypes
Historical patterns being reframed as team delegation prompts and operating shapes.
Architecture overview
See how SQLite state, provider sessions, teamfiles, chat, and durable-memory fit together.