# Platform Specifics and State

**Linux Setup with Systemd**

For Linux users who want Clawd Bot to run continuously in the background as a system service, a systemd unit is recommended. By default, systemd may terminate user processes on logout. To prevent this from stopping your agent, you must enable lingering for your user. This command typically requires superuser privileges.

`sudo loginctl enable-linger your_username`

After enabling linger, you can install and enable the systemd service for Clawd Bot to ensure it starts on boot and runs continuously.

**Where Your Data Lives**

Understanding the file structure is crucial for backups and troubleshooting.

* **Configuration:** The primary .env file is in the application's root directory.
* **Credentials:** Secure tokens and session data are stored in \~/.clawd\_bot/credentials/.
* **Memory and Skills:** Your agent's unique personality and custom tools live in your workspace at \~/clawd/.
* **Logs:** Temporary log files for debugging are typically written to /tmp/clawdbot/.

**Updating Your Agent**

If you used the standard or developer setup, updating is straightforward. Navigate to the Clawd Bot directory and pull the latest changes from the main branch.

`git pull`

If dependencies have changed, run the installer again.

`npm install`

Because your personal configuration and workspace are stored outside this directory, your agent's unique traits will be preserved through the update.


---

# Agent Instructions: 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://docs.clawdtoken.xyz/4-setup/platform-specifics-and-state.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.