lantern
Health Warn
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 9 GitHub stars
Code Pass
- Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
- Permissions — No dangerous permissions requested
No AI report is available for this listing yet.
Your project is the whole context for your AI. Lantern maps it, helps you plan changes, reviews pull requests with generated flows, and keeps your AI assistant sessions together.
Lantern
Your project, your codebase, is the whole context for your AI.
Manage that context well. Lantern will help you with that.
Lantern maps your project, helps you plan changes, reviews pull requests with generated flows and local review, and keeps your AI assistant sessions across your harness together in one desktop app.
What it does
- Watches every session across your harness and shows a live dashboard of
each one: its project, state, and last reply. - Notifies you in the menu bar and with native notifications when a session finishes,
needs approval, or is waiting for input, so you don't babysit a window. - Maps your project into a
.lantern/folder (one record per file, its role, its purpose and
its relations) and draws it as a graph, so you can see the structure without reading the code. - Reviews pull requests and local changes with a file list, diffs and the graph, in review
order, with a reason for each changed file. - Local review: review your uncommitted changes, or a branch with no pull request, with the
same file list, diffs and graph as a pull request (+ Compare in the Lantern tab, orlantern --compare). One click asks Claude for a one-sentence reason per changed file. - Generate with Claude or Codex: choose the assistant used by Lantern's maps
and repairs for each project. This setting does not change the assistant inside the embedded
editor. Pick the output language per project and repair broken output in place.
Sessions are told apart by their working directory: one entry per VS Code project window.
Documentation
The documentation is at https://docs.thelantern.dev and in docs/:
- Installation and command line
- Data and privacy: what Lantern stores, how to remove it, and what leaves your machine
- Getting started
- Architecture
- Product overview: thelantern.dev
Development and checks
The checks CI runs on every push and pull request (.github/workflows/ci.yml, a plain Linux
runner with Node 22, pnpm 10.28.0 and pnpm install --frozen-lockfile) are:
pnpm run typecheck
pnpm run lint # biome lint --diagnostic-level=error
pnpm test
CI never launches Electron, runs the Playwright e2e or signs anything. The stack, the project
layout, the code and testing conventions and the build pipeline are in
CONTRIBUTING.md; a map of the source is in docs/architecture.md.
More
- CONTRIBUTING.md: how to work on the app, test it and build it.
- SECURITY.md: how to report a vulnerability.
- CODE_OF_CONDUCT.md: how we expect people to behave in this project.
- TROUBLESHOOTING.md: known problems and their fixes.
- THIRD_PARTY_NOTICES.md: licences of the software Lantern ships.
License
Lantern is released under the MIT License. Copyright (c) 2026 Mobile Reality. See LICENSE.
Contact: [email protected].
Lantern is not affiliated with or endorsed by Anthropic, OpenAI, Microsoft, Atlassian or GitHub; their names and marks are trademarks of their owners.
Made with <love> by People with AI
By Mobile Reality
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found