| related_files |
|
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| maintenance | Tracks the public repo overview and architecture entry-point table; must stay synced with docs/readmes/ translations and with the linked entry-point files whenever the repository's structure or onboarding steps change. |
The Python runtime and SDK that powers LingTai agents.
This repository is the engine underneath the product, not the product itself.
Looking for LingTai the product? The Lingtai-AI/lingtai
repository is the source of truth for the Digital Scientist — the lifelong, self-growing
agent — including the guided installer, the TUI/Portal, and everyday workflows. Normal
users should start there and let the installer manage this runtime for them. This
repository is for developers who build on or contribute to the kernel; do not treat a
bare pip install here as the normal installation path.
- The agent runtime — the core turn loop, lifecycle, tool dispatch, mailbox, soul (inner voice), molt, and notification machinery that make an agent run.
- Two Python surfaces —
lingtai.kernel, the minimal runtime (BaseAgent, intrinsics, the LLM protocol, mail, and logging), andlingtai, the batteries-included runtime, CLI, and services that buildAgent(BaseAgent)on top of it and re-export the kernel's public API. - The batteries — the bundled built-in tools, the LLM adapters, the curated MCP server implementations, the packaging (Python distribution plus the bundled Rust search sidecar). These are ownership boundaries, not a feature list.
For kernel development — not the normal LingTai user installation path. Requires
Python >= 3.11; use a local .venv.
git clone https://github.com/Lingtai-AI/lingtai-kernel.git
cd lingtai-kernel
uv venv --python 3.11
uv pip install -e . pytest
.venv/bin/python -m pytestBefore changing anything, a coding agent first finds and reads this repository’s local dev guide skill; it owns the workflow and routes each task onward through the linked entry points below without duplicating the Anatomy or Contract systems.
| Entry point | What it covers |
|---|---|
dev-guide-skill/SKILL.md |
The mandatory repository-local dev guide skill: the development workflow a coding agent must follow before editing. |
ANATOMY.md |
Repository structure/composition map — where each subsystem's anatomy begins and how it reaches its behavioral Contract. |
CONTRACT.md |
Normative interface/behavior promises plus the governed-component pairing/ownership rule, linked back to Anatomy structure. |
src/lingtai/kernel/ANATOMY.md |
The core runtime: BaseAgent, turn/lifecycle, tool machinery, mail, LLM protocol. |
src/lingtai/ANATOMY.md |
The lingtai package: Agent(BaseAgent), capabilities, presets, CLI, public re-exports. |
src/lingtai/tools/ANATOMY.md |
The concrete built-in tools and the registry that composes them. |
src/lingtai/mcp_servers/ANATOMY.md |
The bundled MCP server implementations. |
CONTRIBUTING.md |
Contribution workflow and repository navigation. |
docs/references/claude-code-guide.md |
The full repository guide — test commands, architecture notes, and conventions. |
For responsible disclosure, read SECURITY.md; for help, read SUPPORT.md; for credits, read docs/references/acknowledgements.md.
Apache-2.0 — Zesen Huang, 2025–2026