Development Log: Local Path Code Review Preflight

Purpose

Prevent code review requests from falling back to "please upload files" when the user already provided an accessible local project path.

User Feedback

When the user gave a local path such as /Volumes/Data/project/Antigravity/Skybound, the agent did not inspect the folder and repeatedly asked for uploaded files. The expected behavior is to attempt local access first, then request uploads only if access fails.

Implementation Summary

Added a Local Path Handling Rule to the base system prompt.
Explicitly forbade upload requests before attempting local path inspection.
Added code review ordering guidance: confirm path access, scan tree, inspect package.json, src, docs, README, and config files first.
Added deterministic local project path preflight in the agent execution flow.
When a review/analysis prompt contains an allowed Antigravity project path, the agent now:
- validates path access
- scans the directory tree
- previews priority project files
- injects the result into the model context before the answer is generated
If access fails, the injected context includes the concrete failure reason.
Follow-up fix: expanded the scan depth so nested files such as src/features/game/systems/*.ts are included in priority previews.
Follow-up fix: added a final answer brake that removes upload-request wording when local path access already succeeded.

Changed Files

src/agent.ts
src/utils.ts
tests/systemPrompt.test.ts
tests/localPathPreflight.test.ts

Verification

./node_modules/.bin/tsc --noEmit
npm run compile
./node_modules/.bin/jest --runInBand

Result

For local project review requests, the agent should now inspect the provided path first and only ask for uploads when the path is inaccessible.

1.8 KiB Raw Permalink Blame History