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

# January 6, 2026

## What's New:

### Credits Purchase

You can now separately purchase AI credits.

<figure><img src="/files/aZqq2NifLW0900SC2vOx" alt=""><figcaption></figcaption></figure>

***

## Improvements & Fixes:

* Updated the styling for join app cards.
* Fixed an issue where kits are not accessible.
* Fixed an issue where public agents sometimes confuse the current datetime.
* Fixed an issue where breadcrumbs were not showing correctly for /starred pages.
* \[Mobile] Improved mobile-friendliness of /calendar page.
* \[Mobile] Improved mobile-friendliness of the quick add modal.
* \[Mobile] Improved mobile-friendliness of breadcrumbs.
* \[Mobile] Improved mobile-friendliness of the EVE chat panel.
* \[Mobile] Fixed an issue where the navigation panel could not be open.
* \[Mobile] Fixed an issue where automations could not be renamed.


---

# 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.taskade.com/changelog/changelog-2026/january-2026/january-6-2026.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.