> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/release-notes/q1-2026/january-26-2026.md).
# January 26, 2026
**Agents**
Introducing HockeyStack Agents — AI-powered automation that works for you. Choose from our list of 14 out of the box agents from the pre-built templates or build custom agents to automate research, outreach, and workflows. More information [here](https://docs.hockeystack.com/documentation/hockeystack-agents).
**Timezone Standardization**
Set a workspace-level timezone to ensure consistent date handling across your entire team. All reports, dashboards, and scheduled prompts now respect your configured timezone — no more confusion when team members are in different locations. A new timezone indicator shows your current setting throughout the app.
**6sense Integration for Scoring**
6sense data is now included in Companies scoring, giving you richer account intelligence signals for more accurate predictions.
***
Made with ❤️ by the HockeyStack team. For any demo or any questions, please contact your HockeyStack Customer Success Manager!
---
# 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.hockeystack.com/release-notes/q1-2026/january-26-2026.md?ask=&goal=
```
`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.