# Ouros documentation

Choose the product that owns your task, then follow its first useful workflow. Each product keeps its own navigation and reference; account, privacy and recovery guidance is shared.

## Choose a product

- [Ouros X](/docs/products/ouros-x): a free Mac command bar for finding files and apps, keeping local notes and opening working surfaces.
- [Agent RX](/docs/products/agent-rx): a terminal coding agent; start in the intended project and inspect its tools before submitting work.
- [Mandarin](/docs/products/mandarin): the Ouros code editor with Agent RX built in; open a folder and inspect a file first.
- [Fleet Console](/docs/products/fleet-console): inspect what is keeping your Mac busy and distinguish observed processes from managed services.
- [Termin8](/docs/products/termin8): start with its product overview and quickstart, then use its keyboard and recovery reference.
- [Zilch.sh](/docs/products/zilch): extract a public page into a document. Extraction requires active paid Zilch access.
- [Loop Builder](/docs/products/loop-builder): build explicit workflow steps, inspect agent runs and improve the draft from checked results.

## Finish one first task

Choose one result you can check rather than configuring every product at once.

- [Open an app with Ouros X](/docs/getting-started/first-minute), then return to your previous work.
- [Save a Markdown note](/docs/getting-started/fast-notes), then reveal the saved file.
- [Open Agent RX in a project](/docs/agent-rx/quickstart) and inspect its workspace and commands.
- [Open a folder in Mandarin](/docs/mandarin/quickstart) and read the intended file.
- [Inspect your Mac with Fleet Console](/docs/fleet-console/quickstart) before taking a management action.
- [Start with Termin8](/docs/termin8/quickstart) and check the result described in its guide.
- [Extract a public page with Zilch.sh](/docs/zilch/quickstart) and inspect the completed document.
- [Create a loop on the canvas](/docs/loop-builder/quickstart) without mistaking a saved plan for executed work.
- [Save a durable rule in Policy Hub](/docs/shared/write-and-review-rules), then verify its device version and intended consumer.

## Keep the product context

After opening a product overview, use that product's sidebar for related tasks and reference. Check the product context when searching: a similarly named feature in another product may have different permissions, inputs and results.

Quickstarts end at one first result. Guides cover a specific task; concepts explain boundaries; reference pages define controls and states. Troubleshooting starts with the symptom and preserves your work. [Website changes](/docs/changelog) and [Mac version guidance](/docs/ouros-x/compatibility) have different release scopes.

## Shared help and deliberate handoffs

- [Account and access](/docs/shared/account): distinguish sign-in, native approval, paid product access and provider credentials.
- [Privacy and permissions](/docs/shared/privacy): check local files, hosted processing and action-specific permissions.
- [Get help](/docs/shared/support): preserve drafts and collect useful details without secrets.
- [Using products together](/docs/workflows): review output before copying it into another tool.

A common account or reader does not imply automatic file synchronization, shared credentials or permission to execute another product's output.

For documentation authors, [GitHub's article content model](https://docs.github.com/en/contributing/style-guide-and-content-model/contents-of-a-github-docs-article) is useful background on prerequisites and procedures; [Vercel's Markdown access guide](https://vercel.com/docs/agent-resources/markdown-access) explains its own machine-readable documentation. Neither changes the product requirements described here.