LazyMind README

The project's README from github.com/LazyAGI/LazyMind. As one markdown file: README.md.

LazyMind

中文 | English

img_v3_0215b_800b44bc-c72c-4bfa-8e99-7d7c9126310g

LazyMind: Keep AI-Agent under your control.

GitHub stars License macOS Windows Local first

LazyMind is an AI Skill Runtime for knowledge-intensive work: an environment that turns knowledge, expert practice, and tools into executable, recoverable tasks. It connects reusable knowledge, executable Skills, observable workflows, editable artifacts, and evaluation-driven improvement in one workspace.

Instead of repeatedly uploading context, tuning prompts, and supervising every agent step, you choose the knowledge and workflow once. LazyMind then plans, executes, exposes intermediate results, and carries accepted feedback into the next run. Use it locally in Desktop Mode, deploy it as a shared enterprise service, or provide knowledge, Skills, and Workflows to external agents such as Codex, Cursor, and WorkBuddy.

Quick start · Product architecture · Build a workflow · Desktop mode


What can you ship with it?

Scenario LazyMind runs You receive
Research and review Search sources → retrieve evidence → compare → synthesize → review A traceable report grounded in your documents and external sources
AI Writer Organize sources → outline → draft sections → revise → final review An editable, versioned document rather than a one-shot answer
Presentations Clarify intent → gather sources → outline → create and revise slides → export A PDF or PPTX with speaker notes and locally editable slides
AI Image Interpret intent → collect references → refine prompt → generate/edit Images and animated stickers with the process retained
Knowledge assistant Connect sources → parse/OCR → hybrid retrieve → rerank → answer Answers linked back to reusable organizational knowledge
External agent augmentation Connect projects and sessions → call knowledge, Skills, or Workflows → track execution LazyMind capabilities and artifacts inside the agent you already use
Quality improvement Capture a bad case → evaluate → diagnose → A/B test → deploy A verified strategy improvement, not an unchecked prompt change

For an end-to-end product video, see the Chinese README.

How LazyMind works

flowchart LR
    K["Knowledge<br/>local files · cloud docs · object storage"] --> R["Retrieve & reason<br/>parse · OCR · hybrid search · rerank"]
    S["Skills & workflows<br/>instructions · tools · state machines"] --> X["Observable execution<br/>steps · approvals · retry · rewind"]
    R --> X
    X --> A["Editable artifacts<br/>citations · revisions · delivery"]
    A --> F["Feedback & evaluation<br/>preferences · bad cases · A/B tests"]
    F --> K
    F --> S

This loop is built from three connected systems:

System Responsibility Product behavior
Knowledge Foundation Give AI the right context Multi-source ingestion, OCR, hybrid retrieval, reranking, and source traceability
State Brain Keep long tasks on course Visible steps, approvals, editable artifacts, retries, rewinds, and version history
AI Growth Engine Improve future runs safely Reviewable preferences and terminology plus evaluation, diagnosis, A/B tests, and rollback

Core highlights

1. Deliver outcomes, not chat messages

Choose knowledge and a Skill; LazyMind continues from source organization through planning, generation, review, and delivery. Workflows define steps, tools, inputs, outputs, and transitions as state machines, while artifacts preserve editable results and revision history.

For long-running work, each step remains visible. Users can approve checkpoints, edit an artifact, or rerun from the failed step instead of restarting the whole task.

A real Artifact remains editable at an approval checkpoint
Inspect and edit the Artifact before continuing
Inspect the execution trail and approve the next step without restarting
Review a version diff and restore the result you need

2. Ground every run in reusable knowledge

Local directories, object storage, Feishu, Notion, and other sources feed a unified knowledge base. PDFReader, MinerU, or PaddleOCR-VL parses documents; multi-embedding retrieval, hybrid search, and reranking keep results grounded in relevant evidence.

Manage parsed documents in a reusable knowledge base
Organize documents and track parsing status in one knowledge base
Answer with inline citations and an automatically generated reference list
Ground answers with inline citations and traceable references

3. Package expert practice into reusable workflows

Research methods, writing processes, and domain standards can be managed as Skills and converted into executable Workflows. Teams can diagnose, repair, publish, version, and roll them back instead of rebuilding the same setup from prompts and scripts. See the Workflow format specification.

Create an executable workflow from an existing Skill
Select a Skill as the source of a new workflow
Manage converted and custom workflows after generation
Inspect, refine, publish, and version the generated workflow

4. From an idea to an editable presentation

The PPT Workflow carries a presentation request through research, outline approval, slide generation, review, and export. It can use the user's prompt, uploaded files, LazyMind knowledge bases, web search results, and AI-generated images as source material, and it produces speaker notes for each slide.

After generation, users can reorder or remove slides and select text or elements for natural-language content and style changes. Results can be exported as PDF, image-based PPTX, or editable PPTX containing text, shapes, images, and charts.

Image placeholder: end-to-end PPT Workflow. Use one 16:9 screenshot showing the execution stages on the left, a real slide preview in the center, and the outline or source-material panel on the right. The stages should visibly cover research, outline, generation, review, and export.

5. Discover ready-to-run scenarios in the Capability Center

The Capability Center brings quick chat, complex tasks, and curated examples into one entry point. Users can filter by scenario, capability type, and technical tags; inspect the description, workflow, example input, and interactive result; then launch the capability in Chat or Work. Curated entries are backed by runnable Skills and installed on demand when first used.

Image placeholder: Capability Center home and detail view. Show category filters, at least six curated capability cards, and one detail view with a real result preview and a visible “Try it” action. The image should make clear that these are runnable capabilities rather than static examples.

6. Read, question, and revise directly inside documents

The document preview supports conversations scoped to the current document and can cite PDF selections, knowledge chunks, or partial chunk content. Temporary document conversations stay out of normal chat history unless the user chooses to promote and save them.

Selections in chat answers and Writer documents can be revised by AI at the smallest relevant scope. Users review the diff, accept or reject the result, and follow citations back to the original document.

Image placeholder: document chat and local revision pair. Use two side-by-side screenshots: a PDF selection entering a document-scoped conversation with citations, and an AI revision diff with visible Accept and Reject actions.

7. Give external agents the same knowledge and capabilities

LazyMind can discover local projects and native task histories from Codex, Cursor, WorkBuddy, TRAE Work, DeepSeek Harness, and other agents, then create, continue, and inspect their work in one workspace. Through MCP, external agents can also use LazyMind Workflows, Skills, knowledge bases, and cloud documents without rebuilding the same task context.

Image placeholder: external-agent collaboration. Show a Codex or Cursor task discovered and continued inside LazyMind, including project or session selection, execution status, tool steps, and a final artifact. Avoid using only a Settings connection screen.

8. Improve only after evidence

Knowledge Ops captures what the user wants—preferences, terminology, experience, and Skills. evo tests how the system should improve by turning bad cases into evaluation samples and running baseline evaluation, diagnosis, repair, and A/B testing.

Knowledge Ops reviews and improves reusable Skills
Knowledge Ops reviews Skills, preferences, terminology, and experience
The evo workspace turns failures into an evaluated improvement pipeline
Algorithm evolution validates improvements before rollout

9. Start local, scale when collaboration requires it

Desktop Mode uses native processes, SQLite, and Milvus Lite with platform-standard data paths. Shared deployments add Kong, JWT/RBAC, Core ACL, external Milvus/OpenSearch, and on-premises OCR. Your workflow stays recognizable across both modes.


Quick start

Run locally

Prerequisites: Go, Python 3, uv, pnpm, and Node.js.

make local-up

On native Windows PowerShell:

make local-win-up

After startup:

After login, open Settings in the frontend:

Select default models in frontend settings
Select the default models for each system capability
Configure document parsing and search providers in frontend settings
Configure document parsing, search, and integration credentials

Stop the local runtime with:

make local-down

Use make local-win-down on Windows. See the Quick Start guide for complete configuration.

Build the desktop application

Platform Command Output
macOS arm64 make desktop-darwin-arm64 macOS desktop application
Windows x64 make desktop-windows-x64 Portable ZIP
Windows x64 make desktop-windows-x64-installer Installer

Deploy with containers

make up

This starts both the Docker services and the host-side Assistant Bridge. Open Settings → Assistants to connect Codex, Cursor, WorkBuddy, Raccoon, TRAE Work, or DeepSeek Harness without running separate MCP configuration commands. If Docker is installed but Go is not, the bridge is cross-compiled for the host automatically inside Docker.

On Windows, run this command from Git Bash with make available. Do not replace it with bare docker compose up: containers cannot inspect or launch programs installed on the Windows host. On macOS and Windows, the host bridge discovers CLIs and desktop applications through the operating system; Settings → Assistants also accepts a custom or portable host path when automatic discovery cannot resolve it.

Startup Command Reference

Scenario Command
Build images and start make up-build
Deploy MinerU OCR on-premises make up LAZYMIND_DEPLOY_MINERU=1
Deploy PaddleOCR on-premises make up LAZYMIND_DEPLOY_PADDLEOCR=1
Use external Milvus/OpenSearch make up LAZYMIND_MILVUS_URI=http://your-milvus:19530 LAZYMIND_OPENSEARCH_URI=https://your-opensearch:9200

See the Colima setup guide or the complete Quick Start guide. The Architecture guide covers service dependencies, environment variables, and the authentication chain.


Available today

Area Current capabilities
Knowledge base Multiple sources, OCR, vectorization, hybrid retrieval, reranking, sync management
Agents RAG chat, tool calls, subtask timeline, artifacts, task center, long-context compression
Content creation AI Writer, PPT Workflow, AI Image, local revision, multi-format export
Workflows State machines, dynamic routing, automatic review, retry/rewind, visual execution, versioned artifacts
Skills Installation, organization, review, revisions, rollback, Skill → Workflow
Capability Center Curated Skills, scenario categories, interactive demos, on-demand installation
Document reading Current-document chat, PDF selection citations, source navigation, temporary conversations
External agents Local project and session discovery, task continuation, MCP access to knowledge and capabilities
Tasks and conversations Terminal states, archives, recycle bin, recovery, synchronized task and conversation status
Self-evolution Eval-set generation, evaluation, bad-case analysis, repair, deployment, A/B testing
Local experience macOS/Windows local runtime, desktop builds, platform-standard data paths
Enterprise Kong, JWT/RBAC, ACL, OAuth sources, optional external storage

This table describes capabilities implemented in the repository today, not a future roadmap. See docs for module design and implementation details.


Roadmap

LazyMind's next phase is not about adding more isolated features. The goal is to strengthen the Skill Runtime so knowledge, Skills, Workflows, and self-evolution form complete task loops both inside LazyMind and across other agents.

Near term: complete the core v0.4 capabilities

Skill Runtime and Desktop

External agent ecosystem

Task and resource infrastructure

Mid term: connect knowledge, creation, and distribution

Knowledge sources, editing, and publishing

Flagship scenario: evidence-driven paper research and technical writing

Image placeholder: paper reading to technical-guide workflow. Use a horizontal flow or four-panel composition showing PDF selection reading, the paper Evidence list, multi-paper comparison, and citation-grounded writing in AI Writer. Every stage should visibly preserve source information or navigation back to the original text.

Long term: from executable workflows to a self-evolving work system

The roadmap will evolve based on real workflow completion rates, output quality, human interventions, latency, and cost. Repository issues, milestones, and release notes remain the source of truth for specific releases.


Project layout

LazyMind/
├── frontend/                   # Web UI and desktop frontend
├── backend/
│   ├── auth-service/           # Authentication, OAuth, and users
│   ├── core/                   # Data, tasks, retrieval, Workflows, and ACL
│   └── scan-control-plane/     # Source scanning and synchronization
├── algorithm/
│   └── lazymind/               # Chat, parsing, retrieval, and agent runtime
├── workflows/                    # Built-in Workflows
├── skills/                     # Built-in and curated Skills
├── evo/                        # Self-evolution and evaluation loop
├── desktop/                    # Electron desktop application and packaging
├── local/                      # Host-local runtime management
├── api/                        # OpenAPI specifications
├── docs/                       # Architecture, usage, and design docs
└── tests/                      # Cross-service tests

Development and testing

make lint              # Python, Go, docs, and other static checks
make lint-only-diff    # Check changed files only
make test              # Test with host-provided runtimes
make test-hermetic     # Test the same scope in project-managed runtimes

License

See LICENSE.

LazyMind (LazyAGI/LazyMind)

ppt
Searching Database…

What is this?LazyMind is an AI Skill Runtime for knowledge-intensive work: it turns knowledge, expert practice, and tools into executable, recoverable tasks, combining reusable knowledge, executable Skills, observable workflows, editable artifacts, and evaluation-driven improvement in one workspace.
Is this a chat assistant or something closer to a workflow engine?It is closer to a workflow engine with a chat layer on top: work is organized as Workflows, which are state machines with defined steps, tools, inputs, outputs, and transitions, plus editable Artifacts that keep version history, rather than a single back-and-forth chat.
How do I get it running locally?Install the prerequisites (Go, Python 3, uv, pnpm, Node.js), start the local environment through the Quick Start make/PowerShell commands, then log into the frontend with the default admin/admin credentials and configure model providers. You can also build a native desktop app or deploy it with Docker containers instead.
Which coding agents can connect to it?Through a host-side Assistant Bridge and MCP, LazyMind connects to Codex, Cursor, WorkBuddy, Raccoon, TRAE Work, and DeepSeek Harness, letting it discover their local projects and task histories and let them reuse LazyMind's knowledge, Skills, and Workflows.
What happens if a workflow step fails halfway through?Every step stays visible during execution, so instead of losing the whole task you can approve a checkpoint, edit the artifact produced so far, or rerun from just the failed step.
Who is this built for — developers or non-technical staff?Desktop Mode targets technically capable professionals whose main job isn't programming, like solution architects, product managers, operators, testers, and content creators, while team/enterprise deployments serve secondary development, delivery, and org-wide knowledge collaboration.
Can it run fully on my own machine without a server?Yes, Desktop Mode runs on native processes with SQLite and Milvus Lite stored under platform-standard data paths; Docker and shared services like Kong and external Milvus/OpenSearch are only needed when you move to team or enterprise deployment.
What is the Capability Center?It is a single entry point that lists quick chats, complex tasks, and curated examples, filterable by scenario and tag, backed by runnable Skills that get installed on demand when you first use them.
Can it turn research or a prompt into a finished slide deck?Yes, the PPT Workflow walks from research and outline approval through slide generation, review, and export, producing speaker notes, and can export as PDF, image-based PPTX, or an editable PPTX with real text, shapes, images, and charts.
How does LazyMind improve itself over time?The evo system turns a captured bad case into an evaluation sample, then runs baseline evaluation, diagnosis, a repair, and an A/B test before any improved Skill or Workflow is rolled out or rolled back.
How does it ground answers in my own documents?Sources from local folders, object storage, Feishu, or Notion are parsed with PDFReader, MinerU, or PaddleOCR-VL, then retrieved with multi-embedding hybrid search and reranking so chat answers cite the original passages.
Creator
LazyAGI
Size
340.8 MB
Stars
256
Age
2y
Commits · 90 Days