> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/getting-started/say-hello-to-tellius.md).

# Say Hello to Tellius

New to Tellius? Explore our glossary, navigation tips, and guided tours to get started quickly and confidently.

Welcome to Tellius! 😊 Whether you're opening Tellius for the first time or checking what's changed, this page gets you there fast.

{% hint style="success" %}
**Latest release: Tellius 6.4** · 

**Latest patch: 6.3.2**

Patch 6.3.2 brings read-only conversation sharing with a "Continue this Conversation" option, shareable Vizpad Custom Views, section-level Selective Export, platform-wide Scheduled Jobs management for Super Users, and Mission attribution in Kaiya answers — plus a guided home page tour for new users.

→ [See everything in Patch 6.3.2](https://help.tellius.com/whats-new/release-6.3/patch-6.3.2) 

→ [Explore Release 6.4](https://help.tellius.com/whats-new/release-6.4)
{% endhint %}

### Learn by doing

Guided tours walk you through the platform hands-on, right inside Tellius. Signing in for the first time? A home page tour starts automatically and introduces the essentials.

### Stay current

Every release and patch is documented under [✨ What's New](https://help.tellius.com/whats-new/release-6.3). This page always points to the latest.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.tellius.com/getting-started/say-hello-to-tellius.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.