# How the Peptype Works

#### Peptype is a browser-based game where your everyday keyboard activity.

The core idea is simple: you keep using your computer as usual, and Peptype turns that activity into progress inside the game. Instead of separating gameplay from your daily routine, Peptype connects them and makes regular typing part of your growth, rewards, and long-term progression.

***

#### The Core Mechanic

Peptype works through activity-based gameplay.

When the extension is active, the system detects keyboard activity and uses it as a gameplay signal. This activity helps generate progress and supports core game mechanics such as energy collection and character development.

> Peptype does not read or store what you type. It does not collect text content, messages, passwords, or other personal keyboard input. The system only recognizes the fact that keyboard activity happened, without using the content itself.

***

**As browsing continues, the Pep reacts to activity such as:**

* typing
* general page interaction

These activity signals are counted and used for game progression.

***

#### Interaction Detection and Privacy

**Key principles:**

* keystrokes are not recorded
* text input is not read or stored
* form data, messages, and browsing content are not collected

> **Only abstract interaction events are counted and used to power gameplay mechanics like progression and passive actions.**

***


---

# 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://peptype.gitbook.io/peptype/features/how-the-peptype-works.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.
