---
title: "Comment by Julian Neagu on \"Safe AI Agentic Development: Sandboxing Coding Assistants\" | Hashnode"
description: "I’ve found that giving an agent too much access is easy to overlook when you’re trying to ship fast. Keeping it locked to the project folder feels like a simple"
url: "https://hashnode.com/posts/safe-ai-agentic-development-sandboxing-coding-assistants/6ac7b07de1efd00265261ad1/comment/6aca1674fdf3c22131a09978"
---

[Discussion](https://hashnode.com/posts/safe-ai-agentic-development-sandboxing-coding-assistants/6ac7b07de1efd00265261ad1)

Comment [Safe AI Agentic Development: Sandboxing Coding Assistants](https://hashnode.com/posts/safe-ai-agentic-development-sandboxing-coding-assistants/6ac7b07de1efd00265261ad1)

[Julian Neagu](https://hashnode.com/@julianneagulab)

[Oct 10](https://hashnode.com/posts/safe-ai-agentic-development-sandboxing-coding-assistants/6ac7b07de1efd00265261ad1/comment/6aca1674fdf3c22131a09978)

I’ve found that giving an agent too much access is easy to overlook when you’re trying to ship fast. Keeping it locked to the project folder feels like a simple win.

[Yadukrishnan](https://hashnode.com/@yadukrishnan)

[Oct 10](https://hashnode.com/posts/safe-ai-agentic-development-sandboxing-coding-assistants/6ac7b07de1efd00265261ad1/comment/6aca1674fdf3c22131a09978#reply-6aca2b723cf70b63238d63b5)

Exactly. Safe to lockdown the access outside the project directory by default. With sbx I am still exploring how to do that as sbx automatically mount the directory where you start it.
