Newshot

Show HN: Lantern – desktop app that maps your repo and reviews AI-written PRs

Original text(via HN AI)

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.

Website · Documentation

License
License
Latest release
Latest release

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, or lantern --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.

A short tour (mp4, 70 s). The screenshots show a synthetic demo project.

A short tour: the map, a plan lit on it, a pull request opened from the plan, its flow and a diff review
A short tour: the map, a plan lit on it, a pull request opened from the plan, its flow and a diff review

The map of a project

Every file with its role, purpose and relations, drawn as a graph. The changed files of a pull request are lit in it.

The map of a project with the files of pull request #77 highlighted
The map of a project with the files of pull request #77 highlighted

The macro view folds the same map into one card per area, with the systems the code talks to.

The macro view: one card per area, the shared foundation and the outside systems
The macro view: one card per area, the shared foundation and the outside systems

Planning a change

A plan is a file under .lantern/plans/, written against the map and approved section by section. Lantern shows its goal, scope, stages, open questions and the progress of every item, which comes from the pull requests that tick it. Pick a stage and the areas, features and files it changes are marked on the map; open a pull request from an item to review it.

A plan with the stage s2 selected: the areas it changes are marked on the macro view
A plan with the stage s2 selected: the areas it changes are marked on the macro view

Reviewing a pull request

A flow in plain words says who does what and what changed, with the files that carry each step.

A pull request flow: who does what, and what changed in each step
A pull request flow: who does what, and what changed in each step

Then the diffs, in review order, each with the reason the file changed and its place in the graph. With the flow on, the step the file belongs to is lit next to the code.

A diff next to its reason and the flow, with the step the file carries highlighted
A diff next to its reason and the flow, with the step the file carries highlighted
A diff next to its reason, the changed-file list and the graph
A diff next to its reason, the changed-file list and the graph

Download

Packages are attached to each release on the releases page: Lantern-mac.zip for Apple-silicon Macs, Lantern-win-x64.zip for Windows and Lantern-linux-x64.zip for 64-bit Linux (Linux packages are x64 only). The Apple-silicon build is also published as Lantern-mac-arm64.zip for the updater, and the Lantern-mac.zip link stays the one to use. Until a release is published there, build Lantern from source (installation).

The macOS app of a release built by the current workflow is signed with a Developer ID certificate and notarized by Apple, so macOS only asks once to confirm opening it. Earlier releases are signed ad hoc and need the steps in CONTRIBUTING.md. The Windows build is not code-signed, so SmartScreen may warn on first launch.

Verify the download: every release carries a SHA256SUMS file. Put it next to the zips you downloaded and run sha256sum -c SHA256SUMS --ignore-missing on Linux or shasum -a 256 -c SHA256SUMS --ignore-missing on macOS; each zip should print OK.

The Linux build is x64 only and unsigned. Extract it, make the binary executable and run it:


        unzip Lantern-linux-x64.zip
cd Lantern-linux-x64
chmod +x Lantern
./Lantern
      

Chromium's sandbox needs unprivileged user namespaces or a setuid helper. Ubuntu 24.04 and newer restrict user namespaces, so on such a system the app can exit at start with "The SUID sandbox helper binary was found, but is not configured correctly". Fix it once with sudo chown root:root chrome-sandbox && sudo chmod 4755 chrome-sandbox in the extracted folder, or start the app with ./Lantern --no-sandbox, which switches the sandbox off for that run. The Linux build is new: CI builds it on Ubuntu but never runs it, and the memory view still says "Not supported yet" there.

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 runs the unit tests, builds on Linux, macOS and Windows, runs the Playwright e2e for integrations, the tray, pull request host state and skills (the graph suite is not run in CI), and publishes a coverage report as a build artifact. It signs nothing. 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

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by HN AI
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗