Settings

nabsConfidence.retrosFolder

Default

team/retros

Scope

Workspace folder

Type

string

Folder (relative to the repository root) where retro files are stored.

nabsConfidence.defaultPeriodDays

Default

14

Scope

Workspace folder

Type

integer

How many days a retro looks back over, by default: the period ends on the retro date and starts defaultPeriodDays - 1 days earlier (so 14 = a two-week sprint, inclusive). The New Retro form pre-fills this period, and points out (with a one-click fix) when it overlaps the previous retro or leaves a gap.

Allowed range: 1 to 366.

nabsConfidence.home.openAutomatically

Default

whenNothingIsOpen

Scope

Window

Type

string

Whether the Home page (the extension's landing page: objectives and the next retro) opens by itself when the Retros view opens.

Choices:

• whenNothingIsOpen — Open the Home page when the Retros view opens and no editor or panel is open, at most once per window (closing it is respected).
• never — Don't open it by itself: use the Home button in the Retros view, or NABS Confidence: Open Home.

nabsConfidence.home.reviewAfterDays

Default

28

Scope

Workspace folder

Type

integer

Home flags an objective Needs review when it was last assessed longer ago than this many days, or wasn't assessed in the latest retro. The default, 28, is two two-week periods.

Allowed range: 1 to 366.

nabsConfidence.defaultFeedbackTemplate

Default

classic

Scope

Workspace folder

Type

string

Overrides the default feedback template for new retros. If empty, the default comes from the template sources ("default" in a templates.json), else classic.

nabsConfidence.feedbackTemplates

Default

[]

Scope

Workspace folder

Type

array

Your own feedback templates (retro formats), in addition to the built-in ones. A template with the id of a built-in one replaces it. Each has:

• id, label (required): e.g. team-health / Team health. The id is saved in each retro's front matter (feedbackTemplate:), so don't rename it once used.
• types (required): the feedback types people can add, each with id, label and optional description, icon, section (wentWell, didNotGoWell, actionItems or none: which retro section the type feeds) and prompt (an outline the feedback box starts with).
• headings (optional): wentWell, didNotGoWell, actionItems: the headings of those sections in new retros.
• ratingScale (optional): options with value, label, icon, section; every entry then needs a rating, and the rating's section wins.
• trendScale (optional): options with value, label, icon for an optional trend (e.g. improving / same / getting worse).
• questions (optional): questions for the team, written into new retros.
• aiGuidance (optional): extra instructions for Copilot when it summarises this kind of feedback.

Invalid templates are skipped with a warning. See the README for an example.

nabsConfidence.templateSources

Default

[
  "repo",
  "shared",
  "nabs"
]

Scope

Workspace folder

Type

array

Where feedback templates come from, highest precedence first: when two sources have a template with the same id, the earlier one wins. repo = template folders in <retrosFolder>/templates/; shared = nabsConfidence.sharedTemplates; nabs = the built-in templates. nabsConfidence.feedbackTemplates is applied on top of all of them.

nabsConfidence.sharedTemplates

Default

(empty)

Scope

Workspace folder

Type

string

A shared template repository maintained by your agile team, read as raw files over the GitHub API (no clone) and cached for offline use: owner/repo, owner/repo/path/to/templates, optionally @branch-or-tag, or a URL such as https://github.com/owner/repo/tree/main/templates. A local folder (an absolute path) also works. Private repositories use your VS Code GitHub sign-in. Run NABS Confidence: Refresh Feedback Templates to fetch the latest.

nabsConfidence.feedbackTypes

Default

[
  {
    "id": "went-well",
    "label": "Went well",
    "description": "Something that helped the team.",
    "icon": "👍",
    "section": "wentWell"
  },
  {
    "id": "didnt-go-well",
    "label": "Didn't go well",
    "description": "Something that slowed us down or hurt.",
    "icon": "👎",
    "section": "didNotGoWell"
  },
  {
    "id": "idea",
    "label": "Idea / suggestion",
    "description": "Something to try next time; becomes a suggested action item.",
    "icon": "💡",
    "section": "actionItems"
  },
  {
    "id": "kudos",
    "label": "Kudos",
    "description": "Thanks or recognition for someone.",
    "icon": "🙌",
    "section": "wentWell"
  }
]

Scope

Workspace folder

Type

array

Deprecated. Replaced by Feedback Templates (nabsConfidence.feedbackTemplates) in 0.3.0. If you set this, it still works: it becomes the *Custom (from Feedback Types setting)* template, and the default for new retros unless you set nabsConfidence.defaultFeedbackTemplate. To migrate, copy the array into the types of a template in nabsConfidence.feedbackTemplates and remove this setting.

Deprecated (see nabsConfidence.feedbackTemplates). The types of feedback people can add (shown in the Add Feedback form, in that order). Each type has:

• id (required): stored in the feedback file, e.g. went-well. Letters, digits, - and _. Don't rename an id once you've used it: entries with an id that isn't listed here still load, but show as *Other*.
• label (required): what people see, e.g. Went well.
• description, icon (optional): a short explanation and an emoji.
• section (optional): which retro section the type feeds when you run Summarise Feedback into Retro: wentWell, didNotGoWell, actionItems (suggested actions) or none (Copilot uses its judgement; the plain summary leaves it out).

Invalid entries are skipped with a warning; if none are valid, the defaults are used.

nabsConfidence.feedbackEntryTemplate

Default

## {{timestamp}} | {{author}} | {{type}} {{text}}

Scope

Workspace folder

Type

string

How each feedback entry is written to the feedback file (Markdown). Must contain {{text}} exactly once. Placeholders: {{timestamp}}, {{date}}, {{time}}, {{author}}, {{type}} (the id), {{typeLabel}}, {{icon}}, {{rating}} (for templates with a rating scale), {{text}}, {{retroDate}}.

Example: ### {{icon}} {{typeLabel}} — {{author}}, {{date}} then {{text}} on the next line.

The extension always writes a hidden <!-- retro:feedback {...} --> marker line above each entry and reads the author, time and type from that, so changing this template never breaks reading older entries. An invalid template falls back to the default with a warning.

nabsConfidence.feedbackFiles

Default

perPerson

Scope

Workspace folder

Type

string

Where Add Feedback writes new entries. Either way, the Retros view, Summarise Feedback and Copilot read *all* of a retro's feedback files, so you can switch at any time. Anonymous entries always go into the shared file.

Choices:

• perPerson — Each person's feedback goes into their own file, <date>-retro.feedback/<your-name>.md: no merge conflicts, and people can add feedback in their own time and time zone.
• shared — Everyone's feedback goes into one shared file, <date>-retro.feedback.md (how 0.3.0 and earlier worked).

nabsConfidence.actionItemLabel

Default

retro-action

Scope

Workspace folder

Type

string

The label given to GitHub issues created by Create GitHub Issues for Action Items (it's created in the repository if it doesn't exist).

nabsConfidence.objectivesFolder

Default

team/objectives

Scope

Workspace folder

Type

string

Where the team's objective files are (<id>.md, relative to the workspace folder). New Objective... creates them here. See the README's Objectives section for the format.

nabsConfidence.objectiveSources

Default

[
  "files"
]

Scope

Workspace folder

Type

array

Where the objectives come from, in order (the first wins when two have the same id): files (the objectives folder), issues (GitHub issues of this repository with the Objective label) and issues:owner/repo (another repository's). For example ["files", "issues:my-org/strategy"]. Issue sources need a GitHub sign-in.

nabsConfidence.objectiveLabel

Default

objective

Scope

Workspace folder

Type

string

The label that marks a GitHub issue as an objective (for the issues sources of Objective Sources).

nabsConfidence.useAI

Default

true

Scope

Workspace folder

Type

boolean

Use a GitHub Copilot language model to summarise the period and the feedback. When off, retros are still created with the deterministic insights.

nabsConfidence.modelFamily

Default

(empty)

Scope

Workspace folder

Type

string

Preferred Copilot model family (for example gpt-4.1). Leave empty to use the first available Copilot model.

nabsConfidence.facilitator

Default

(empty)

Scope

Workspace folder

Type

string

Default facilitator name for new retros. Defaults to your Git user.name.

nabsConfidence.includeGitHub

Default

true

Scope

Workspace folder

Type

boolean

Include GitHub issues, pull requests and discussions in the insights (needs a github.com remote and a GitHub sign-in).

nabsConfidence.release.since

Default

(empty)

Scope

Workspace folder

Type

string

The Git tag or commit that the release is compared with, for the changed-code summary and the *unowned change* check of Release Confidence. Empty means the newest tag that looks like v1.2.3.

nabsConfidence.release.unknownRunCredit

Default

half

Scope

Workspace folder

Type

string

How much a real-world run counts toward an activity's score when the run records no commit and is on another version, so what changed since is not known.

Choices:

• half — Half credit: as if only shared code changed since (what the coverage matrix assumes).
• none — No credit: as if the activity's own code changed since.

nabsConfidence.release.writtenGaps

Default

ignore

Scope

Workspace folder

Type

string

The catalogue's gaps are free text with no severity yet. This chooses how much each one takes off an activity's score in Release Confidence, or ignores them.

Choices:

• ignore — Do not count them.
• low — Count each as a low gap.
• medium — Count each as a medium gap.
• high — Count each as a high gap.