Lattice AI

Your model is the voice you use today. Your Brain is the asset you keep.

모델은 갈아타도, 내 지식은 내 컴퓨터에 남는 로컬 우선 AI 브레인.

v12.3.0 Living Brain walkthrough

Lattice AI is a Digital Brain that lives on your computer. Chat, files, folders, notes, and web pages all land in one knowledge graph you own. The default is local. Cloud is optional, and nothing leaves the machine without your consent.

대화·파일·폴더·웹페이지가 전부 내 컴퓨터 안의 지식 그래프로 쌓입니다. 기본은 로컬이고, 클라우드는 선택입니다.

Install

pip install ltcai        # or: npm install -g ltcai
LTCAI                    # then open http://127.0.0.1:4825/app

Apple Silicon local models: pip install "ltcai[local]"
Mac app: the .dmg on each GitHub Release
Editor: the VS Code / Cursor / Open VSX extension

First five minutes

Open the app and sign in as the owner.
Pick a recommended local model for this computer.
Drop a folder, a file, or a note into Capture.
Ask the Brain a question in your own words.

Screenshot index: output/release/v12.3.0/SCREENSHOT_INDEX.md

What you can do


See your Brain's story in time — a growth curve, an activity heatmap, and each day's story	Chat with a Brain that remembers — every conversation grows durable, source-linked memory
See how knowledge connects — a real relationship graph, not a file list	Capture anything — files, whole folders, notes, screenshots, web pages
Automate with review — agent changes become proposals you approve first	Pick a model in one click — recommended local models for your hardware
Watch a file become memory — three named steps, not a pipeline diagram	Say how much it may do alone — one dial in plain words

Why this is yours

The memory stays. Knowledge lives in a local SQLite Brain you can back up, export, inspect, and restore (.latticebrain).
The model is replaceable. Switch local MLX and optional cloud without rebuilding context from zero.
It says when it does not know. Thin retrieval, a poor page extract, or hash-only search is named, not dressed as meaning.
Edits wait for you. New files can land with little friction. Changing or deleting existing files becomes a proposal with a diff.
Small models can still act. A 2B-class local model can call tools and skills; a model too small to emit JSON is walked through numbered choices.

매번 AI에게 프로젝트 맥락을 다시 설명하고 있다면, 지식이 여러 서비스에 흩어져 있다면, 그 기억을 특정 회사가 아니라 내가 소유하고 싶다면 — Lattice AI가 그 브레인입니다.

Current Release

The current release is 12.3.0 — Live Wire:

Model catalog routes, GGUF quantization tags, small-model tool/MCP calling, and HTML generation/inspection/download are verified end-to-end against live repositories and a loaded local model. The door is still 422 operations / 41 families over a 20-route worker. Cloud is still optional and the default is still local.

Verified Hugging Face GGUF tags & routes. ggml-org/gemma-4-*-GGUF uses Q4_0, ggml-org/gpt-oss-20b-GGUF uses MXFP4, and Qwen3.5-9B / Qwen3.6-35B-A3B GGUF routes are wired across ollama, lmstudio, and llamacpp.
Auxiliary GGUF filtering, --mmproj companion load, and shard checks. mmproj-/mtp-/dflash-/eagle3-/imatrix GGUFs are excluded from primary weight selection, companion mmproj-*.gguf files are downloaded for llama-server, and model.safetensors.index.json shards are verified.
Small-model tool calling & MCP calling hardening. Expanded KNOWN_ACTIONS, stringified arguments recovery, OpenAI tool_calls array unwrapping, fenced HTML/code block salvage, and adopt_named_args in perform_action.
HTML structure inspection & RFC 5987 UTF-8 download. POST /tools/inspect_html extracts title, links, scripts, stylesheets, images, forms, and headings; GET /tools/download decodes UTF-8 paths and sends filename*=UTF-8''....

Release notes live in docs/releases/. This version: docs/releases/RELEASE_NOTES_v12.3.0.md. Guide: RELEASE.md · History: docs/CHANGELOG.md.

Expected artifacts for 12.3.0 must use exact filenames:

dist/ltcai-12.3.0-py3-none-any.whl
dist/ltcai-12.3.0.tar.gz
ltcai-12.3.0.tgz
dist/ltcai-12.3.0.vsix
src-tauri/target/release/bundle/dmg/Lattice AI_12.3.0_aarch64.dmg

Do not use wildcard artifact uploads. Package registry publishing remains owner-run.

Architecture At A Glance

One Rust server on localhost is the source of truth: lattice-host answers every product route, owns every write to the Brain, and supervises a Python AI worker it reaches over loopback for the things a model does — inference, embedding, extraction, parsing, rendering, speech-to-text. The React/Vite frontend and the Tauri desktop shell sit on top of that one door. Local-first by default — cloud is optional (OAuth CLI or an API key you configure), and downloads, Brain Network, and update checks are opt-in.

See ARCHITECTURE.md for details and docs/DEVELOPMENT.md for the developer workflow (npm start / bin/ltcai.js is the product; npm run dev is the 20-route worker). Each of the two largest crates carries its own domain map — rust/lattice-agent/ARCHITECTURE.md and rust/lattice-platform/ARCHITECTURE.md — and open gaps are tracked in docs/ROADMAP.md. Validation via npm run lint, npm run test:unit, npm run test:visual.

Known Limitations

External package registries are owner-published and can lag behind GitHub.
SQLite is the live local Brain store. The optional PostgreSQL/pgvector migration tooling is not part of the 12.1.0 worker.
Docker, model downloads, cloud model calls, Brain Network, and update checks require explicit user action. Cloud is optional: cli_oauth (agy / grok) was live-checked at zero billing; the api_key path probes GET /models with the key and fail-closes if the provider is unreachable — it does not run a billed completion to verify.
The Telegram bridge was removed in 11.6.0 — it lived in the platform code that became the AI worker. SSO/OIDC login and callback flows were removed with it; the configuration surface remains and password login is native.
Conversation does not fabricate answers when no model is loaded. Agent and workflow simulation without a loaded LLM is deterministic and LLM-free (it does not call a model) — labeled as such, never presented as autonomous model success.
POST /worker/render/pdf ships working out of the box: reportlab is a required dependency as of 11.6.0 (it used to be an undeclared lazy import that raised a 500; ltcai[pdf] remains as an empty alias for older install instructions).
The multimodal image and video analysis functions have no HTTP door as of 11.8.0: their only route wrapped a native image ingest that was never built. The observation code stays in Brain Core under unit test, and its module header says so.
The Python coverage gate is a line floor of 90 since 11.8.0 (the 100%-lines-and-branches gate was removed). The enforced claim is the floor, not whatever a given run measures.
Small-model content quality is gated honestly. With the guided profile even a 0.5B model writes the requested file and reaches DONE. A requested summary is filled from the file that was actually read; if those words are still missing the run is held for review, not marked done.
Vector search env still defaults to brute — exact and byte-compatible on a small Brain. At 512+ vectors with a bound worker sidecar it tries hnsw+rescore first and falls back to the exact scan if the sidecar cannot answer. LATTICEAI_VECTOR_INDEX=hnsw is still the explicit opt-in.
Watch prune removes vanished files from the graph, never from disk. A one-shot folder ingest still reports vanished files and waits for the confirmed prune door.
The macOS dmg is ad-hoc signed — effectively unsigned — so first launch needs the usual Gatekeeper step.
Pointer-control tools execute in the worker and are installed with pip install "ltcai[pointer]". Remaining honest gaps (open_keys pending-only, no Self-Model refiner, delete_node leaving PART_OF, review events silent without an owner, KG-api ingest text-only, two store cycles per review mutation) are listed with their reasons in docs/releases/RELEASE_NOTES_v12.3.0.md and prioritized in docs/ROADMAP.md.

Release History

Public history starts at 11.0.0. 11.6.0 rebuilt the product server in Rust and reduced the Python package to an AI worker, so a 10.x or 9.x install is a different program; SECURITY.md supports only 11.x, and this table states the same boundary. Earlier notes live in docs/releases/.

Version	Theme
12.3.0	Live Wire
12.2.1	True Count
12.2.0	Small Voice
12.1.0	Fast Path
12.0.0	Open House
11.9.0	Working Order
11.8.0	Travel Light
11.7.0	Clean Sweep
11.6.0	One Door
11.5.2	Tight Ship
11.5.1	Rust Full Loop
11.5.0	Rust Complete
11.4.0	Rust Foundation
11.3.0	Time Remembers
11.2.0	All Systems On
11.1.0	Product Intelligence
11.0.1	Both Branches
11.0.0	Full Measure

Per-release details: RELEASE_NOTES.md · folder: docs/releases/

Metadata

Release files for ltcai 12.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ltcai 12.3.0
File	Size	Uploaded	Provenance
ltcai-12.3.0.tar.gz	2.5 MB	Oct 18, 2026	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for ltcai 12.3.0
File	Interpreter	ABI	Platform	Reset
ltcai-12.3.0-py3-none-any.whl 2.0 MB Oct 18, 2026 Without provenance	Python 3	none	any	Details

Total release size: 4.5 MB

Release files / ltcai-12.3.0.tar.gz

Download URL	ltcai-12.3.0.tar.gz
Size	2.5 MB
Tags	Source
SHA-256 checksum How to use checksums	`330c60fadbe451b48ef4e692478ccf5c1bff7b979171e569dd1caa612443afbe`
BLAKE2b-256 checksum How to use checksums	`9a8092c5b13d4f9eca41fc346a861783a3360b3802dd0bbfcf91f0e1c7706c79`
Upload date	Oct 18, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.11.17`

Release files / ltcai-12.3.0-py3-none-any.whl

Download URL	ltcai-12.3.0-py3-none-any.whl
Size	2.0 MB
Tags	Python 3
SHA-256 checksum How to use checksums	`ada1be6ade5df480fbe65c3120f1722e248815fabfd87e9b400dfbfba20159b1`
BLAKE2b-256 checksum How to use checksums	`b5eccc75c375ac7498bae86cf006c07cda338425131380d2dc83e3d8c3517ff0`
Upload date	Oct 18, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.11.17`

Security for ltcai 12.3.0

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.