LORE
Install
Safety modes
Use full-auto, auto-safe, ask, or read-only depending on how much control you want.
Open-source terminal agent
Bring your own key. Keep the memory.
Lore is an open-source AI coding agent for your terminal. It connects directly to your chosen provider, keeps project memory in .lore/, previews risky work, creates rollback snapshots, and verifies changes before you trust them.
lore session
$ export OPENROUTER_API_KEY=sk-or-v1-...
$ lore init
lore > created local wiki in .lore/
$ lore
you > add rate limits to the API
lore > reading wiki, checking routes, preparing diff
VERIFY go test ./... passed, ledger saved to .lore/runs
$ lore init
lore > created local wiki in .lore/
$ lore
you > add rate limits to the API
lore > reading wiki, checking routes, preparing diff
VERIFY go test ./... passed, ledger saved to .lore/runs
git clone https://github.com/fayzkk889/lore && cd lore && go build -o lore .
MITOpen-source license
0Middleman servers
4Safety modes
v0.9.1Beta release line
Project wiki memory
Stop re-explaining the same codebase.
Lore turns your repository into a local, git-friendly knowledge base. Every session starts from your wiki, rules, recalled notes, and recent learnings.
Initialize once
lore init scans architecture, conventions, entities, and project structure into .lore/.
Guide every session
Add LORE.md with rules Lore should always follow, from test commands to architecture constraints.
Recall and remember
Use /memory, /remember, /wiki, and /recall to shape the project knowledge base.
Verified completion
An agent you can inspect.
Lore is built around local consent, recovery, and evidence that the work actually ran.
Build, vet, test, runtime
Verified completion means running the checks that matter: build commands, vetting, tests, and runtime smoke checks when configured.
Verification ledgers
Check results are stored locally under .lore/runs, with redacted summaries you can inspect later.
Rollback snapshots
Snapshots are hardened to avoid obvious secrets and preserve files Lore intentionally skipped.
Audit trail
Use /runs, /audit, /status, /rollback, and /permissions inside the TUI.
Headless mode
Run scripted work with lore do, using the same project context and permission defaults.
Direct provider connections
No telemetry. No hosted metering. No middleman server.
Lore connects from your machine to your selected provider. You bring the key, choose the model, and pay the provider directly according to their terms.
Cloud models
Use Anthropic, OpenAI-compatible endpoints, OpenRouter, DeepSeek, or custom base URLs.
Local models
Run against Ollama for local workflows, experimentation, and offline-friendly development.
Open source
The source is public at github.com/fayzkk889/lore.
Release installers
Install scripts target signed release artifacts and checksum verification for v0.9.1-beta.
Demo
Watch a session unfold.
The core flow is simple: choose a provider, ask, inspect, apply, verify, and let Lore update project memory when the work is done.
Comparison
Built for local trust.
| Capability | Hosted coding tools | Lore |
|---|---|---|
| Provider path | Often routed through a product service | Direct from your machine |
| Project memory | Manual files or remote history | Local .lore/ wiki plus LORE.md rules |
| Change safety | Diffs vary by tool | Preview, teach, rollback snapshots |
| Verification | Often conversational | Local self-check and ledgers |
| Automation | Interactive only in many tools | TUI plus headless lore do |
Open source, BYO key
Clone Lore and build it locally.
No hosted metering, no telemetry, no service dependency. Your repo, your key, your terminal.