# Local Config

Tracker behavior is configured through project-level directories and settings. Everything is stored as plain files, version-controlled, and portable between machines.

### 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](/task-management/custom-tracker-types.md) for the full YAML schema.

### Tracker Files

Inline tracker markdown files are stored in the `nimbalyst-local/tracker/` directory within your project. You can organize files by type, topic, sprint, or any structure that works for you:

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

These are standard markdown files with inline `#type[...]` tags or `trackerStatus` YAML frontmatter. The tracker system scans this directory and surfaces all items in the kanban board and list view.

### Issue Key Prefix

Each project can have a configurable issue key prefix (e.g., `NIM-`) that appears on all item IDs. This makes it easy to reference items in commit messages, comments, and conversations. Configure the prefix in your project settings.

### Commit-Tracker Linking

Automatic commit-tracker linking is an opt-in toggle in project settings. When enabled, Nimbalyst scans git commit messages for item ID references (e.g., `NIM-42`) and links the commit to the corresponding tracker item.

### 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` -- Item files are local by default. Add them to `.gitignore` if you want project-specific items that don't sync, or commit them if you want shared visibility.
* 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.


---

# Agent Instructions: 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:

```
GET https://docs.nimbalyst.com/task-management/local-config.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.