> For the complete documentation index, see [llms.txt](https://yvechat.gitbook.io/wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yvechat.gitbook.io/wp/getting-started/pair-your-browser.md).
# Pair Your Browser
Pairing tells YveChat Engine that one specific website is allowed to use it. You approve that connection yourself, on your own machine, once.
Have YveChat Engine running before you start.
The pairing flow, and the browser constraints that make it necessary
***
### Why this step exists
The hosted interface is a static browser application. Browsers restrict pages on the public internet from reaching software on your local machine, which is a protection worth having. Pairing is how you grant that access deliberately, to one origin, on your terms.
***
### The steps
#### 1. Open the hosted workspace
Go to `https://app.yvechat.xyz`.
The workspace loads and reports that YveChat Engine is not yet connected.
#### 2. Allow local-network access
Your browser asks whether this site may connect to devices on your local network. Approve the request.
Chrome describes this permission as looking for and connecting to devices on your local network, and it gates connections from public sites to loopback addresses.
Source: [Chrome Local Network Access](https://developer.chrome.com/blog/local-network-access)
Declining the request leaves the workspace unable to reach YveChat Engine. See [Troubleshooting](/wp/getting-started/troubleshooting.md) if you declined and want to reverse it.
#### 3. Open the local approval page
The workspace shows the loopback address for YveChat Engine and a six-digit code. Open that address in a new browser tab.
This page is served by YveChat Engine from your own computer.
#### 4. Sign in locally
Sign in on the approval page using your local account, or with wallet authentication if you prefer. Wallet authentication is optional, and a wallet signature creates or identifies a profile held locally.
Signing in sets a secure local session cookie, which is what authenticates you on the local page.
#### 5. Verify the displayed origin
The approval page displays the origin requesting access. Read it before continuing.
It should read exactly `https://app.yvechat.xyz`.
{% hint style="danger" %}
Check this character by character. A pairing token grants a website the ability to use your models, your conversations, and your machine. An origin that differs in any way, including by a single character, a hyphen, or a different ending such as `.com`, belongs to someone else. Cancel if it does not match, and check [Verified Links](/wp/resources/verified-links.md).
{% endhint %}
#### 6. Enter the six-digit code
Type the six digits shown in the hosted workspace into the approval page, then approve.
The code proves the two tabs belong to the same person. Codes expire after a short period, and an expired code is replaced by requesting a new one from the workspace.
#### 7. Return to the hosted workspace
Go back to the `app.yvechat.xyz` tab.
It now reports a connection to YveChat Engine, and your installed models appear in the model selector.
***
### What pairing creates
| Property | Behavior |
| -------------- | -------------------------------------------------------------- |
| Origin binding | The token works for the approved origin alone |
| Local storage | The token is stored as a hash on your machine |
| Expiry | Tokens expire |
| Revocation | You can revoke a paired origin at any time from YveChat Engine |
Revoking a pairing ends that site's access immediately. Pairing again repeats the steps above.
***
### Next
Continue to [First Conversation](/wp/getting-started/first-conversation.md).
---
# 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, and the optional `goal` query parameter:
```
GET https://yvechat.gitbook.io/wp/getting-started/pair-your-browser.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.