fix(server): detect repositories after initialization

[StiensWout]

Problem

Initializing Git from a fresh thread creates the repository, but the immediate status refresh can reuse a cached negative repository detection. The UI then continues to show "Initialize Git" until another event, such as the first agent turn completing, refreshes Git status.

Fix

Cache successful repository detections for the existing two-second TTL, but do not retain negative detections. This lets the status refresh following git init discover the repository immediately while preserving the positive detection cache.

A focused registry test covers a path transitioning from non-repository to repository between consecutive detections.

Validation

• vp test run apps/server/src/vcs/VcsDriverRegistry.test.ts apps/server/src/vcs/VcsProvisioningService.test.ts apps/server/src/vcs/VcsStatusBroadcaster.test.ts
• vp run --filter t3 typecheck
• Reproduced in an isolated T3 instance before the fix: .git existed within 100 ms, while the UI remained stale for 10+ seconds and updated only when the first agent turn completed.

Generated with GPT-5.6-Sol in T3 Code using the Codex harness.

---

Note

Low Risk
Small, targeted cache TTL change in VCS detection with a regression test; no auth or data-path changes.

Overview
Fixes stale Initialize Git UI after git init by changing how VCS repository detection is cached in VcsDriverRegistry.

Successful detections still use the existing 2s TTL, but negative results (null, no repo) are no longer cached—they get zero TTL so the next status refresh re-runs detection. Failures also skip retention. A new test asserts that a second detect call sees a repo after the first call returned non-repo.

^{Reviewed by Cursor Bugbot for commit f609a4d. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix repository detection cache to not cache null results in VcsDriverRegistry

Previously, a null result from repository detection (e.g. "not a git repository") was cached with the full TTL, preventing a subsequent positive detection. Now, only non-null detection results are cached; null results and failures expire immediately (TTL of zero). A new test in VcsDriverRegistry.test.ts verifies that a negative lookup followed by a positive one returns the correct repository on the second attempt.

^{Macroscope summarized f609a4d.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4cf03d2c-cde8-4272-a796-dd43fde03d6f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved f609a4d

This is a focused bug fix that changes cache TTL behavior for negative repository lookups. The 3-line change prevents caching of "no repository found" results, enabling detection of repositories created after initial lookup. Well-tested with a clear unit test covering the exact scenario.

^{You can customize Macroscope's approvability policy. Learn more.}