Tracker behavior comes from a mix of project files and Nimbalyst settings. Custom type definitions and markdown-backed items can travel through version control. Native tracker items and settings such as the issue-key prefix stay in Nimbalyst's local database and settings store unless you share their tracker with a team.

Tracker Type Definitions

Custom tracker types live in the .nimbalyst/trackers/ directory at your project root. Each YAML file in this directory defines one tracker type. Nimbalyst loads all type definitions when the workspace opens.

your-project/
  .nimbalyst/
    trackers/
      customer-feedback.yaml
      release-note.yaml
      interview-question.yaml

See Custom Tracker Types for the full YAML schema.

Markdown-backed tracker items

Nimbalyst's built-in tracker workflows use the nimbalyst-local/tracker/ directory for markdown files that carry inline tracker tags. You can also track a markdown file anywhere in the project by adding trackerStatus frontmatter.

your-project/
  nimbalyst-local/
    tracker/
      bugs.md
      sprint-12-tasks.md
      api-decisions.md
      q2-features.md

These are standard markdown files. Changes made through the tracker UI update the underlying file, and file edits flow back into the tracker.

Issue Key Prefix

Each project can have a configurable issue-key prefix (for example NIM) for numbered local items. Configure it under Settings > Project > Trackers. In a team project, the team owns its shared issue-key prefix; personal items use a separate local prefix so keys do not collide.

Commit-Tracker Linking

Automatic commit-tracker linking is an opt-in application setting under Settings > Application > Advanced. When enabled, Nimbalyst links commits through session relationships and by parsing issue keys (for example NIM-42) in commit messages, including commits made in the terminal.

What Gets Version-Controlled

Tracker files are plain markdown, so they work with any version control system:

.nimbalyst/trackers/*.yaml -- Type definitions travel with the repo. Anyone who clones the project gets the same custom types.
nimbalyst-local/tracker/*.md -- Markdown-backed items can be committed for visibility through git or ignored to keep them machine-local.
Changes to tracker items via the UI or AI update the underlying markdown files, which show up in your normal git diff and commit workflow.

Native items stored in Nimbalyst's database do not appear in git diffs. To collaborate on those items in real time, use a team tracker.