Linghun: a local-first, evidence-first AI programming terminal
Linghun is a local-first, evidence-first AI programming terminal that connects the model to real projects, tools, permissions, verification and context.
Verified
Core facts
Read by a script from the official API, not rewritten by a model.
- Repository
- https://github.com/linghungegeg/Linghun
- License
- Apache-2.0
- Languages
- TypeScript
- Maintainer
- linghungegeg
- Verified
What it is
Linghun is a local-first, evidence-first AI programming terminal. Linghun can be understood as an engineering exoskeleton fitted onto a large model. The model is responsible for understanding, reasoning and generation. Linghun is responsible for connecting the model to real projects, real tools, real permissions, real verification and real context.
Main features
Linghun supports OpenAI-compatible, DeepSeek and Anthropic Messages style endpoints, covering streaming output, tool calls, usage, reasoning, timeout, idle timeout, provider diagnostics and failure summaries.
Linghun has built-in tool paths such as Read, Write, Edit, MultiEdit, Grep, Glob, Bash, Todo, Diff and Git.
Linghun supports Workflow Matrix, durable job, background task, agent transcript, budget, steps, logs, reports and handoff boundaries.
Linghun distinguishes PASS, PARTIAL, FAIL, TIMEOUT, STALE and CANCELLED, and also distinguishes focused verification, mock verification, real smoke and unverified conclusions.
Before and after large changes, Linghun can check Git status, create stable points, help manage worktrees, and bind Git-related conclusions to the real repository state.
Roles such as planning, execution, review, verification, summary, vision and image can use different model routes.
Getting started
The environment requirements include Node.js 22 or newer.
After installing, start Linghun first, inside the project you want to work on; besides linghun, Windows also supports the capital-L Linghun as a compatible entry, so pick either one. /model setup runs after Linghun has started and /model doctor checks the provider configuration; both are used inside the Linghun session, not separately in the system terminal.
The model provider key is saved by default in a user-private configuration outside the project.
By default, Linghun runs code execution on your machine.
npm install -g @linghun/clilinghunLinghunlinghun --version/model setup/model doctorWho it is for
Linghun is still under active development. Linghun uses the Apache License 2.0. Linghun does not require users to first memorize a pile of English commands.
MCP, Skills, Plugins, Workflows and Hooks provide extension entries, following the principles of metadata before execution, trust before enabling, and diagnosis before use. Remote notifications and approvals can connect to channels such as WeCom, Feishu/Lark and DingTalk. The remote channel is not a remote execution platform that bypasses local permissions, and it should not send full code and full transcripts to external platforms at will.
Emotion and user state cannot replace permission confirmation, cannot serve as test evidence, cannot trigger automatic agent/job/workflow execution, and cannot justify writing files beyond permission because the user is in a hurry. Evidence Merge distinguishes evidence that can support a completion claim from states that can only serve as context. Agent summary, job completed, remote event and failure learning cannot pose directly as PASS.
Controlled memory uses a candidate-first confirmation flow, to avoid writing one-off emotions, sensitive information or unconfirmed facts as lasting rules. AntiCodeBlob prompts remind the model not to keep piling code into god files, overlong functions, deep nesting or unbounded global state. The Linghun architecture system watches module boundaries, dependency direction, responsibility backflow, duplicate runtime, permission bypass, diagnostic leakage, frontend/TUI experience constraints and delivery consistency.
The ordinary main screen does not leak provider, baseUrl, endpointProfile or plaintext key. Linghun is positioned as not bound to a single model vendor, and instead provides a unified engineering exoskeleton for different models. Linghun can use a code index, search, architecture evidence, workspace snapshots and large file protection to reduce repeated file reading.
Linghun can accumulate project rules, handoff summaries, controlled memory and failure experience. Linghun pays attention to prompt cache, tool list stability, context noise, long log summaries, cache freshness and usage tracking.
Sources
This page is written from the official sources below. Open them to check the original text.
- GitHub READMEhttps://github.com/linghungegeg/LinghunFetched
Verified ·
This page is written by AI from the official sources above and checked automatically. This site has not tested it. Found a mistake? Tell us.