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: a free Mac command bar for finding files and apps, keeping local notes and opening working surfaces.
• Agent RX: a terminal coding agent; start in the intended project and inspect its tools before submitting work.
• Mandarin: the Ouros code editor with Agent RX built in; open a folder and inspect a file first.
• Fleet Console: inspect what is keeping your Mac busy and distinguish observed processes from managed services.
• Termin8: start with its product overview and quickstart, then use its keyboard and recovery reference.
• Zilch.sh: extract a public page into a document. Extraction requires active paid Zilch access.
• 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, then return to your previous work.
• Save a Markdown note, then reveal the saved file.
• Open Agent RX in a project and inspect its workspace and commands.
• Open a folder in Mandarin and read the intended file.
• Inspect your Mac with Fleet Console before taking a management action.
• Start with Termin8 and check the result described in its guide.
• Extract a public page with Zilch.sh and inspect the completed document.
• Create a loop on the canvas without mistaking a saved plan for executed work.
• Save a durable rule in Policy Hub, 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 and Mac version guidance have different release scopes.

Shared help and deliberate handoffs

• Account and access: distinguish sign-in, native approval, paid product access and provider credentials.
• Privacy and permissions: check local files, hosted processing and action-specific permissions.
• Get help: preserve drafts and collect useful details without secrets.
• Using products together: 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 is useful background on prerequisites and procedures; Vercel's Markdown access guide explains its own machine-readable documentation. Neither changes the product requirements described here.