> For the complete documentation index, see [llms.txt](https://mile-hi-labs.gitbook.io/react-session/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mile-hi-labs.gitbook.io/react-session/master.md).

# Welcome

## Overview

React Session is a session management library for React applications. The library is built on local-storage and designed to work with [React Data](https://github.com/mile-hi-labs/react-data).

## Why React Session

Most applications needs a fast and efficient way to authenticate users and persist that data across browser sessions. Rather than authoring a new (but very similar strategy) across every application, React Session takes care of the heavy lifting for you offering authentication, local storage, and integration with React Data.

## How it Works

React Session uses the [Context Hook](https://reactjs.org/docs/context.html) API to provide a global session where you can authenticate and persist the current user across multiple browser windows or sessions. Once authenticated, React-Session will automatically add your JWT token to API requests sent via React Data. 

To learn more about React Data, visit the [API Documentation](https://app.gitbook.com/@mile-hi-labs/s/react-session/).

{% content-ref url="/pages/-MQDTuuHBvKUlioiTLCv" %}
[Quick Start](/react-session/quick-start.md)
{% endcontent-ref %}


---

# 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 current page URL with the `ask` query parameter:

```
GET https://mile-hi-labs.gitbook.io/react-session/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.