> For the complete documentation index, see [llms.txt](https://docs.vibetrading.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vibetrading.dev/resources/changelog.md).

# Changelog

## 2026/03/24

* **Removed** `vibetrading.evolution` module (`StrategyEvolver`, `evolve()`, `EvolutionStep`, `EvolutionResult`) — the project now focuses on generate → backtest → analyze workflows. Users can iterate manually using `vibetrading.strategy.generate()` and `vibetrading.strategy.analyze()`.

## 2026/02/26

* Added LLM-powered backtest analysis (`vibetrading.strategy.analyze()`): scores performance (1-10), identifies strengths/weaknesses, and suggests actionable improvements.
* ~~Added strategy evolution (`vibetrading.evolve()`): iteratively improves strategies through generate → backtest → analyze → regenerate feedback loops.~~ *(removed in v0.4.0)*
* ~~New modules: `vibetrading.evolution` (StrategyEvolver, evolve), `vibetrading.strategy.BacktestAnalyzer`.~~ *(removed in v0.4.0)*
* Added `vibetrading.strategy.generate()` convenience function for one-call generation.
* Updated documentation: new pages for Backtest Analysis, updated Quick Start, API Reference, and Configuration.

## 2025/11/01

* Added Live Agent Edit feature.
* Improved live agent reports.

## 2025/10/23

* Added Live Agent Report feature.

## 2025/10/17

* Improved grid strategies.

## 2025/10/15

* Added Live Agent Chat feature.

## 2025/10/08

* Supported lighter and extended agent, fixed bugs in backtest.

## 2025/09/27

* Released agent showcase page and clone feature.

## 2025/09/23

* Improved Grid Strategies: better managed liquidations; VibeAgent inferred grid center from external data source.
* Backtest: fixed limit order one-side position issue.

## 2025/09/21

* Improved Grid Strategies: added intelligent limit order and position management.
* Backtest now supported simulating limit order and price matching.
* Improved backtest data ingestion and stability.

## 2025/09/15

* Live trade supported limit order and added set\_leverage/reduce\_position function.
* Added coin overview and market data analytics tool for IDE.

## 2025/09/12

* Improved VibeAgent’s strategy code generation.

## 2025/09/10

* Fixed streaming issue in backtesting.
* Added version selection feature in IDE.
* Upgraded VibeAgent architecture to support planning and complex external data.
* Supported external data source (defillama, search).

## 2025/09/05

* Added total transaction fees in backtest.
* Sped up page loading.
* Improved UI.

## 2025/08/31

* Added Paper trading feature, now available for risk-free practice.

## 2025/08/30

* Upgraded VibeAgent with improved intention tracking.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vibetrading.dev/resources/changelog.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.