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

# Threads — Chat with Ana

> TextQL's agentic data platform, built for enterprise data scale and security.

## What is Ana?

Ana is TextQL's AI agent — think of her like a data analyst you just hired. She writes SQL, runs Python, searches the web, and produces charts, reports, CSVs, PDFs, and Markdown files, all through natural language conversation.

<Frame>
  <video autoPlay muted loop playsInline>
    <source src="https://cdn-docs.textql.com/threads_demo.mp4" type="video/mp4" />
  </video>
</Frame>

<Card title="Try your first chat!" icon="message" href="/core/get-started/your-first-chat">
  Get started with Ana in a few minutes.
</Card>

## What Ana can do

Ana is equipped with a set of [tools](/core/how-it-works/tools) she uses to answer questions and complete tasks. Each tool handles a different part of the analysis workflow.

<CardGroup cols={2}>
  <Card title="Text-to-SQL" icon="database" href="/core/how-it-works/tools/text-to-sql">
    Writes and runs SQL against your connected data warehouses and databases — no query knowledge required.
  </Card>

  <Card title="Python" icon="python" href="/core/how-it-works/tools/python">
    Runs Python for data transformations, statistical analysis, chart generation, and file exports.
  </Card>

  <Card title="Web Search" icon="magnifying-glass" href="/core/how-it-works/tools/web-search">
    Searches the web to enrich analysis with real-time external data, market context, or public benchmarks.
  </Card>

  <Card title="Ontology" icon="diagram-project" href="/core/how-it-works/tools/ontology">
    Queries against a governed metrics layer for teams that need consistent, enforced definitions.
  </Card>
</CardGroup>

## What Ana produces

Ana outputs results in a range of formats depending on what you ask for.

* **Charts and visualizations** — bar, line, scatter, and custom plots generated inline in the thread
* **Interactive dashboards** — reusable, shareable views built directly from your data. See [Dashboards](/core/how-it-works/dashboards).
* **Scheduled reports** — automated analyses delivered to Slack or email on a set schedule. See [Playbooks](/core/how-it-works/playbooks).
* **Downloadable files** — CSVs, PDFs, PPTs, and Markdown files Ana can produce and attach to any thread
* **Interactive HTML reports** — fully custom, browser-renderable reports. See [Interactive HTML Reports](/core/guides/interactive-html-reports).

When an artifact is open in the side panel, its ID is encoded in the URL. You can copy and share that URL to send a colleague directly to the same artifact view.

## Steering mid-run

You don't have to wait for Ana to finish before adjusting course. Send a message while a run is in progress and it steers the active run right away, rather than waiting in the queue for a separate turn — useful for narrowing scope, correcting an assumption, or redirecting before Ana goes too far down a path.

Steering is controlled by a per-user toggle in **Settings → Personal** and only applies to models that support it (currently Opus 4.8 and GPT-5.5). On other models, a message sent mid-run is queued and handled as the next turn.

## Connecting your data

Ana works with whatever data sources your organization uses. Connect a warehouse, database, BI tool, or API and Ana is ready to query immediately — no data modeling required.

<Card title="Connect your data" icon="plug" href="/core/get-started/connect-your-data">
  Set up your first connector in minutes.
</Card>

Supported sources include Snowflake, BigQuery, Redshift, Databricks, Tableau, PowerBI, REST APIs, and more. See the full list on the [Connectors page](/core/datasources/the-connectors-page).

## Guiding Ana with context

Ana gets smarter when you tell her about your business. The [Ontology](/core/ontology/overview) lets you store metric definitions, table preferences, and business logic that apply automatically to every query — so you don't have to re-explain things in each thread.

For teams with stricter data governance needs, the [Ontology](/core/ontology/overview) layer lets you define exactly which tables and fields Ana can access and how metrics should be calculated.

## Delivering results

Ana can deliver results beyond the chat interface:

* **[Slack](/core/integrations/slack)** — tag Ana in any channel for on-demand analysis, or receive scheduled playbook reports directly in a thread
* **Email** — configure [Playbooks](/core/how-it-works/playbooks) to send reports to any recipient on a schedule
* **Embed** — surface Ana directly inside your own product. See [Embedding Ana](/core/guides/embedding-ana).