> For the complete documentation index, see [llms.txt](https://leather.gitbook.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leather.gitbook.io/guides/stacking/desktop-vs.-extension.md).

# Desktop vs. extension

Leather for Desktop has the same functionality before and after the launch of Stacks 2.1 and POX2.

Whereas the Stacking Dapp, that can be used in conjunction with the Wallet extension will get the options to take advantages of the features added in Proof of Transfer 2 (PoX2). Namely: topping off when stacking on your own `stackIncrease`, and extending the duration `stackExtend` (without the need for a cooldown cycle as was the case in PoX1).

When pooling there are similar improvements for the pool operator so that they can extend the duration without requiring cooldown cycles. When stacking in a pool you will not see these changes, they remain in the background with the pool operators (i.e. Friedger, Planbetter and Xverse) handling the relevant contract calls for you.


---

# 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://leather.gitbook.io/guides/stacking/desktop-vs.-extension.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.