> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mibyanai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Chat and agents

> Use one conversation to plan work, delegate tasks, and refine the result

Mibyan is organized around a conversation rather than a collection of disconnected forms. You describe the outcome, Atlas interprets the request, and specialist agents help produce the right result.

## The conversation flow

<Steps>
  <Step title="Describe the outcome">Say what you want to achieve, who the work is for, and what format you need.</Step>
  <Step title="Add context">Attach relevant files, mention your market or organization, and share constraints that should shape the result.</Step>
  <Step title="Review activity">Mibyan may show a safe progress summary, planned tasks, sources, and generated files.</Step>
  <Step title="Refine the result">Ask for a focused change instead of repeating the whole request.</Step>
</Steps>

## Choosing an agent

Atlas is the default coordinator. It can route a task toward a specialist style such as presentations, writing, research, strategy, marketing, operations, or data. You can name a preferred direction in your prompt when the choice matters.

Examples:

```text theme={null}
Use a concise executive writing style and prepare a one-page decision memo.
```

```text theme={null}
Create a 10-slide investor deck. Ask me for missing assumptions before drafting.
```

```text theme={null}
Analyze the attached spreadsheet, identify anomalies, and return a short action plan.
```

## Attachments and context

Upload only files you are allowed to use. Mibyan extracts supported text and structured content to help the conversation; extraction quality depends on the source file. Review important numbers, citations, and names before sharing the output.

## Progress and thinking summaries

During a long task, the interface can show planning, tool activity, waiting states, and completion. These are user-safe status summaries, not a transcript of hidden reasoning. A tool approval, when required, explains the action and its impact before it runs.

## Better follow-up requests

* "Keep the structure, but shorten the executive summary to 120 words."
* "Add a risks table with probability, impact, mitigation, and owner."
* "Use Modern Standard Arabic and keep product names in English."
* "Turn the current document into a 12-slide presentation for a board meeting."