> 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/item-detail.md). # Item Detail, Comments, Activity Open a tracker item to edit fields in place, write the body, add comments, and follow the full activity history of a piece of work. The detail view is where you work on a single tracker item: edit its fields in place, discuss it in comments, review its history, and launch or link the AI sessions that carry it forward. Click any item in the kanban board or list view to open it.

A task selected on the kanban board with its detail panel open on the right, showing status, priority, owner, content location, and a Sessions section — The detail panel for a task: status, priority, and owner dropdowns, the item's content location, and the Sessions section with Launch Session.

### Editable Fields * **Title**: Click the title text to edit it inline. * **Status**: Dropdown with all valid statuses for the item's type. * **Priority**: Dropdown (Critical, High, Medium, Low). * **Owner**: User picker to assign responsibility. * **Description**: Text area for detailed notes and context. * **Tags**: Add or remove categorization tags. * **Due Date**: Date picker for deadlines. * **Progress**: Percentage slider, available on Plan items only. Fields vary by item type. For example, Release items include Version, Git Tag, Channel, and Released At, while Idea items keep a smaller set of fields for early-stage work. See [Item Types and Fields](/task-management/item-types-and-fields.md). ### Comments Add comments to discuss an item without changing its fields. Each comment shows the author and timestamp.

The item detail panel where fields, comments, and activity live — Comments and activity live in the same detail panel as the item's fields.

Comments are useful for team discussions, leaving notes for your future self, or recording context that doesn't fit in the description. AI agents can also add comments to items during sessions. You can edit or delete your own comments. Hover a comment you wrote and use the pencil to edit it inline (press Enter to save, Escape to cancel), or the trash icon to delete it. Edited comments are marked as edited. ### Activity Log Every change to an item is recorded in the activity log: * **Who** made the change (you or an AI agent) * **When** it happened * **What** changed (field name, before value, after value)

The item detail panel, which records every field change in its activity history — The detail panel records every change to the item, whether made by you or by an agent.

The activity log provides a complete audit trail. When an AI agent updates an item during a session, marking a bug as done or changing a plan's progress, that change is recorded with the same detail as manual edits. ### Linked Sessions Linked sessions appear at the top of the detail panel, above the item's fields, with a count. Each one shows the provider, the session title, and when it was last active. Click one to jump back to that conversation. Use **Launch Session** to start a fresh session for the item, or **Link Existing** to connect a session you already have.

Tracker item detail with the Sessions section at the top, above Status and Priority — The Sessions section sits at the top of the item detail, with Link Existing and Launch Session controls.

Linking is deliberate: creating or updating an item does not attach your current session unless you ask for it. See [Linking Sessions and Tracked Items](/task-management/linking-sessions-and-tracked-items.md). ### Open an Item in Agent Mode A tracker item opens as a tab in Agent mode, exactly like a file. You get the item's full body above and the agent session below, so you can write in the item and direct the agent against it without switching modes or losing your place.

Agent mode with a tracker item open as a tab above the session, showing the item body with its fields and content on top, the agent conversation underneath, and the session edits panel on the right — The item opens as a tab above the session. Edit its body on top, work with the agent underneath.

This is the natural place to work an item end to end. The agent reads and updates the same item you are editing, its file changes appear in the right panel as it goes, and the item stays linked to the session so the connection survives after you move on. Use the **Files**, split, and **Agent** controls at the top right to change how much room the item and the conversation each get. ### Choose What the Right Panel Shows The panel on the right of the agent window is a switcher, not a fixed sidebar. Use the dropdown in its header to change what it displays.

The agent window right panel dropdown, open on three options: Edited Files with a checkmark, Review, and Chat with Session — Switch the right panel between edited files, review, and a chat about the session.

* **Edited Files**: The files the agent created and changed in this session, with uncommitted changes and commit controls. * **Review**: The review queue for changes waiting on your approval. * **Chat with Session**: A conversation about the session itself, separate from the main transcript. When you have a tracker item open, the same panel can also scope a chat to that item. See [Agent Window & Session Management](/session-management/agent-window-and-session-management.md). ### Launch an Isolated Worktree When Git worktrees are available, choose **Launch Worktree** in the Sessions section to start an isolated worktree and AI session for the item. Nimbalyst proposes a branch and worktree name from the Tracker key and title, inserts a live Tracker reference into the session draft, and links the resulting session back to the item. Review the worktree details before creating it. Use **Launch Session** for work that can happen in the current project checkout. Use **Launch Worktree** when the task needs its own branch and filesystem state. See [Worktrees](/developer-features/worktrees.md). ### Linked Files Items backed by markdown files show their source file path. You can also explicitly link additional files to an item for reference: design docs, specs, or related source code. --- # 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/item-detail.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.