> For the complete documentation index, see [llms.txt](https://t1t.gitbook.io/t1c-js-guide-v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t1t.gitbook.io/t1c-js-guide-v3/t1c-js-sdk/miscellaneous/installation-faq.md).

# Installation FAQ

## Where can I find the installed files

### Windows

The Trust1Connector API will be located in `%localappdata%/Trust1Connector/`

### MacOS

The API will be located in 

`~/Library/Application Support/Trust1Team/Trust1Connector/`

## Do I need administrator rights for installation

For the Trust1Connector API you do not need any administrator rights.

## How can I manually restart the API?

### Windows

The Windows version of the Trust1Connector can be started with the Launcher executable provided. More information can be found [here](https://t1t.gitbook.io/t1c-api/v3.5.5/launcher)

### MacOS

First unload and stop the services. The first is the API and the second is for card communication;

`launchctl unload ~/Library/LaunchAgents/com.t1t.t1c.api.plist`

Now load the service again which will make it restart

`launchctl load ~/Library/LaunchAgents/com.t1t.t1c.api.plist`

## Where can i find the log files

### Windows

`%localappdata%/Trust1Connector/`

### Macos

`~/Library/Application Support/Trust1Team/Trust1Connector/`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://t1t.gitbook.io/t1c-js-guide-v3/t1c-js-sdk/miscellaneous/installation-faq.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 `automate deployments from our CI pipeline` 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.