> 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/my-sessions.md). # My Sessions “My Sessions” is the user’s dashboard for managing all past and ongoing interactions with the Synthetic Darwin platform. * A gallery view of all your tasks, forks, and experiments. * Each card displays: * Task type * Last benchmark score * Cost so far (e.g., GPU credits, $DARWIN usage) * Timestamp of last run * Direct link to its Tree of Life branch * You can tag or group sessions into folders (e.g., “Successful Runs”, “Concept Forks”, “RAG Experiments”). * A wizard generates API keys or webhooks so top-performing models can be deployed into your apps. * Real-time metrics display GPU minutes used, energy-per-token consumed, and validator load. * The ledger tab shows your token balance, prior staking for privacy tasks, and upcoming consumption forecasts. My Sessions allows Darwin users to run full-scale scientific inquiries with traceable lineage, cost accountability, and seamless deployment—all from a single interface. --- # 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/my-sessions.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.