Collaborative Trackers

Share one tracker board across your team. Teammates and their locally running AI agents keep the same bugs, features, and plans current.

One shared board your team and its agents keep current

Bugs, features, tasks, plans, and decisions live on shared Trackers in the same workspace as your docs. Teammates and their local agents update the same items in real time or asynchronously, so the board reflects what is actually happening.

See shared trackers in Nimbalyst Teams for how the shared board works.

Group shared work by tag to see plans across areas and milestones.

One board, everyone on it

Use kanban stages, lists, filters, and saved views to organize shared work.

• Real-time and multiplayer: The board updates live as people and agents change items, with no refresh or manual synchronization.

• Kanban with your stages: Move work across the stages you define, from backlog to done, on a shared kanban board.

• Recently changed: See what moved recently, with a marker on items that changed since you last looked.

The tracker also includes a sortable list, filters, saved views, and a tag board.

Your agents and your team keep it up to date

Open an item to see its current fields, content, owner, and the session working on it.

• Agents update the board: Claude Code and Codex agents can create items, change status, and update many trackers as they work.

• People edit too: Teammates edit the same items by hand, so the board stays accurate whether a person or agent made the change.

• Comments and full history: Every item keeps a threaded discussion and a record of what changed and who changed it.

Enable or disable agent Tracker tools per project under Settings > Project > Trackers > AI Agent Access.

Track any kind of work

Create tracker types and relationships that match how your team organizes work.

• Bugs, features, and your own types: Use built-in trackers or define custom types with the fields you need.

• Hierarchy and links: Break work into parent and child items and link related items across trackers.

• Fields that fit: Give each type its own fields, statuses, owners, tags, dates, priorities, and progress.

See Custom Tracker Types and Linking Tracker Items.

A collaborative document inside every item

Each full tracker item has a rich body the team edits together, so the plan and discussion live with the task.

Write the plan in the item and embed diagrams, mockups, images, and other project files.

• Write the plan in place: Draft the spec, repro steps, decision, or rollout plan inside the item.

• Diagrams and mockups too: Add diagrams, mockups, images, data models, and spreadsheets so the full picture sits with the work.

• Edited together: The item body is collaborative, so teammates and agents work on it in the same place.

Every item is wired into the work

An item connects to the sessions working it, the parent and child items around it, and the documents that reference it.

Build a hierarchy around the work and link the session, source file, and pull request that belong to it.

• Hierarchy and linked sessions: Break work into parent and child items, and connect each one to the session working it, the file it came from, and the pull request that closes it.

The agent updates linked items while it works and reports the changes in the session.

• Updated from the session: Claude Code and Codex agents change linked items as they work, so a session and its tracker items stay in step.

Reference live tracker items in a document so their current status stays beside the plan.

• Tracker pills in your docs: Reference an item in any document with a live pill that shows its status and links back to the board.

Use Link Existing, Launch Session, or ask the agent to link the current session when that relationship belongs in the item's history.

Keep trackers private or share them, and organize by tag

Keep personal trackers local, promote team trackers to shared, and group the shared board by tag.

• Local trackers: Track your own work in local trackers that stay on your machine.

• Shared trackers: Promote a tracker to shared so the whole team and its agents work on the same board.

• Board by tag: Group the board by tag to slice work by area, milestone, or any other label.

Choose a sync policy per tracker type

Sharing is decided per tracker type, not all-or-nothing, under Settings > Project > Trackers > Team Sync Policy. Changes apply to every member of the team.

Each tracker type is Local, Shared, or Hybrid, with its current item count beside it.

• Shared: Items sync to all team members in real time. The row reads Visible to all team members.

• Local: Items stay on your machine only. The row reads Only visible to you.

• Hybrid: Each item carries its own sharing choice, so one tracker type can hold both team and private work.

An Override badge marks a type whose settings differ from the default. Use the pencil to edit it and the revert arrow to return it to the default. Custom types you defined yourself can be deleted from this panel.

Inline #type[...] items stay local until they are promoted to full items. Shared items show their synchronization state, and list view can display the optional Shared column.

Shared Tracker data flows through Nimbalyst's Cloudflare sync service and is encrypted in transit and at rest. Local and unshared items remain outside the team workspace.