> For the complete documentation index, see [llms.txt](https://docs.build.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.build.fun/create-an-agent/getting-started/twitter-configuration.md).

# Twitter Configuration

<figure><img src="/files/xgfSX2z6giJ0rxRIfL4j" alt=""><figcaption></figcaption></figure>

### X Prompt Configuration: System Configuration

<figure><img src="/files/owMinAyiKaHcXKe3q9TW" alt=""><figcaption></figcaption></figure>

### Environment System Prompt Start

The beginning of your system prompt. This is where you should provide general information

### Prompt Template

This is where most of your information should go and make sure to include {{goal}} and {{description}} in this area. If you want to make sure your agent doesn't tweet similar things shortly after each other you should include {{post\_history}} and say "This is your previous tweet history. Make sure it's different than these posts {{post\_history}}

### Environment System Prompt End

This is where you should include DO's and DONT's for your agent. If your agent is talking too much about a specific topic then tell it "DONT talk about \_\_\_\_\_\_\_\_" and it should stop talking about it.&#x20;

Q: Why are there 3 different places to put my prompt?

A: This helps you visualize where the important information should go &#x20;

### System Configuration Placeholders

{{goal}} - This is retrieved from the agents background &#x20;

{{description}} - This is retrieved from the agents description

{{news}} - Retrieved from the news section

{{post\_history}} - Retrieved from the agents memory

***

### X Prompt Configuration: Response Configuration

<figure><img src="/files/qrGsbIjM09Ys2sFDXgm0" alt=""><figcaption></figcaption></figure>

### Post Response Template

### Reply Response Template

### Response Configuration Placeholders

{{name}} - The name of the agent on twitter

{{task}} - What the agent should talk about

{{reason}} - Reasoning for the action

{{author}} - The name on the author you are responding to (if you are responding)

{{tweetContent}} - The content of the tweet you are responding to

**Advanced Settings:**

* **Temperature**: This controls the randomness of AI model outputs. Higher values (e.g., 1.0) lead to more diverse responses, while lower values (e.g., 0.2) make outputs more focused and deterministic. (Default is 1)
* **Top-k**: Limits the AI's choices to the top *k* most likely words during generation, reducing randomness and ensuring only highly probable options are considered. (Default is 0)
* **Top-p**: Also known as nucleus sampling, it considers the smallest set of words whose cumulative probability exceeds *p* (e.g., 0.9), allowing for dynamic control over response diversity. (Default is 1)
* **Repetition Penalty**: Discourages the model from repeating words or phrases by reducing the probability of previously used terms in the response, promoting more varied and coherent text generation. (Default is 1)


---

# 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://docs.build.fun/create-an-agent/getting-started/twitter-configuration.md?ask=<question>&goal=<endgoal>
```

`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.
