> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/task-management/linking-sessions-and-tracked-items.md).
# Linking Sessions and Tracked Items
### Session Linking
Session linking is deliberate. Creating or updating an item does not automatically attach every active session. Link the session when the conversation is part of the item's implementation or decision history:
* Ask the agent to create an item and link it to the current session
* Tell the agent to link an existing item while it updates the item's status or fields
* Open the item and choose **Link Existing** to select a session yourself
* Choose **Launch Session** to start a new session from the item
### Navigating Between Items and Sessions
The connection is bidirectional:
* **From an item:** The detail view shows all linked sessions. Click any session to jump back to that conversation.
* **From a session:** The agent sidebar panel shows tracker items linked to the current session. Click any item to open its detail view.
### Linked Tracker Items Sidebar
In agent mode, a dedicated sidebar panel shows all tracker items linked to the current session. This panel updates when the agent or a person adds a link, giving you a live view of the work associated with the conversation.
### Why This Matters
Session and commit linking close the loop between planning and execution. You can start with an idea, track it through a decision, assign it as a task, link it to the AI session that implemented it, and see the commits that shipped it -- all from the item's detail view.
---
# 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.nimbalyst.com/task-management/linking-sessions-and-tracked-items.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.