Connecting an AI client to developer tools should not imply access to every repository, shell session or secret available on a computer. A useful integration begins with a logical project identity and a narrowly authorized workspace.
Treat connection and permission as different things
- Pair the machine so requests can be routed to the intended runtime.
- Grant the specific workspace that the AI is allowed to understand and operate on.
- Let policy decide whether a requested action can run automatically or requires approval.
- Keep the transport stable so multiple compatible AI clients can reuse the same governed project boundary.
npm install -g codelocal@latest
# Then pair the runtime and grant the intended workspace.