The scenario

A repository already builds on a developer Mac, Linux or Windows workstation. It has the right SDKs, caches, test data and local services. Recreating that environment in a cloud sandbox adds delay and often changes the behavior being investigated.

A bounded workflow

Expose one repository folder, authorize one Agent for the required tools and connect the preferred MCP client or CLI. The Agent can inspect files, apply a focused patch and run the existing test command without receiving general access to the rest of the device.

adc login --url https://your-adc.example
adc connect ACCESS
adc invoke file.read --node node_example \
  --args '{"path":"/Users/me/work/README.md"}' --json

Controls that remain in place

The device keeps the final decision. Removing the folder or narrowing local access is reflected by the Connector and can cancel affected running work. Every completed side effect retains a receipt for later review.