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

# v.2.0

{% hint style="info" %}
To get the new version ✨
{% endhint %}

```bash
pip install shimoku
```

With this version we have changed the responsibilities of the different modules that compose the SDK as well as added a new module, the **Command Line Interface(CLI)**! This means that some functionalities have shifted location, make sure to check the changes in the documentation.

## Improvements

* The name of the package has been changed from `shimoku-api-python` to `shimoku`.

  This will be reflected in the new scripts as the users will no longer be importing the former package name, the recommended new way to import it is:

  ```
  from shimoku import Client
  ```

* The inner workings of the SDK have been separated further in order to respect the responsibilities of each module.
  * The playground no longer gets initialized automatically, it needs the user to use the new CLI command.
  * The code generation functionalities are no longer accessible from the client object, the user needs to use the commands provided in the persist module from the CLI.

* A CLI has been added to ensure full access to the functionalities of the SDK.

Changes in the documentation can be seen here:

{% content-ref url="/spaces/UlHTfmIZY46Z1EDfyGMz/pages/kWqjcPn5pVWb60OTvvDd" %}
[Installation & Setup](/dev/quickstart/installation-and-setup.md)
{% endcontent-ref %}

{% content-ref url="/spaces/UlHTfmIZY46Z1EDfyGMz/pages/H1NPb0FobqGZDIBB2GNi" %}
[Shimoku Cloud](/dev/cloud-and-community/shimoku-cloud.md)
{% endcontent-ref %}

{% content-ref url="/spaces/UlHTfmIZY46Z1EDfyGMz/pages/jPdRBaxSPxL5CBkBAQZE" %}
[CLI](/dev/advanced-usage/cli.md)
{% endcontent-ref %}

{% content-ref url="/spaces/UlHTfmIZY46Z1EDfyGMz/pages/iaTeIDWCG5Z0RDKoMJ2A" %}
[Menu](/dev/building-web-app/menu.md)
{% endcontent-ref %}

{% content-ref url="/spaces/UlHTfmIZY46Z1EDfyGMz/pages/o0dSRZMnTG7yUSvMThUt" %}
[Colors Usage](/dev/building-web-app/theming/colors-usage.md)
{% endcontent-ref %}

{% content-ref url="/spaces/UlHTfmIZY46Z1EDfyGMz/pages/vaW7U2OsgPwXiD17J0sK" %}
[History navigation & Breadcrumb](/dev/elements/features-and-navigation/history-navigation-and-breadcrumb.md)
{% endcontent-ref %}

{% content-ref url="/spaces/UlHTfmIZY46Z1EDfyGMz/pages/XSuOprNYI0B4g8BBEc31" %}
[Code Generation](/dev/advanced-usage/code-generation.md)
{% endcontent-ref %}


---

# 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.shimoku.com/dev/releases/2024/v.2.0.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.