> 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/the-product-screen-by-screen/ui-overview.md).

# Workspace & UI overview

> Status: The product · Target version 0.1.x ｜ Verify labels against your build

## What you'll learn

How the Planetz desktop app is laid out, so you can find any feature quickly. Every later page in this section zooms into one part of this screen.

***

## Open a workspace first

Planetz works on a workspace — a Git repository you open with **Open workspace**. Planetz keeps its own state in a sidecar beside your project and never writes into your existing tool data at runtime (see [Git integration](/planetz/core-ideas/git-integration.md)). On first open it guides you through a short setup (default **Provider** and **Model**).

## The three regions

The deck has three regions:

1. **Left rail — the views.** A vertical rail switches the primary view. The main views are:

   | View            | What it's for                                                                                              |
   | --------------- | ---------------------------------------------------------------------------------------------------------- |
   | **Task**        | Queue and watch work → [Task deck](/planetz/the-product-screen-by-screen/task-deck.md)                     |
   | **Issue**       | Pull GitHub issues into the queue                                                                          |
   | **Spec Studio** | Author and trace intent → [Spec Studio](/planetz/the-product-screen-by-screen/spec-studio.md)              |
   | **Decisions**   | Review what agents decided → [Decisions](/planetz/the-product-screen-by-screen/decisions.md)               |
   | **Workflows**   | Browse the process catalog → [Workflows](/planetz/the-product-screen-by-screen/workflows.md)               |
   | **Log**         | Execution log → [Logs & summary](/planetz/the-product-screen-by-screen/logs-and-summary.md)                |
   | **Summary**     | Execution summary (outcomes) → [Logs & summary](/planetz/the-product-screen-by-screen/logs-and-summary.md) |
   | **Adapter**     | External agent connections *(Experimental)*                                                                |
2. **Center — the active view.** Whatever the rail selects: the task board, a conversation, Spec Studio, and so on.
3. **Panels — the fleet at a glance.** Dockable panels show **Agents** and **Tasks** alongside your work, with **Add task** to enqueue new work. The header has **Workspace**, **View**, **Panels**, and **Reset layout** controls, plus **Settings**.

## The optional companion

If you have the **Manta** desktop robot, it mirrors the same fleet state (working / waiting / approve / error) as ambient light and an LCD, with physical Approve / Deny. Planetz works fully on screen without it. See [Edge AI & data sovereignty](/planetz/core-ideas/edge-ai.md).

## Next

* [Task deck](/planetz/the-product-screen-by-screen/task-deck.md) — the view you'll spend the most time in.
* [Overview & mental model](/planetz/core-ideas/overview.md) — how these views map to the underlying loop.


---

# 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/the-product-screen-by-screen/ui-overview.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.