> For the complete documentation index, see [llms.txt](https://docs.darwinslab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darwinslab.ai/ux-tree-of-life-terminal-journal-sessions/terminal.md).
# Terminal
The Terminal offers power users full control over agent creation, task submission, and branching logic.
* A command-line-meets-IDE interface where users input instructions, tasks, or agent constraints.
* Contextual autocomplete surfaces pre-built task types, supported datasets, available evaluator suites, and configuration templates as you type.
* Advanced users can tweak fork-budgets, model temperature, structural mutation rates, or toggle optional modules (e.g., RAG, tool use, memory).
* Before submitting, a real-time diff viewer highlights exactly what will change from the previous run (e.g., prompt mutations, evaluator shift).
* After execution, the task ID appears in the Tree of Life immediately—allowing you to track evolution in real time.
The Terminal is especially suited for researchers, developers, and optimization engineers who want to push Darwin’s evolution mechanics toward novel goals.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.darwinslab.ai/ux-tree-of-life-terminal-journal-sessions/terminal.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
