> For the complete documentation index, see [llms.txt](https://docs.datasaur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasaur.ai/compatibility-and-updates/release-notes/version-6/6.160.0.md).
# 6.160.0
May 13, 2026
## **What's New? 💡**
### **Data Studio**
* Bounding Box Labeling — Added support for [relationship labeling between bounding boxes](https://docs.datasaur.ai/data-studio-projects/lets-get-labeling/bounding-box-labeling#bounding-box-arrows-relationships).
* Audio Labeling — Added keyboard shortcuts for marking start and end timestamps in the audio to connect them with the transcript, allowing users to create timestamp labels without using the mouse.
## **Bug Fixes 🐞**
### **Data Studio**
* Fixed an issue in Audio Labeling where the span highlight from a timestamp selection remained visible and could not be removed after clicking elsewhere, pressing Escape, or entering edit mode.
---
# 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.datasaur.ai/compatibility-and-updates/release-notes/version-6/6.160.0.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.