Skip to content

Ask before initializing Tracybot in a repository - #145

Open
ranimkhojah wants to merge 1 commit into
mainfrom
ask-before-init
Open

ranimkhojah wants to merge 1 commit into
mainfrom
ask-before-init

Conversation

@ranimkhojah

Copy link
Copy Markdown
Contributor

The extension initialized Tracybot in every repository opened in VS Code, adding Git hooks and recording AI prompts without asking. It now asks "Do you want to initialize Tracybot for this project?" with Initialize, Not now and Never for this project; a "never" is remembered inside .git. The Research Mode prompt only follows once the repo is initialized.

Repos that are already initialized are not asked again, and a stale script path after an extension update is still repaired silently. A new "Tracybot: Initialize in This Repository" command, plus Initialize buttons in AI Blame and Manage Research Mode, cover repos that were declined or skipped.

The extension initialized Tracybot in every repository opened in VS Code,
adding Git hooks and recording AI prompts without asking. It now asks
"Do you want to initialize Tracybot for this project?" with Initialize,
Not now and Never for this project; a "never" is remembered inside .git.
The Research Mode prompt only follows once the repo is initialized.

Repos that are already initialized are not asked again, and a stale
script path after an extension update is still repaired silently. A new
"Tracybot: Initialize in This Repository" command, plus Initialize
buttons in AI Blame and Manage Research Mode, cover repos that were
declined or skipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@EsmeYi

EsmeYi commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

LGTM!

PS. This is not a regression introduced by this PR, but I found it while testing: when .git is a file rather than a directory (linked worktrees and submodules), the .git/tracybot/... paths don't work.

For example, in a linked worktree, clicking "Never for this project" throws ENOTDIR, and an existing config is not detected, this already happens on main. I'll submit a separate PR for that. It doesn't need to block this one.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants