> For the complete documentation index, see [llms.txt](https://planetz.gitbook.io/planetz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://planetz.gitbook.io/planetz/where-planetz-is-going/whats-next.md).

# What's next

> Status: Roadmap — forward-looking · Target version 0.1.x

## What you'll learn

Where Planetz is headed. This page is **deliberately forward-looking**: some items ship today, others are in progress or planned. We mark which is which rather than describe a finished product.

***

## The throughline

Planetz's bet is that as agents get more autonomous, the scarce thing isn't code — it's **staying in control of what the agents are building and understanding it.** Everything on this roadmap serves that: more autonomy, paired with more comprehension and governance.

## Manta — the desktop robot

> **Status: reference hardware, reserve / waitlist.**

A palm-rest companion device that takes control off your monitor: a status **LCD** and **ambient light** for each agent's state, physical **Approve / Deny** buttons for the deliberate confirmations, and **hold-to-talk** to turn speech into an agent's next instruction. Connects over **USB-C / BLE**, with an open device-protocol roadmap. Planetz works fully without it; Manta makes control calmer and more physical.

## Planetz Cloud

> **Status: planned / waitlist.**

A managed private node you drive from the browser, with the **same deck UX and workflows** as the desktop app. Start locally on edge models, then move workspaces to Cloud for more power — without relearning the product — and add **team sharing and audit logs**. The local Deck and Cloud are designed to be two ends of one spectrum, not two products.

## More autonomy, in safe steps

The roadmap moves runs up an **autonomy ladder** — from *report-only*, to *propose changes for human merge*, to *run unattended within safe bounds* — where each step up is earned by measured reliability, not flipped on by hope. Stop conditions, approval gates, and the [intent ledger](/planetz/core-ideas/intent-ledger.md) remain the controls underneath.

## Processes that improve themselves

> **Status: direction, not yet shipped.**

Today, workflows and **facets** (reusable persona / policy / knowledge blocks) are authored by you. The direction is for these *processes* to grow into durable team assets — and for a librarian-style helper to keep them from rotting (retiring unused ones, merging duplicates). The honest framing: the value isn't "the AI magically self-improves," it's **"the assets you build don't decay."**

## The Comprehension Dashboard

> **Status: planned — the differentiator we care most about.**

The biggest risk of autonomous agents is **comprehension debt**: code ships faster than anyone understands it, until no one can safely change it. The planned dashboard makes that debt *measurable* — signals like revert rate, generated-vs-reviewed pace, and a weekly digest — so you can see whether your team still understands its own system, not just whether the agents are busy.

## What this is *not*

We won't claim Planetz prevents every mistake, or that smarter models make governance unnecessary. The opposite: the smarter agents get, the more they decide silently — so the value of keeping intent, decisions, and comprehension under your control only grows.

## Next

* [The standard workflow](/planetz/the-standard-workflow/standard-workflow.md) — the loop these features extend.
* [Why Planetz is different](/planetz/why-planetz/how-planetz-is-different.md) — the thesis behind the roadmap.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://planetz.gitbook.io/planetz/where-planetz-is-going/whats-next.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.