When Claude Plans Your Route on Mars: NASA Uses AI for Perseverance
4 min read

When Claude Plans Your Route on Mars: NASA Uses AI for Perseverance

686 words

A few days ago I read news that left me thinking for a while. It’s not the first time I’ve heard about AI in space, but it is the first time I’ve read about Claude planning routes on Mars. And the best part: it worked.

NASA has been using Anthropic’s Claude to plan the Perseverance rover’s routes on Mars. Yes, you read that right: a generative language model generating navigation routes for a rover that’s 225 million kilometers away.

The Problem: Planning Routes on Mars is Tedious

To understand why this is interesting, you have to understand the problem. Mars’s surface is treacherous. No one wants to be responsible for getting a billions-of-dollars rover stuck in the sand, as happened to the Spirit rover in 2009.

So Perseverance’s team spends considerable time planning routes. This involves:

  • Consulting orbital Mars images
  • Analyzing terrain to identify hazards
  • Establishing waypoints to guide movement
  • Transmitting data 225 million kilometers
  • Praying nothing was missed

The Solution: Claude as Navigator

JPL researchers decided to let Claude - using its vision capabilities - have its chance. And Claude did what Claude does best: analyzing data and generating structured results.

What Claude did:

  • Analyzed high-resolution orbital images from HiRISE
  • Processed terrain data from digital elevation models
  • Identified critical terrain features: bedrock, outcrops, dangerous rock fields, sand ripples
  • Generated a continuous route with complete waypoints
  • All in Rover Markup Language (RML), which is basically XML

The Interesting Part: Humans in the Loop

Here’s where the story gets good. Because Claude didn’t do it all alone. JPL engineers did exactly what any sensible person would do when programming rovers on other planets: verify everything.

Using a simulator representing a virtual replica of the rover, engineers reviewed more than 500,000 telemetry variables about the rover’s projected position and potential obstacles. And they made corrections.

The best part: when engineers reviewed Claude’s plans, they found only minor changes were needed. The ground-level camera images (which Claude hadn’t seen) gave a clearer view of sand ripples in a narrow corridor, so drivers divided the route more precisely. But beyond that, the route held up well.

The Result: 400 Meters on Mars

On Martian days (sols) 1,707 and 1,709, corresponding to December 8 and 10, 2025, Perseverance executed routes planned by AI instead of humans. The rover traveled about 400 meters based on an AI-generated route.

And it worked. NASA shows an orbital image where you can see the AI-planned route (in magenta) and the actual route (in orange). They’re not exactly identical - the rover’s AutoNav made real-time decisions - but the base route was solid.

Why This Matters

What fascinates me most about this milestone isn’t just the technical feat - which it is - but what it represents:

1. AI in Critical Environments

We’re not talking about generating text for marketing or summarizing documents. We’re talking about navigating a billions-of-dollars rover on Mars. The confidence this requires is enormous.

2. The Approach is Responsible

NASA didn’t give Claude the keys and say “do whatever you want.” There was exhaustive human verification. There was simulation. There was validation. It’s exactly the approach I like: AI amplifying human capabilities, not replacing them.

3. Real Time Savings

According to Anthropic, JPL engineers say Claude can reduce route planning time by half. They don’t specify how long that “half” is, but if you know what it takes to plan space missions, you know any savings is significant.

Personal Reflections

What I like most about this story is that it represents exactly the type of AI application that excites me: AI working on real problems, with responsible human supervision, generating tangible value.

It’s not hype. It’s not “AI will replace NASA engineers.” It’s “AI is helping NASA engineers do their job more efficiently and focus on what matters.”

Claude didn’t replace anyone. Claude did the tedious work of analyzing orbital images and generating waypoints. Humans did what they do best: verify, validate, and make responsible decisions.

References

Comments

Latest Posts

2 min

349 words

A few days ago I came across an article that literally left me with my mouth open. It’s about TinyEMU-Go: a RISC-V emulator written entirely in Go, ported from C using Claude. And the best part: you can run a complete Linux with a single command.

The Command Line That Gave Me Envy

go run github.com/jtolio/tinyemu-go/temubox/example@2c8151233c2d

And boom, you have a complete Linux running. No special permissions, no containers, no weird dependencies. A pure static Go binary.

5 min

945 words

Creating long, well-founded articles has traditionally been a complex task requiring advanced research and writing skills. Recently, researchers from Stanford presented STORM (Synthesis of Topic Outlines through Retrieval and Multi-perspective Question Asking), a revolutionary system that automates the Wikipedia-style article writing process from scratch, and the results are truly impressive.

In this detailed analysis, we’ll explore how STORM is transforming the way we think about AI-assisted writing and why this approach could forever change the way we create informative content.

7 min

1438 words

A few days ago I discovered Agent Lightning, a Microsoft project that I believe marks a before and after in how we think about AI agent orchestration. It’s not just another library; it’s a serious attempt to standardize how we build multi-agent systems.

What is Agent Lightning?

Agent Lightning is a Microsoft framework for orchestrating AI agents. It enables composition, integration, and deployment of multi-agent systems in a modular and scalable way. The premise is simple but powerful: agents should be components that can be combined, connected, and reused.

9 min

1747 words

If you’re using tools like Claude Code, GitHub Copilot Workspace, or similar, you’ve probably noticed there’s technical jargon that goes beyond simply “chatting with AI”. I’m talking about terms like rules, commands, skills, MCP, and hooks.

These concepts are the architecture that makes AI agents truly useful for software development. They’re not just fancy marketing words — each one serves a specific function in how the agent works.

Let’s break them down one by one in a clear way.

4 min

782 words

Lately I’m seeing more and more AI models calling themselves “open source”. Llama, Mistral, Falcon… they all claim to be “open”. But are they really? How open are they actually?

I recently discovered the European Open Source AI Index (OSAI), a European initiative doing excellent work systematically evaluating how open generative AI models really are.

3 min

609 words

Recently, Addy Osmani published an article that gave me much to think about: “Self-Improving Coding Agents”. The idea is simple but powerful: agents that not only execute tasks, but improve their own performance over time.

This isn’t science fiction. It’s happening now, in 2026. And it has profound implications for the future of software development and, by extension, for all professions.

What is a Self-Improving Agent?

A self-improving agent is an AI system with the capacity to: