METAL LAB

Claude codes moon navigation app using NASA lunar terrain data

Built entirely in the browser without external libraries, the app calculates routes that avoid craters

Summary

  • Claude coded a lunar surface navigation app from scratch in the browser, with no external libraries
  • It uses NASA's LOLA altimeter and LROC mosaic data to calculate routes that avoid or cross craters
  • Each route comes with an explanation of why it turned the way it did
Claude codes turn-by-turn directions for the Moon

Anthropic's AI model Claude has coded a full navigation app that runs across the lunar surface, and the demo is now up on YouTube. Working from real NASA terrain data, Claude worked out routes on its own that steer around steep craters while cutting straight through gentler ones, explaining the reasoning behind every turn along the way.

NASA's accumulated observation data flows toward Claude via dotted arrows, and Claude interprets it to build the navigation app screen, shown with solid arrows. On that solid line sits a gate marked by a dotted circle, containing a solid-filled circle labeled "human review, verify decision logic," showing that a person must check the AI's judgment before it gets used as-is.NASA's accumulated observation data flows toward Claude via dotted arrows, and Claude interprets it to build the navigation app screen, shown with solid arrows. On that solid line sits a gate marked by a dotted circle, containing a solid-filled circle labeled "human review, verify decision logic," showing that a person must check the AI's judgment before it gets used as-is.

Anthropic official website

The demo video is meant to showcase coding ability, highlighting that Claude built both the browser-based 3D moon globe and the route-guidance feature entirely from scratch.

What was built

Every number that shows up on screen traces back to public data that Claude pulled in on its own. The terrain and crater-depth figures come from LOLA, a laser altimeter carried aboard the Lunar Reconnaissance Orbiter (LRO), while the surface imagery comes from a global mosaic captured by the same orbiter's LROC camera. Both datasets reportedly came from NASA's public database, the Planetary Data System (PDS).

To put it simply: LOLA is a laser altimeter that measures the height and depth of the lunar surface, and LROC is the camera that photographs that same surface. Both instruments ride aboard a NASA orbiter circling the moon, and the data they collect ends up in PDS, a public repository anyone can download from.

Deciding when to avoid a crater and when to cross it

Based on the terrain data, the app calculates routes that go around craters too steep to enter and cut straight across ones gentle enough to cross. Each route also comes with an explanation of why it turned in a given direction — meaning the app isn't just finding the shortest path, it's factoring in the steepness of the terrain itself.

Drawing a map in the browser, no library required

This 3D moon globe was built entirely inside the browser without relying on any separate graphics library. That means every line of code for drawing the map, rotating it, and plotting routes was written by Claude from the ground up — a case study in just how much complexity an AI coding agent can handle on its own.

Claude is Anthropic's conversational AI, widely used not just for reading and writing long documents but for coding as well. This video isn't a real product launch so much as a demonstration of how sophisticated a 3D interface and route-calculation logic can get when built purely from public data.

Like the case of an ASCII city you can walk through, built with no game engine and packed into a single HTML file, a string of recent demos have shown complex results built with nothing but a browser and no outside tools.

Editor's view

What makes this demo interesting isn't the polish of the output — it's the approach. Instead of borrowing a commercial mapping library or a 3D engine, Claude read raw observational data published by NASA directly, reconstructed the terrain from it, and set its own routing rules. It's a sign of where coding agents are headed: from patching existing code toward looking at raw data and designing new algorithms from the ground up.

Anyone who's put this kind of coding agent to work in practice tends to arrive at the same conclusion. Tasks with well-structured API documentation get handled quickly, but work like this — where the agent has to interpret raw data on its own and set the criteria for judgment calls (like whether a crater is passable) — takes far longer to verify. Teams here looking to apply a similar demo would do well to start with prototypes built on public datasets, and build in a step where a human reviews any decision logic that touches on safety.

There's a good chance similar from-scratch demos spread to other domains — weather, navigation, architecture — within weeks. As long as the underlying data is public, this video makes the point that the range of what coding agents can build keeps expanding.

Comments