Handle non-git drafts in local mode

[SAKETH11111]

Closes #1914

What was broken

Draft threads could stay in New worktree mode for directories that are not Git repositories. On the first send, that pushed users into the base-branch guard even though the project could only run locally.

Root cause

The draft env-mode resolver treated persisted worktree mode as authoritative without considering the active project's Git status, so non-git drafts kept a worktree-only send path.

What changed

• fall back to local mode when the active project is known to be non-git
• normalize draft thread state away from stale worktree metadata for non-git projects
• add regression coverage for the shared env-mode resolver and the browser send flow

Note

Handle non-git projects in local draft mode by falling back from worktree to local send

• resolveEffectiveEnvMode in BranchToolbar.logic.ts gains an optional isGitRepo flag; when false, it returns 'local' regardless of the draft's persisted mode.
• Local drafts on non-git projects automatically reset their thread context to local mode (null branch and worktree path) via a new useEffect in ChatView.tsx.
• Before enforcing the base-branch requirement on a first worktree-mode message, ChatView now calls refreshGitStatus; if the project is not a git repo, it falls back to a local send and skips prepareWorktree.
• Behavioral Change: drafts saved in worktree mode will silently send as local when the project is not a git repo.

^{Macroscope summarized f56bf0c.}

---

Note

Medium Risk
Touches the first-send dispatch path and draft thread state normalization for worktree creation, which could affect message sending/worktree bootstrapping behavior. Changes are scoped and covered by new unit + browser regression tests but still impact a core interaction flow.

Overview
Fixes drafts getting stuck in New worktree mode for non-git projects by making env-mode resolution explicitly fall back to local when isRepo is false, even if worktree was persisted.

Normalizes local draft thread state when git status indicates a non-repo (clearing branch/worktreePath and forcing envMode: "local"), and updates the send flow to refresh git status before enforcing the worktree base-branch guard—falling back to local dispatch (or persisting the detected branch) based on the refreshed result.

Adds regression coverage in BranchToolbar.logic tests and full-app ChatView.browser tests for non-git fallback and the pending-status refresh race.

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

[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

Run ID: f2215670-c9f7-43f4-8550-d674cdb5c5e6

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR modifies runtime behavior in the message send flow by adding git status checks and fallback logic for non-git projects. While the changes are well-tested and the edge case handling is sensible, the modifications to critical path code (message sending) warrant human review to verify the interaction with existing worktree/local mode logic.

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